jestem w posiadaniu Della Laptitude E5400 z XP SP3. Od pewnego czasu zaraz po włączeniu wyświetla mi się bsod jak w temacie.
log z WinDbg:
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Administrator\Pulpit\Jakub Jedrzejak\WER060b.dir00\Mini092010-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100427-1636
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Sep 20 15:22:38.992 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:51.746
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 805c3133, 96f2aa48, 0}
Probably caused by : ntkrpamp.exe ( nt!ObInsertObject+1ad )
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: 805c3133, The address that the exception occurred at
Arg3: 96f2aa48, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo
FAULTING_IP:
nt!ObInsertObject+1ad
805c3133 8b4e1c mov ecx,dword ptr [esi+1Ch]
TRAP_FRAME: 96f2aa48 -- (.trap 0xffffffff96f2aa48)
ErrCode = 00000000
eax=96f2abb8 ebx=00000000 ecx=89df3e00 edx=00000000 esi=00000001 edi=00000000
eip=805c3133 esp=96f2aabc ebp=96f2ab8c 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!ObInsertObject+0x1ad:
805c3133 8b4e1c mov ecx,dword ptr [esi+1Ch] ds:0023:0000001d=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: cmd.exe
LAST_CONTROL_TRANSFER: from 805d0e8b to 805c3133
STACK_TEXT:
96f2ab8c 805d0e8b 85b41020 96f2abb8 001f0fff nt!ObInsertObject+0x1ad
96f2ace4 805d11ab 0012f114 001f0fff 00000000 nt!PspCreateProcess+0x635
96f2ad38 8054164c 0012f114 001f0fff 00000000 nt!NtCreateProcessEx+0x77
96f2ad38 7c90e514 0012f114 001f0fff 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f780 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObInsertObject+1ad
805c3133 8b4e1c mov ecx,dword ptr [esi+1Ch]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObInsertObject+1ad
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4bd6e0e8
FAILURE_BUCKET_ID: 0x8E_nt!ObInsertObject+1ad
BUCKET_ID: 0x8E_nt!ObInsertObject+1ad
Followup: MachineOwner
---------Przegooglowałem temat dosyć dokładnie i nie znalazłem rozwiązania. Ma ktoś jakiś pomysł jak naprawić tą sytuację?
