Hallo
Mein Rechner Marke Eigenbau:
Board: Asrock 4CoreDual-Sata2
CPU: Intel Core 2 Quad Q6700
System: Vista Ultimate
...stürzt alle Nase lang (manchmal 3 mal am Tag, manchmal 3 Wochen gar nicht) mit einem Bluescreen ab.
Gestern das neuste Bios drauf gemacht, eine als problematisch eingestufte Soundkarte samt Treiber entfernt, mit TuneUp registy defragmentiert und gereinigt, HD auf Fehler überprüft, den neusten Chipsatz-Treiber installiert,
scheint jedoch nicht das Bluescreen-Problem behoben zu haben.
Habe jetzt mal das Minidump file ausgelesen, mit dessen Fehlerbeschreibung ich aber nun wirklich nichts anfangen kann.
Jemand da, der das Ding versteht und das Wesentliche in nachvollziehbares Deutsch transformieren kann?
Schonmal im Voraus vielen Dank für die Mühe! :-)
Hier das File:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini013110-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 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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x81852000 PsLoadedModuleList = 0x8195f930
Debug session time: Sun Jan 31 19:43:37.535 2010 (GMT+1)
System Uptime: 0 days 9:41:46.071
*********************************************************************
* 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 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
..........
Unable to load image \SystemRoot\system32\drivers\NETIO.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETIO.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {140932a9, 2, 0, 89dad968}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : NETIO.SYS ( NETIO+1968 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 140932a9, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 89dad968, address which referenced memory
Debugging Details:
------------------
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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: NETIO
FAULTING_MODULE: 81852000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0209d
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
140932a9
CURRENT_IRQL: 0
FAULTING_IP:
NETIO+1968
89dad968 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 89dad968 to 818accb9
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
87a4e98c 89dad968 badb0d00 140932a1 87a4e9a8 nt+0x5acb9
87a4ea0c 89dad90a 84e4f148 87a4ea68 b9f4f68a NETIO+0x1968
87a4ea30 89e22504 84e4f148 b9f4f68a 87a4ea68 NETIO+0x190a
87a4ea80 89e22d9e b9f4f68a 00000000 00000000 tcpip+0x3b504
87a4eaa8 89e230a6 84fc1100 00000000 8466caf0 tcpip+0x3bd9e
87a4ead0 89e21308 8466caf0 00000000 84e32f40 tcpip+0x3c0a6
87a4eb18 89e22b93 00000000 848327c8 86901370 tcpip+0x3a308
87a4eb4c 9085e1c9 00fbf8f0 87a4eb78 17203dda tcpip+0x3bb93
87a4ec1c 90859040 84b3dd10 85fd96d8 87a4ec44 afd+0x231c9
87a4ec2c 8189817f 85fd96d8 86901370 86901370 afd+0x1e040
87a4ec44 81a44e8a 84b3dd10 86901370 8690144c nt+0x4617f
87a4ec64 81a4f9cb 85fd96d8 84b3dd10 03b16000 nt+0x1f2e8a
87a4ed00 81a8183e 85fd96d8 86901370 00000000 nt+0x1fd9cb
87a4ed34 818a997a 000004b0 00000000 00000000 nt+0x22f83e
87a4ed64 77485e74 badb0d00 0890f030 00000000 nt+0x5797a
87a4ed68 badb0d00 0890f030 00000000 00000000 0x77485e74
87a4ed6c 0890f030 00000000 00000000 00000000 0xbadb0d00
87a4ed70 00000000 00000000 00000000 00000000 0x890f030
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO+1968
89dad968 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: NETIO+1968
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: NETIO.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> lmvm NETIO
start end module name
89dac000 89de7000 NETIO T (no symbols)
Loaded symbol image file: NETIO.SYS
Image path: \SystemRoot\system32\drivers\NETIO.SYS
Image name: NETIO.SYS
Timestamp: Sat Apr 11 06:46:21 2009 (49E0209D)
CheckSum: 0003BC94
ImageSize: 0003B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
1: kd> lmvm nt
start end module name
81852000 81bfd000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: \SystemRoot\system32\ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Tue Aug 04 11:26:05 2009 (4A77FEAD)
CheckSum: 0036E01D
ImageSize: 003AB000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
chrissv2
kds
shrek3
