Is the problem the memory? or Driver problem?
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [G:\WINDOWS\Minidump\Mini051709-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sun May 17 10:12:59.265 2009 (GMT+1)
System Uptime: 0 days 0:00:41.843
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp 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, 80565a41, eb424a34, 0}
Probably caused by : ntoskrnl.exe ( nt!ObpParseSymbolicLink+241 )
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: 80565a41, The address that the exception occurred at
Arg3: eb424a34, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!ObpParseSymbolicLink+241
80565a41 66837c41fe5c cmp word ptr [ecx+eax*2-2],5Ch
TRAP_FRAME: eb424a34 -- (.trap 0xffffffffeb424a34)
ErrCode = 00000000
eax=00000017 ebx=eb424b38 ecx=61ac6aa0 edx=00000000 esi=e1ac46b0 edi=0000002e
eip=80565a41 esp=eb424aa8 ebp=eb424af4 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ObpParseSymbolicLink+0x241:
80565a41 66837c41fe5c cmp word ptr [ecx+eax*2-2],5Ch ds:0023:61ac6acc=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 80563fec to 80565a41
STACK_TEXT:
eb424af4 80563fec e1ac46a8 00000000 85857600 nt!ObpParseSymbolicLink+0x241
eb424b7c 805684da 00000000 eb424bbc 00000040 nt!ObpLookupObjectName+0x56a
eb424bd0 805745a3 00000000 00000000 00000001 nt!ObOpenObjectByName+0xeb
eb424d54 804de7ec 0173f208 0173f1e0 0173f234 nt!NtQueryAttributesFile+0xf1
eb424d54 7c90e514 0173f208 0173f1e0 0173f234 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0173f234 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObpParseSymbolicLink+241
80565a41 66837c41fe5c cmp word ptr [ecx+eax*2-2],5Ch
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObpParseSymbolicLink+241
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 498c1a18
FAILURE_BUCKET_ID: 0x8E_nt!ObpParseSymbolicLink+241
BUCKET_ID: 0x8E_nt!ObpParseSymbolicLink+241
Followup: MachineOwner
---------
Back to top
