Witam!
Mam problem zwazany z plikiem, ktory podalem w temacie.
Po prostu siedze sobie przy kompie i nagle blue screen z bledem "*STOP* 0x0000008E" Nawet wyskoczylo to, gdy komputer stal wlaczony, ale przez nikogo nie uzywany. wrzucilem plik minidump, ktory opisuje ten blad do Windbg i otrzymalem to:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini042206-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 2
*** 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Apr 22 21:28:07.671 2006 (GMT+2)
System Uptime: 0 days 1:05:58.259
*********************************************************************
* 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 2
*** 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 sptd.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, f84ab9ac, f62f5ac0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : sptd.sys ( sptd+179ac )
Followup: MachineOwner
---------
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: f84ab9ac, The address that the exception occurred at
Arg3: f62f5ac0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: sptd
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4391a4df
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo
FAULTING_IP:
sptd+179ac
f84ab9ac 0000 add [eax],al
TRAP_FRAME: f62f5ac0 -- (.trap fffffffff62f5ac0)
ErrCode = 00000000
eax=00000000 ebx=00000008 ecx=00000000 edx=e101e2de esi=e101e2d8 edi=f62f5cdc
eip=f84ab9ac esp=f62f5b34 ebp=f62f5be4 iopl=0 nv up ei ng nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
sptd+0x179ac:
f84ab9ac 0000 add [eax],al ds:0023:00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 805c4b54 to f84ab9ac
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f62f5be4 805c4b54 00000000 00000508 f62f5cdc sptd+0x179ac
f62f5c04 806380ab 00000000 00000508 f62f5cdc nt+0xedb54
f62f5d08 805c4905 7c810867 00000000 00000000 nt+0x1610ab
f62f5d50 80540fa2 00000000 7c810867 00000001 nt+0xed905
00000000 00000000 00000000 00000000 00000000 nt+0x69fa2
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
sptd+179ac
f84ab9ac 0000 add [eax],al
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: sptd+179ac
IMAGE_NAME: sptd.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Czytalem w necie o tym pliku i jest to sterownik DAEMON Tools (ja mam wersje 3.47). NIGDY nie mialem jeszcze takiego bledu.
Jakby co to mam Windowsa Xp SP2(wszystkie update'y wgrane)
Mam problem zwazany z plikiem, ktory podalem w temacie.
Po prostu siedze sobie przy kompie i nagle blue screen z bledem "*STOP* 0x0000008E" Nawet wyskoczylo to, gdy komputer stal wlaczony, ale przez nikogo nie uzywany. wrzucilem plik minidump, ktory opisuje ten blad do Windbg i otrzymalem to:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini042206-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 2
*** 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Apr 22 21:28:07.671 2006 (GMT+2)
System Uptime: 0 days 1:05:58.259
*********************************************************************
* 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 2
*** 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 sptd.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, f84ab9ac, f62f5ac0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : sptd.sys ( sptd+179ac )
Followup: MachineOwner
---------
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: f84ab9ac, The address that the exception occurred at
Arg3: f62f5ac0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: sptd
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4391a4df
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo
FAULTING_IP:
sptd+179ac
f84ab9ac 0000 add [eax],al
TRAP_FRAME: f62f5ac0 -- (.trap fffffffff62f5ac0)
ErrCode = 00000000
eax=00000000 ebx=00000008 ecx=00000000 edx=e101e2de esi=e101e2d8 edi=f62f5cdc
eip=f84ab9ac esp=f62f5b34 ebp=f62f5be4 iopl=0 nv up ei ng nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
sptd+0x179ac:
f84ab9ac 0000 add [eax],al ds:0023:00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 805c4b54 to f84ab9ac
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f62f5be4 805c4b54 00000000 00000508 f62f5cdc sptd+0x179ac
f62f5c04 806380ab 00000000 00000508 f62f5cdc nt+0xedb54
f62f5d08 805c4905 7c810867 00000000 00000000 nt+0x1610ab
f62f5d50 80540fa2 00000000 7c810867 00000001 nt+0xed905
00000000 00000000 00000000 00000000 00000000 nt+0x69fa2
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
sptd+179ac
f84ab9ac 0000 add [eax],al
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: sptd+179ac
IMAGE_NAME: sptd.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Czytalem w necie o tym pliku i jest to sterownik DAEMON Tools (ja mam wersje 3.47). NIGDY nie mialem jeszcze takiego bledu.
Jakby co to mam Windowsa Xp SP2(wszystkie update'y wgrane)
Pozdramiam
