Cooling-Masters
Connexion · INSCRIPTION · Site Recevoir à nouveau l'e-mail de validation


En finir avec les BSOD

Ajouter ou retirer ce sujet de vos favoris  ·  Suivre ce sujet  ·  Imprimer ce sujet
Page précédente    Page suivante 
xalis


Membre
Messages : 9791

vendredi 04 avril 2008 à 03:21:03     
Tout le monde connait les bsod je suppose ? Bien, depuis quelques temps que mon portable bsod comme qui rigole ( à tour de bras donc ).
J'ai donc décidé de me doter d'une arme létale : windbg

Alias windows debugger.

Lors d'un bsod, un fichier minidump est automatiquement crée et stocké à la racine, plus précisément ici : \SystemRoot\Minidump\

Je propose donc à toute personne subissant le courroux du bsod, de lire leur fichier minidump afin de trouver l'origine de leur(s) problème(s).

Message édité par benoît le vendredi 04 avril 2008 à 03:31:05
Google




     
xalis


Membre
Messages : 9791

vendredi 04 avril 2008 à 03:21:41     
Exemple de fichier minidump décrypté :


Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ben\Desktop\Mini040308-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols\
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81c39000 PsLoadedModuleList = 0x81d50c70
Debug session time: Thu Apr 3 16:42:02.779 2008 (GMT+2)
System Uptime: 0 days 5:27:18.714
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 88882030, 874db030, 86f10e00}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.
SPOILER :


*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_DEVICE_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntkrnlpa.exe ( nt+cd163 )

Followup: MachineOwner
---------

Message édité par benoît le vendredi 04 avril 2008 à 03:24:18
xalis


Membre
Messages : 9791

vendredi 04 avril 2008 à 03:22:41     
Exemple de fichier Minidump analysé :

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 88882030, Physical Device Object of the stack
Arg3: 874db030, Functional Device Object of the stack
Arg4: 86f10e00, The blocked IRP

Debugging Details:
------------------
SPOILER :


***** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_DEVICE_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************



MODULE_NAME: nt

FAULTING_MODULE: 81c39000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12

DRVPOWERSTATE_SUBCODE: 3

DEVICE_OBJECT: 874db030

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x9F

LAST_CONTROL_TRANSFER: from 81c6cb6c to 81d06163

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
81d2eacc 81c6cb6c 0000009f 00000003 88882030 nt+0xcd163
81d2eb28 81c6c6bc 81d2ebac 87e932f8 87d0bc00 nt+0x33b6c
81d2eb68 81cefd00 81d474e0 00000000 e150c650 nt+0x336bc
81d2ec88 81cef8c0 81d2ecd0 87662002 81d2ecd8 nt+0xb6d00
81d2ece8 81cef483 00000000 00000000 00133582 nt+0xb68c0
81d2ed50 81cedf9d 00000000 0000000e 00000000 nt+0xb6483
81d2ed54 00000000 0000000e 00000000 00000000 nt+0xb4f9d


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+cd163
81d06163 8be5 mov esp,ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+cd163

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

Message édité par benoît le vendredi 04 avril 2008 à 03:23:33
Cooling


Membre
Messages : 327

samedi 05 avril 2008 à 11:07:24     
Pour en finir avec les BSOD, suffit de passer sous un OS autre que ceux de M$
--> []

Message édité par Cooling le samedi 05 avril 2008 à 11:07:35
perecastor


Modérateur-faker/Portuguais des iles/父 亲河&a
Messages : 15091

samedi 05 avril 2008 à 12:25:12     
Ou installer vista
xalis


Membre
Messages : 9791

samedi 05 avril 2008 à 12:38:00     
edit : trolls out
Tyrou


★ Jet Lag Addict ★
Messages : 21926

samedi 05 avril 2008 à 12:41:21     
(ou avoir un pc stable, installé correctement, j'ai jamais vu le BSOD de vista sur mon pc d'usage courant )
perecastor


Modérateur-faker/Portuguais des iles/父 亲河&a
Messages : 15091

samedi 05 avril 2008 à 12:48:34     
+1 spours ca que je dit d installer vista
J ai jamais eu de bsod mis a part au debut et c etait a cause des drivers tiers.....
kissagogo27


Méchant Vieux Râleur
Messages : 27502

samedi 05 avril 2008 à 12:59:05     
j'en ai qu'au debut d'un windows vierge le temps d'installer les pilotes et ensuite la paix
xalis


Membre
Messages : 9791

samedi 05 avril 2008 à 13:20:19     
moi j'ai eu un problème avec un driver fourni dans l'inf chipset d'intel
KzR


Modérateur Trancheur
Messages : 11562

samedi 05 avril 2008 à 13:55:52     
Moi depuis que je suis sous Mac OSX, j'ai eu très très peu de plantage, 2 ou 3 max, ben vi ça arrive aussi aux autres OS mais toujours beaucoup moins qu'XP et consort Vista, je n'en sais rien pas trop essayé à part pour remettre le système en état, en tout cas je ne suis pas trop attiré par ce truc
Bien souvent les BSOD que j'ai eu étaient dus à une mauvaise gestion de la mémoire sous XP
Google




     
Page précédente    Page suivante