Blue screen a répétition

[percubabs]

Bonjour,

 

J'ai un pc qui blue screen souvent.

J'ai récupéré le dmp mais je ne sais pas le déchiffrer.

 

Est ce que quelqu'un peut m'aider?

 

ps : c'est arrivé sur internet.

 

Merci

Microsoft ® Windows Debugger  Version 6.4.0007.2Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [xxxxxxxxxxxMini100614-02.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: *** Invalid ******************************************************************************** Symbol loading may be unreliable without a symbol search path.           ** Use .symfix to have the debugger choose a symbol path.                   ** After setting your symbol path, use .reload to refresh symbol locations. *****************************************************************************Executable search path is: ********************************************************************** Symbols can not be loaded because symbol path is not initialized. **                                                                   ** The Symbol Path can be set by:                                    **   using the _NT_SYMBOL_PATH environment variable.                 **   using the -y <symbol_path> argument when starting the debugger. **   using .sympath and .sympath+                                    **********************************************************************Unable to load image ntoskrnl.exe, Win32 error 2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSKernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720Debug session time: Mon Oct  6 10:23:50.139 2014 (GMT+2)System Uptime: 0 days 0:05:58.059********************************************************************** Symbols can not be loaded because symbol path is not initialized. **                                                                   ** The Symbol Path can be set by:                                    **   using the _NT_SYMBOL_PATH environment variable.                 **   using the -y <symbol_path> argument when starting the debugger. **   using .sympath and .sympath+                                    **********************************************************************Unable to load image ntoskrnl.exe, Win32 error 2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols.....................................................................................................................Loading unloaded module list.............Loading User SymbolsUnable to load image watchdog.sys, Win32 error 2*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1000008E, {e0000001, ba480925, ae0a4820, 0}***** Kernel symbols are WRONG. Please fix symbols to do analysis.****************************************************************************                                                                   ******                                                                   ******    Your debugger is not using the correct symbols                 ******                                                                   ******    In order for this command to work properly, your symbol path   ******    must point to .pdb files that have full type information.      ******                                                                   ******    Certain .pdb files (such as the public OS symbols) do not      ******    contain the required information.  Contact the group that      ******    provided you with these symbols if you need this command to    ******    work.                                                          ******                                                                   ******    Type referenced: nt!_KPRCB                                     ******                                                                   ****************************************************************************Probably caused by : watchdog.sys ( watchdog+925 )Followup: MachineOwner---------

[Ellierys]

1000008E, {e0000001}

 

 

Petit souci de drivers visiblement. Que dit le journal des évènements de Windows ? :)

[percubabs]

pas évident, tu veux quoi? appli, système ? c'est un xp

 

J'ai pas mal d’erreurs Userenv

 

"Erreur réseau inattendue" Le traitement de la stratégie de groupe est interrompu.

[Invité]

Utilise blue screen reader de nirsoft et met une capture d'écran avec la première ligne cliquee. Ça permettra de savoir quel fichier est impliqué et par conséquent l'origine. Ceci dit, au pif je pense a un driver realtek dans une version pourrie (fréquent)

[Aloyse57]

C'est une machine réelle ou VM (je vois TerminalServer et je me demande si c'est normal/pourquoi) ?

[percubabs]

réelle, c'est un des derniers xp à remplacer.