Ostatni błąd:
Sygnatura błędu:
BCCode : 1000008e
BCP1 : C0000005
BCP2 : 80582DFF
BCP3 : B7862A00
BCP4 : 00000000
OSVer : 5_1_2600
SP : 3_0
Product : 256_1
a o to raport:
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini062712-03.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 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: Wed Jun 27 17:26:35.937 2012 (GMT+2)
System Uptime: 0 days 0:10:38.666
*********************************************************************
* 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
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 80582dff, b7862a00, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+abdff )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 80582dff, The address that the exception occurred at
Arg3: b7862a00, Trap Frame
Arg4: 00000000
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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
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: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa3cc43
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo
FAULTING_IP:
nt+abdff
80582dff 8b441089 mov eax,dword ptr [eax+edx-77h]
TRAP_FRAME: b7862a00 -- (.trap 0xffffffffb7862a00)
ErrCode = 00000000
eax=86aeaa98 ebx=86a14608 ecx=804f0f5e edx=86b81300 esi=86b81300 edi=86ea8640
eip=80582dff esp=b7862a74 ebp=b7862b4c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt+0xabdff:
80582dff 8b441089 mov eax,dword ptr [eax+edx-77h] ds:0023:0d66bd21=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 805bf490 to 80582dff
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b7862b4c 805bf490 86f05900 00000000 86aeaa00 nt+0xabdff
b7862bc4 805bba1c 00000000 b7862c04 00000040 nt+0xe8490
b7862c18 80576051 00000000 00000000 a146f001 nt+0xe4a1c
b7862c94 805769c8 022ffea8 40100080 022ffe48 nt+0x9f051
b7862cf0 805790d2 022ffea8 40100080 022ffe48 nt+0x9f9c8
b7862d30 8054168c 022ffea8 40100080 022ffe48 nt+0xa20d2
b7862d64 7c90e514 badb0d00 022ffe10 00000000 nt+0x6a68c
b7862d68 badb0d00 022ffe10 00000000 00000000 0x7c90e514
b7862d6c 022ffe10 00000000 00000000 00000000 0xbadb0d00
b7862d70 00000000 00000000 00000000 00000000 0x22ffe10
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+abdff
80582dff 8b441089 mov eax,dword ptr [eax+edx-77h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+abdff
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------W raporcie było dużo powtarzających się treści więc usunąłem żeby nie był za długi. Jeśli będzie potrzebny pełny raport umieszczę go na forum i jak też będą potrzebne wcześniejsze to też je wkleję. Liczę na szybką pomoc.
Pozdrawiam.
