Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c45000 PsLoadedModuleList = 0x82d8d810
Debug session time: Sun Jan 16 05:11:32.560 2011 (GMT-5)
System Uptime: 0 days 1:45:47.230
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 82e7cb4b, a19a6958, 0}
Probably caused by : ntkrpamp.exe ( nt!CmpParseCacheLookup+24 )
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: 82e7cb4b, The address that the exception occurred at
Arg3: a19a6958, 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!CmpParseCacheLookup+24
82e7cb4b 8b7304 mov esi,dword ptr [ebx+4]
TRAP_FRAME: a19a6958 -- (.trap 0xffffffffa19a6958)
ErrCode = 00000000
eax=82771f08 ebx=00000000 ecx=00000000 edx=00000001 esi=c0000034 edi=00000000
eip=82e7cb4b esp=a19a69cc ebp=a19a6b48 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!CmpParseCacheLookup+0x24:
82e7cb4b 8b7304 mov esi,dword ptr [ebx+4] ds:0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: sidebar.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82e6626b to 82e7cb4b
STACK_TEXT:
a19a6b48 82e6626b 8c00ad50 85476980 889c1d20 nt!CmpParseCacheLookup+0x24
a19a6bc4 82e8c2d9 00000000 a19a6c18 00000040 nt!ObpLookupObjectName+0x4fa
a19a6c20 82e83a24 020ae060 85476980 ffffff01 nt!ObOpenObjectByName+0x165
a19a6d00 82e7e777 020ae5c4 00000001 020ae060 nt!CmOpenKey+0x1f4
a19a6d1c 82c8844a 020ae5c4 00000001 020ae060 nt!NtOpenKeyEx+0x18
a19a6d1c 771264f4 020ae5c4 00000001 020ae060 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
020ae294 00000000 00000000 00000000 00000000 0x771264f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpParseCacheLookup+24
82e7cb4b 8b7304 mov esi,dword ptr [ebx+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpParseCacheLookup+24
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0x8E_nt!CmpParseCacheLookup+24
BUCKET_ID: 0x8E_nt!CmpParseCacheLookup+24
Followup: MachineOwner
---------
Debug session time: Sun Jan 16 05:16:07.596 2011 (GMT-5)
System Uptime: 0 days 0:00:19.266
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 62e20bfe, 9e3f99ec, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
*** Possible invalid call from 82e2feda ( nt!ObCheckObjectAccess+0x62 )
*** Expected target 82e20bfe ( nt!SeLockSubjectContext+0x0 )
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: 62e20bfe, The address that the exception occurred at
Arg3: 9e3f99ec, 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:
+5e62952f017fdd60
62e20bfe ?? ???
TRAP_FRAME: 9e3f99ec -- (.trap 0xffffffff9e3f99ec)
ErrCode = 00000010
eax=00000000 ebx=85349b98 ecx=00000004 edx=9128c018 esi=9e3f9b48 edi=9e3f9b64
eip=62e20bfe esp=9e3f9a60 ebp=9e3f9a84 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
62e20bfe ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82e2fedf to 62e20bfe
POSSIBLE_INVALID_CONTROL_TRANSFER: from 82e2feda to 82e20bfe
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
9e3f9a5c 82e2fedf 9e3f9b64 9e3f9b48 9e3f9cec 0x62e20bfe
9e3f9a84 82e2fe6a 91200598 9e3f9b48 00000001 nt!ObCheckObjectAccess+0x67
9e3f9aa8 82e227ac 00000001 9e3f9b01 00000000 nt!ObpGrantAccess+0x5f
9e3f9b08 82e7b06e 00000001 91200598 00000000 nt!ObpCreateHandle+0x8b
9e3f9c88 82e7b0d3 91200598 00000000 00000000 nt!ObOpenObjectByPointerWithTag+0xc1
9e3f9cb0 82e3c172 91200598 00000000 00000000 nt!ObOpenObjectByPointer+0x24
9e3f9d1c 82c4344a ffffffff 00000008 00000000 nt!NtOpenProcessTokenEx+0xb4
9e3f9d1c 772b64f4 ffffffff 00000008 00000000 nt!KiFastCallEntry+0x12a
001cec40 00000000 00000000 00000000 00000000 0x772b64f4
STACK_COMMAND: .trap 0xffffffff9e3f99ec ; kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
[B]BUCKET_ID: CPU_CALL_ERROR[/B]
Followup: MachineOwner
---------
*** Possible invalid call from 82e2feda ( nt!ObCheckObjectAccess+0x62 )
*** Expected target 82e20bfe ( nt!SeLockSubjectContext+0x0 )