Blue Screen Windows 2008 Server R2 : Help !

Blue Screen Windows 2008 Server R2 : Help ! - Infrastructures serveurs - Systèmes & Réseaux Pro

Marsh Posté le 04-09-2012 à 15:30:18    

Bonjour à tous,
 
j'ai un plantage avec blue screen et ou reboot de mon serveur Windows 2008 R2 qui arrive presque chaque jour,
j'ai voulu effectuer une vérication de mon fichier memory.dmp pour comprendre d'ou celà peut provenir, mais je n'arrive pas à l'interpreter.
 
voici le résultat du fichier memory.dmp après anylse de windbg :
 

Citation :


Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\Administrateur\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
 
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:  
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0181b000 PsLoadedModuleList = 0xfffff800`01a57e70
Debug session time: Tue Sep  4 13:55:42.917 2012 (UTC + 2:00)
System Uptime: 1 days 2:46:29.190
Loading Kernel Symbols
...............................................Missing image name, possible paged-out or corrupt data.
.*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147
 
Loading unloaded module list
.....
WARNING: .reload failed, module list may be incomplete
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1, {776cfaaa, 0, fffe, fffff8800aa12ca0}
 
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
 
Followup: MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00000000776cfaaa, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000fffe, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff8800aa12ca0, Call type (0 - system call, 1 - worker routine)
 
Debugging Details:
------------------
 
 
FAULTING_IP:  
+0
00000000`776cfaaa ??              ???
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
BUGCHECK_STR:  0x1
 
CURRENT_IRQL:  0
 
LAST_CONTROL_TRANSFER:  from 0000000000000000 to 000007fefdec4bd4
 
STACK_TEXT:  
00000000`027dd880 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fdec4bd4
 
 
STACK_COMMAND:  kb
 
SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: Unknown_Module
 
IMAGE_NAME:  Unknown_Image
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
BUCKET_ID:  INVALID_KERNEL_CONTEXT
 
Followup: MachineOwner
---------
 


 
Quel'un aurait il un indice ?


---------------
http://www.mangas-videos.com
Reply

Marsh Posté le 04-09-2012 à 15:30:18   

Reply

Marsh Posté le 04-09-2012 à 15:32:33    

Commence par le mettre à jour, puis regarde si tu n'as pas un driver ou l'antivirus qui mettrait la pagaille.

Reply

Sujets relatifs:

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed