Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
849 connectés 

  FORUM HardWare.fr
  Windows & Software
  Win Vista

  bsod vista 64bits

 


 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

bsod vista 64bits

n°2912871
girafe
vive linux
Posté le 19-11-2009 à 19:37:32  profilanswer
 

bonsoir à toi  
 
j'ai un vista 64 bits et j'ai un BSOD de temps à autre souvent quand je branche une clé usb ou carte mémoire  
 
voici le détail de l'erreur  
 
Signature du problème :  
Nom d’événement de problème: BlueScreen  
Version du système: 6.0.6002.2.2.0.768.3  
Identificateur de paramètres régionaux: 1036  
 
Informations supplémentaires sur le problème :  
BCCode: 50  
BCP1: FFFFFFFFFFFFFFF2  
BCP2: 0000000000000000  
BCP3: FFFFF80002D97D13  
BCP4: 0000000000000000  
OS Version: 6_0_6002  
Service Pack: 2_0  
Product: 768_1  
 
Fichiers aidant à décrire le problème :  
C:\Windows\Minidump\Mini111709-02.dmp  
C:\Users\Benoit\AppData\Local\Temp\WER-50653-0.sysdata.xml  
C:\Users\Benoit\AppData\Local\Temp\WER888.tmp.version.txt  
 
Lire notre déclaration de confidentialité :  
http://go.microsoft.com/fwlink/?li [...] cid=0x040c  
 
 
j'ai fait un windbg et voila le rapport  
 
 
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86  
Copyright (c) Microsoft Corporation. All rights reserved.  
 
 
Loading Dump File [C:\Windows\Minidump\Mini111709-02.dmp]  
Mini Kernel Dump File: Only registers and stack trace are available  
 
Symbol 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2  
*** WARNING: Unable to verify timestamp for ntoskrnl.exe  
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe  
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64  
Product: WinNt, suite: TerminalServer SingleUserTS Personal  
Machine Name:  
Kernel base = 0xfffff800`02c64000 PsLoadedModuleList = 0xfffff800`02e28dd0  
Debug session time: Tue Nov 17 22:17:49.303 2009 (GMT+1)  
System Uptime: 0 days 0:49:19.197  
*********************************************************************
* 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2  
*** WARNING: Unable to verify timestamp for ntoskrnl.exe  
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe  
Loading Kernel Symbols  
...............................................................  
................................................................  
........................  
Loading User Symbols  
Loading unloaded module list  
...  
*******************************************************************************
* *  
* Bugcheck Analysis *  
* *  
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.  
 
BugCheck 50, {fffffffffffffff2, 0, fffff80002d97d13, 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 ***  
*** ***  
*************************************************************************
*************************************************************************
*** ***  
*** ***  
*** 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 ***  
*** ***  
*************************************************************************
*********************************************************************
* 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+ *  
*********************************************************************
*********************************************************************
* 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+ *  
*********************************************************************
Probably caused by : Microsoft (R) Windows Debugger Version 6.11.0001.404 X86  
Copyright (c) Microsoft Corporation. All rights reserved.  
 
 
Loading Dump File [C:\Windows\Minidump\Mini111709-02.dmp]  
Mini Kernel Dump File: Only registers and stack trace are available  
 
Symbol 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2  
*** WARNING: Unable to verify timestamp for ntoskrnl.exe  
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe  
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64  
Product: WinNt, suite: TerminalServer SingleUserTS Personal  
Machine Name:  
Kernel base = 0xfffff800`02c64000 PsLoadedModuleList = 0xfffff800`02e28dd0  
Debug session time: Tue Nov 17 22:17:49.303 2009 (GMT+1)  
System Uptime: 0 days 0:49:19.197  
*********************************************************************
* 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2  
*** WARNING: Unable to verify timestamp for ntoskrnl.exe  
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe  
Loading Kernel Symbols  
...............................................................  
................................................................  
........................  
Loading User Symbols  
Loading unloaded module list  
...  
*******************************************************************************
* *  
* Bugcheck Analysis *  
* *  
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.  
 
BugCheck 50, {fffffffffffffff2, 0, fffff80002d97d13, 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 ***  
*** ***  
*************************************************************************
*************************************************************************
*** ***  
*** ***  
*** 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 ***  
*** ***  
*************************************************************************
*********************************************************************
* 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+ *  
*********************************************************************
*********************************************************************
* 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+ *  
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+133d13 )  
 
Followup: MachineOwner  
--------- ( nt+133d13 )  
 
 
le fichier ntoskrnl.exe serait la cause, comment faire pour solutionner mon probléme  
 
d'avance merci  
 
Followup: MachineOwner  
 
Crash dump directory: C:\Windows\Minidump  
 
Crash dumps are enabled on your computer.  
 
 
On Tue 17/11/2009 21:21:07 your computer crashed  
This was likely caused by the following module: ntoskrnl.exe  
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF2, 0x0, 0xFFFFF80002D97D13, 0x0)  
Error: PAGE_FAULT_IN_NONPAGED_AREA  
Dump file: C:\Windows\Minidump\Mini111709-02.dmp  
file path: C:\Windows\system32\ntoskrnl.exe  
product: Microsoft® Windows® Operating System  
company: Microsoft Corporation  
description: NT Kernel & System  
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.  
 
 
 
On Tue 17/11/2009 20:29:06 your computer crashed  
This was likely caused by the following module: ntoskrnl.exe  
Bugcheck code: 0x50 (0xFFFFFB8009CA3670, 0x0, 0xFFFFF80002E9410F, 0x7)  
Error: PAGE_FAULT_IN_NONPAGED_AREA  
Dump file: C:\Windows\Minidump\Mini111709-01.dmp  
file path: C:\Windows\system32\ntoskrnl.exe  
product: Microsoft® Windows® Operating System  
company: Microsoft Corporation  
description: NT Kernel & System  
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time
---------

mood
Publicité
Posté le 19-11-2009 à 19:37:32  profilanswer
 


Aller à :
Ajouter une réponse
  FORUM HardWare.fr
  Windows & Software
  Win Vista

  bsod vista 64bits

 

Sujets relatifs
Pilotes SCSI Tekram XP sous Vista 32Trouver image dvd Vista
Quel espace dsque pour VistaErreur "Appcrash" sur Vista
Probléme centre de sécurité windows sous vistaQuestion mise à jour vista vers seven
BSOD sous WIN7 64bOffre Microsoft : Vista SP1 vers Windows 7
BSOD + dump[BSOD] vista 64bits & 32bits "driver irql not less..."
Plus de sujets relatifs à : bsod vista 64bits


Copyright © 1997-2022 Hardware.fr SARL (Signaler un contenu illicite / Données personnelles) / Groupe LDLC / Shop HFR