Posiadam od wczoraj nowa płyte główna ASROCK P45 ,KART GRAFICZNA GF 7300GT,PAMIEC DDR3 .Pojawia mi sie co jakiś czas niebieski ekran i reset kompa
Kod błędu 100000d1, parametr 1 b1ed7000, parametr 2 00000002, parametr 3 00000000, parametr 4 b4ffc0d8.
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C]
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 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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Dec 29 10:09:18.281 2009 (GMT+1)
System Uptime: 0 days 1:00:30.987
*********************************************************************
* 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 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 viahduaa.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for viahduaa.sys
*** ERROR: Module load completed but symbols could not be loaded for viahduaa.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {b1ed7000, 2, 0, b4ffc0d8}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for portcls.sys
*** ERROR: Module load completed but symbols could not be loaded for portcls.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
*************************************************************************
*** ***
*** ***
*** 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 : viahduaa.sys ( viahduaa+280d8 )
Followup: MachineOwner
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.
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a24e854
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
b3129000
CURRENT_IRQL: 2
FAULTING_IP:
viahduaa+280d8
b50130d8 3b0f cmp ecx,dword ptr [edi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from b501634c to b50130d8
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b40969a0 b501634c b3128fe0 00000020 b3128fe0 viahduaa+0x280d8
b40969c4 b4fce676 8981f5d0 b3128fe0 b30e8c00 viahduaa+0x2b34c
b40969ec b4fce945 b4096a01 00000020 b4096a1c portcls+0x7676
b4096a2c b4fce11b 0002bd60 899327c8 86f2b120 portcls+0x7945
b4096a44 b4fdd51f 88e26e34 86fcf008 00000000 portcls+0x711b
b4096a7c b4fe461a 00000000 86fcf008 00000000 portcls+0x1651f
b4096ab0 b4fd774d 00000000 89841ad0 86fcf008 portcls+0x1d61a
b4096acc b7349f1f 89841ad0 86fcf008 b4096af4 portcls+0x1074d
b4096adc b4fd78c0 89841ad0 86fcf008 89841b88 ks+0x8f1f
b4096af4 b4fd7881 89841ad0 86fcf008 b4096b34 portcls+0x108c0
b4096b04 b5131501 89841ad0 86fcf008 895c7000 portcls+0x10881
b4096b34 804ef18f 89841ad0 86fcf008 c0000120 viahduaa+0x146501
00000000 00000000 00000000 00000000 00000000 nt+0x1818f
STACK_COMMAND: kb
FOLLOWUP_IP:
viahduaa+280d8
b50130d8 3b0f cmp ecx,dword ptr [edi]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: viahduaa+280d8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: viahduaa
IMAGE_NAME: viahduaa.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
0: kd> lmvm nt
start end module name
804d7000 806e4000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Sun Apr 13 20:31:06 2008 (4802516A)
CheckSum: 001FD544
ImageSize: 0020D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm viahduaa
start end module name
b4feb000 b513a900 viahduaa T (no symbols)
Loaded symbol image file: viahduaa.sys
Image path: viahduaa.sys
Image name: viahduaa.sys
Timestamp: Tue Jun 02 10:52:36 2009 (4A24E854)
CheckSum: 00156D7B
ImageSize: 0014F900
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
