Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\060210-61245-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x83c37000 PsLoadedModuleList = 0x83d7f810
Debug session time: Wed Jun 2 09:12:17.889 2010 (UTC + 8:00)
System Uptime: 0 days 0:09:51.276
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 83e6dd63, 9caf5cb0, 0}
Probably caused by : ntkrpamp.exe ( nt!CmpParseKey+80e )
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: 83e6dd63, The address that the exception occurred at
Arg3: 9caf5cb0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
nt!CmpParseKey+80e
83e6dd63 8b0f mov ecx,dword ptr [edi]
TRAP_FRAME: 9caf5cb0 -- (.trap 0xffffffff9caf5cb0)
ErrCode = 00000000
eax=00000100 ebx=83e6844f ecx=83e6855b edx=746c6644 esi=073dfea8 edi=00000af0
eip=83e6dd63 esp=9caf5d24 ebp=9caf5d34 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
nt!CmpParseKey+0x80e:
83e6dd63 8b0f mov ecx,dword ptr [edi] ds:0023:00000af0=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: iexplore.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 77a064f4 to 83e6dd63
STACK_TEXT:
9caf5d34 77a064f4 badb0d00 073dfe9c 00000000 nt!CmpParseKey+0x80e
WARNING: Frame IP not in any known module. Following frames may be wrong.
9caf5d38 badb0d00 073dfe9c 00000000 00000000 0x77a064f4
9caf5d3c 073dfe9c 00000000 00000000 00000000 0xbadb0d00
9caf5d40 00000000 00000000 00000000 00000000 0x73dfe9c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpParseKey+80e
83e6dd63 8b0f mov ecx,dword ptr [edi]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpParseKey+80e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007
FAILURE_BUCKET_ID: 0x8E_nt!CmpParseKey+80e
BUCKET_ID: 0x8E_nt!CmpParseKey+80e
Followup: MachineOwner
---------
