Hallo zusammen,
bei der Fehlersuche in Google bin ich auf dieses Forum hier gestoßen. Da ich gesehen habe, dass hier fachmännische Forenuser unterwegs sind, hoffe ich, dass ihr mir bei meinem BSOD-Problem ebenfalls helfen könnt.
Vorab mein System:
Asus M4a79t Deluxe (BIOS wurde gestern auf die neuste Version geflasht)
Phenom 965BE (nicht übertaktet)
2x Samsung SpinPoint F3 HD502HJ 500GB (nicht im RAID)
Powercolor HD5770 1GB (Gestern aktueller ATI Treiber installiert)
2x2GB GEIL DDR3 1333 (Aus der QVL von ASUS; im BIOS auf 1,5V und 1333Mhz - wie vorgegeben - eingestellt)
LC-Power 650Watt (Bei voller Belastung von CPU/GPU bleiben die Spannungen über 12V bzw 5V)
Das System ist etwas mehr als 2 Jahre alt und lief immer problemlos. Bis dato keine BSODs und bei allen Anwendungen eine gute Performance!
Seit einer Woche bekomme ich jedoch in unregelmäßigen Abständen BSODs verschiedendster Art. Es scheint auch unabhängig von der Belastung zu sein, da der Rechner sowohl bei 3D-Spielen als auch im idle auf dem Desktop abschmiert.
Die alten Crashdumps kann ich leider nicht komplett posten, da ich Windows7x64 inzwischen neu aufgesetzt habe. Der Grund dafür war, dass nach dem fünften BSOD ein booten nicht mehr möglich war. Es tauchte immer ein Fehler mit der Datei ntfs.sys auf. Selbst die Reparaturfunktion von Windows scheiterte an diesem Fehler. Der Abgesicherte Modus ebenfalls, da Windows schon vor dem booten den BSOD mit dieser Datei brachte! Daraufhin formatierte ich die System-HDD mit Hilfe der "Ultimatebootcd" und installierte Win7 neu. Des Weiteren ließ ich 2h beide RAM-Riegel gleichzeitig von Memtest86 überprüfen. Der Test erbrachte keine Fehler. Chkdsk /f war ebenfalls ohne Fehlermeldungen.
Die handnotierten Crashcodes und Fehlermeldungen vor dem Neuaufsetzen lauteten in etwa so:
"Video scheduler encountered an unexpected fatal error"
"Bugcode_USB_Driver"
"NTFS.SYS" + STOP:0x00000050
"Page_Fault_in_unpaged_area"
"Win7_Driver_Fault" + 0xFE000000
Nach der Neuinstallation von Win7 lief der PC zwei Tage problemlos. Ich ließ testweise Prime95 2h laufen. CPU-Temperaturen blieben unter 50°C und es kam zu keinen Abstürzen. Ferner installierte ich alle aktuellen Treiber von der ASUS-HP + ATI-Treiber
Heute passierte es dann wieder. Den Crashdump kann ich dieses mal zum Glück posten:
Ich habe bereits viel gegoogelt. Leider werde ich jedoch aus den ganzen Fehlermeldungen nicht schlau.
Ich hoffe ihr könnt mir bei der Analyse weiter helfen. Bei zukünftigen BSODs werde ich auch die Crashdumps sofort posten!
Vielen Dank schon mal für die Mühe!
bei der Fehlersuche in Google bin ich auf dieses Forum hier gestoßen. Da ich gesehen habe, dass hier fachmännische Forenuser unterwegs sind, hoffe ich, dass ihr mir bei meinem BSOD-Problem ebenfalls helfen könnt.
Vorab mein System:
Asus M4a79t Deluxe (BIOS wurde gestern auf die neuste Version geflasht)
Phenom 965BE (nicht übertaktet)
2x Samsung SpinPoint F3 HD502HJ 500GB (nicht im RAID)
Powercolor HD5770 1GB (Gestern aktueller ATI Treiber installiert)
2x2GB GEIL DDR3 1333 (Aus der QVL von ASUS; im BIOS auf 1,5V und 1333Mhz - wie vorgegeben - eingestellt)
LC-Power 650Watt (Bei voller Belastung von CPU/GPU bleiben die Spannungen über 12V bzw 5V)
Das System ist etwas mehr als 2 Jahre alt und lief immer problemlos. Bis dato keine BSODs und bei allen Anwendungen eine gute Performance!
Seit einer Woche bekomme ich jedoch in unregelmäßigen Abständen BSODs verschiedendster Art. Es scheint auch unabhängig von der Belastung zu sein, da der Rechner sowohl bei 3D-Spielen als auch im idle auf dem Desktop abschmiert.
Die alten Crashdumps kann ich leider nicht komplett posten, da ich Windows7x64 inzwischen neu aufgesetzt habe. Der Grund dafür war, dass nach dem fünften BSOD ein booten nicht mehr möglich war. Es tauchte immer ein Fehler mit der Datei ntfs.sys auf. Selbst die Reparaturfunktion von Windows scheiterte an diesem Fehler. Der Abgesicherte Modus ebenfalls, da Windows schon vor dem booten den BSOD mit dieser Datei brachte! Daraufhin formatierte ich die System-HDD mit Hilfe der "Ultimatebootcd" und installierte Win7 neu. Des Weiteren ließ ich 2h beide RAM-Riegel gleichzeitig von Memtest86 überprüfen. Der Test erbrachte keine Fehler. Chkdsk /f war ebenfalls ohne Fehlermeldungen.
Die handnotierten Crashcodes und Fehlermeldungen vor dem Neuaufsetzen lauteten in etwa so:
"Video scheduler encountered an unexpected fatal error"
"Bugcode_USB_Driver"
"NTFS.SYS" + STOP:0x00000050
"Page_Fault_in_unpaged_area"
"Win7_Driver_Fault" + 0xFE000000
Nach der Neuinstallation von Win7 lief der PC zwei Tage problemlos. Ich ließ testweise Prime95 2h laufen. CPU-Temperaturen blieben unter 50°C und es kam zu keinen Abstürzen. Ferner installierte ich alle aktuellen Treiber von der ASUS-HP + ATI-Treiber
Heute passierte es dann wieder. Den Crashdump kann ich dieses mal zum Glück posten:
Code:
Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\051312-17253-01.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 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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e9f670
Debug session time: Sun May 13 18:30:15.259 2012 (UTC + 2:00)
System Uptime: 0 days 6:42:01.398
*********************************************************************
* 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 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
................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
...Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002e069bc, 0, ffffffffffffffff}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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!_EXCEPTION_POINTERS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 : ntoskrnl.exe ( nt+1ab9bc )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002e069bc, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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!_EXCEPTION_POINTERS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002c5b000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4f76721c
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt+1ab9bc
fffff800`02e069bc 4c8b02 mov r8,qword ptr [rdx]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
BUGCHECK_STR: 0x1e_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ce2cf9 to fffff880040037f2
STACK_TEXT:
fffff800`00b9cc98 fffff800`02ce2cf9 : 00000000`0032d686 fffffa80`05131698 fffff800`02e5acc0 00000000`00000001 : 0xfffff880`040037f2
fffff800`00b9cca0 00000000`0032d686 : fffffa80`05131698 fffff800`02e5acc0 00000000`00000001 fffff800`02e4ce80 : nt+0x87cf9
fffff800`00b9cca8 fffffa80`05131698 : fffff800`02e5acc0 00000000`00000001 fffff800`02e4ce80 fffff800`02ce49b7 : <Unloaded_Unknown_Module_00000000`00000000>+0x32d686
fffff800`00b9ccb0 fffff800`02e5acc0 : 00000000`00000001 fffff800`02e4ce80 fffff800`02ce49b7 00000012`b629968b : 0xfffffa80`05131698
fffff800`00b9ccb8 00000000`00000001 : fffff800`02e4ce80 fffff800`02ce49b7 00000012`b629968b 00000012`001797f9 : nt+0x1ffcc0
fffff800`00b9ccc0 fffff800`02e4ce80 : fffff800`02ce49b7 00000012`b629968b 00000012`001797f9 00000012`b629968b : <Unloaded_Unknown_Module_00000000`00000000>+0x1
fffff800`00b9ccc8 fffff800`02ce49b7 : 00000012`b629968b 00000012`001797f9 00000012`b629968b 00000000`000000f9 : nt+0x1f1e80
fffff800`00b9ccd0 00000012`b629968b : 00000012`001797f9 00000012`b629968b 00000000`000000f9 fffffa80`05131600 : nt+0x899b7
fffff800`00b9ccd8 00000012`001797f9 : 00000012`b629968b 00000000`000000f9 fffffa80`05131600 400000c2`400000c1 : 0x12`b629968b
fffff800`00b9cce0 00000012`b629968b : 00000000`000000f9 fffffa80`05131600 400000c2`400000c1 fffff800`400000c3 : 0x12`001797f9
fffff800`00b9cce8 00000000`000000f9 : fffffa80`05131600 400000c2`400000c1 fffff800`400000c3 00000010`db8f272a : 0x12`b629968b
fffff800`00b9ccf0 fffffa80`05131600 : 400000c2`400000c1 fffff800`400000c3 00000010`db8f272a 00000000`00000000 : <Unloaded_Unknown_Module_00000000`00000000>+0xf9
fffff800`00b9ccf8 400000c2`400000c1 : fffff800`400000c3 00000010`db8f272a 00000000`00000000 fffff800`02cdd51d : 0xfffffa80`05131600
fffff800`00b9cd00 fffff800`400000c3 : 00000010`db8f272a 00000000`00000000 fffff800`02cdd51d 00000000`00000010 : 0x400000c2`400000c1
fffff800`00b9cd08 00000010`db8f272a : 00000000`00000000 fffff800`02cdd51d 00000000`00000010 00000000`00200247 : 0xfffff800`400000c3
fffff800`00b9cd10 00000000`00000000 : fffff800`02cdd51d 00000000`00000010 00000000`00200247 fffff800`00b9cd40 : 0x10`db8f272a
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt+1ab9bc
fffff800`02e069bc 4c8b02 mov r8,qword ptr [rdx]
SYMBOL_NAME: nt+1ab9bc
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------Ich habe bereits viel gegoogelt. Leider werde ich jedoch aus den ganzen Fehlermeldungen nicht schlau.
Ich hoffe ihr könnt mir bei der Analyse weiter helfen. Bei zukünftigen BSODs werde ich auch die Crashdumps sofort posten!
Vielen Dank schon mal für die Mühe!
Zuletzt bearbeitet:
:
