Koledzy z forum mi pomogli. Lecz dzisiaj gdy przeglądałem internet "zawiesił" się komputer i po chwili wyskoczył BSoD.
Zdarzyłem zapamiętać problem Stop 0x0000008E. Poniżej daje debug pliku Minidump.
Oto moje tematy
bezpieczenstwo/wolno-uruchamiajacy-sie-komputer-t16059.html (nie zdążyłem zrobić tylko skanu programem Dr. Web CureIt!. Wszystko resztę zrobiłem i pomogło.)
sprzet-komputerowy/analiza-smart-s-m-a-r-t-dysku-twardego-t30-2175.html (pod koniec strony)
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\mini111211-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sat Nov 12 08:45:19.343 2011 (GMT+1)
System Uptime: 0 days 0:08:14.082
Loading Kernel Symbols
...............................................................
......................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {e0000001, f779f925, b2a7b6e0, 0}
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
Probably caused by : nv4_disp.dll ( nv4_disp+242e0e )
Followup: MachineOwner
---------
0: 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: e0000001, The exception code that was not handled
Arg2: f779f925, The address that the exception occurred at
Arg3: b2a7b6e0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xe0000001 - <Unable to get error code text>
FAULTING_IP:
watchdog!RaiseExceptionInThread+b
f779f925 c3 ret
TRAP_FRAME: b2a7b6e0 -- (.trap 0xffffffffb2a7b6e0)
ESP EDITED! New esp=b2a7ba90
ErrCode = 00000000
eax=e170e800 ebx=0000004f ecx=0000006b edx=000008e8 esi=e2a0c2c0 edi=000011e5
eip=f779f925 esp=b2a7b754 ebp=b2a7bacc iopl=0 nv up ei pl nz na po nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
watchdog!RaiseExceptionInThread+0xb:
f779f925 c3 ret
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: plugin-containe
LAST_CONTROL_TRANSFER: from bf8055b0 to f779f925
STACK_TEXT:
b2a7b750 804e326c b2a7b764 b2a7b7b4 00000001 watchdog!RaiseExceptionInThread+0xb
b2a7bacc bd254e0e e2e43240 e16c2010 bd190d8d nt!ExRaiseStatus+0xca
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 nv4_disp+0x242e0e
STACK_COMMAND: .trap 0xffffffffb2a7b6e0 ; kb
FOLLOWUP_IP:
nv4_disp+242e0e
bd254e0e ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nv4_disp+242e0e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4e390d56
FAILURE_BUCKET_ID: 0x8E_nv4_disp+242e0e
BUCKET_ID: 0x8E_nv4_disp+242e0e
Followup: MachineOwner
---------
0: 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: e0000001, The exception code that was not handled
Arg2: f779f925, The address that the exception occurred at
Arg3: b2a7b6e0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xe0000001 - <Unable to get error code text>
FAULTING_IP:
watchdog!RaiseExceptionInThread+b
f779f925 c3 ret
TRAP_FRAME: b2a7b6e0 -- (.trap 0xffffffffb2a7b6e0)
ESP EDITED! New esp=b2a7ba90
ErrCode = 00000000
eax=e170e800 ebx=0000004f ecx=0000006b edx=000008e8 esi=e2a0c2c0 edi=000011e5
eip=f779f925 esp=b2a7b754 ebp=b2a7bacc iopl=0 nv up ei pl nz na po nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
watchdog!RaiseExceptionInThread+0xb:
f779f925 c3 ret
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: plugin-containe
LAST_CONTROL_TRANSFER: from bf8055b0 to f779f925
STACK_TEXT:
b2a7b750 804e326c b2a7b764 b2a7b7b4 00000001 watchdog!RaiseExceptionInThread+0xb
b2a7bacc bd254e0e e2e43240 e16c2010 bd190d8d nt!ExRaiseStatus+0xca
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 nv4_disp+0x242e0e
STACK_COMMAND: .trap 0xffffffffb2a7b6e0 ; kb
FOLLOWUP_IP:
nv4_disp+242e0e
bd254e0e ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nv4_disp+242e0e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4e390d56
FAILURE_BUCKET_ID: 0x8E_nv4_disp+242e0e
BUCKET_ID: 0x8E_nv4_disp+242e0e
Followup: MachineOwner
---------
0: 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: e0000001, The exception code that was not handled
Arg2: f779f925, The address that the exception occurred at
Arg3: b2a7b6e0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xe0000001 - <Unable to get error code text>
FAULTING_IP:
watchdog!RaiseExceptionInThread+b
f779f925 c3 ret
TRAP_FRAME: b2a7b6e0 -- (.trap 0xffffffffb2a7b6e0)
ESP EDITED! New esp=b2a7ba90
ErrCode = 00000000
eax=e170e800 ebx=0000004f ecx=0000006b edx=000008e8 esi=e2a0c2c0 edi=000011e5
eip=f779f925 esp=b2a7b754 ebp=b2a7bacc iopl=0 nv up ei pl nz na po nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
watchdog!RaiseExceptionInThread+0xb:
f779f925 c3 ret
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: plugin-containe
LAST_CONTROL_TRANSFER: from bf8055b0 to f779f925
STACK_TEXT:
b2a7b750 804e326c b2a7b764 b2a7b7b4 00000001 watchdog!RaiseExceptionInThread+0xb
b2a7bacc bd254e0e e2e43240 e16c2010 bd190d8d nt!ExRaiseStatus+0xca
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 nv4_disp+0x242e0e
STACK_COMMAND: .trap 0xffffffffb2a7b6e0 ; kb
FOLLOWUP_IP:
nv4_disp+242e0e
bd254e0e ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nv4_disp+242e0e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4e390d56
FAILURE_BUCKET_ID: 0x8E_nv4_disp+242e0e
BUCKET_ID: 0x8E_nv4_disp+242e0e
Followup: MachineOwner
---------
Kod: Zaznacz cały
*******************************************************************************
* *
* 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: e0000001, The exception code that was not handled
Arg2: f779f925, The address that the exception occurred at
Arg3: b2a7b6e0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xe0000001 - <Unable to get error code text>
FAULTING_IP:
watchdog!RaiseExceptionInThread+b
f779f925 c3 ret
TRAP_FRAME: b2a7b6e0 -- (.trap 0xffffffffb2a7b6e0)
ESP EDITED! New esp=b2a7ba90
ErrCode = 00000000
eax=e170e800 ebx=0000004f ecx=0000006b edx=000008e8 esi=e2a0c2c0 edi=000011e5
eip=f779f925 esp=b2a7b754 ebp=b2a7bacc iopl=0 nv up ei pl nz na po nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
watchdog!RaiseExceptionInThread+0xb:
f779f925 c3 ret
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: plugin-containe
LAST_CONTROL_TRANSFER: from bf8055b0 to f779f925
STACK_TEXT:
STACK_COMMAND: .trap 0xffffffffb2a7b6e0 ; kb
FOLLOWUP_IP:
nv4_disp+242e0e
bd254e0e ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nv4_disp+242e0e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4e390d56
FAILURE_BUCKET_ID: 0x8E_nv4_disp+242e0e
BUCKET_ID: 0x8E_nv4_disp+242e0e
Followup: MachineOwner
---------
