Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\010511-23337-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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 = 0x82e04000 PsLoadedModuleList = 0x82f4c810
Debug session time: Wed Jan 5 21:24:51.584 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:26.254
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 83036591, 8d6c58f0, 0}
Probably caused by : ntkrpamp.exe ( nt!ObpWaitForMultipleObjects+14e )
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: c0000005, The exception code that was not handled
Arg2: 83036591, The address that the exception occurred at
Arg3: 8d6c58f0, 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!ObpWaitForMultipleObjects+14e
83036591 8b4110 mov eax,dword ptr [ecx+10h]
TRAP_FRAME: 8d6c58f0 -- (.trap 0xffffffff8d6c58f0)
ErrCode = 00000000
eax=00000000 ebx=87f0d960 ecx=00000000 edx=87fa6e88 esi=87fa6e88 edi=980f7650
eip=83036591 esp=8d6c5964 ebp=8d6c5bc8 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!ObpWaitForMultipleObjects+0x14e:
83036591 8b4110 mov eax,dword ptr [ecx+10h] ds:0023:00000010=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 83036412 to 83036591
STACK_TEXT:
8d6c5bc8 83036412 00000024 8d6c5c18 00000001 nt!ObpWaitForMultipleObjects+0x14e
8d6c5d18 82e4744a 00000024 00280e80 00000001 nt!NtWaitForMultipleObjects+0xcd
8d6c5d18 76e264f4 00000024 00280e80 00000001 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0087f9c0 00000000 00000000 00000000 00000000 0x76e264f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ObpWaitForMultipleObjects+14e
83036591 8b4110 mov eax,dword ptr [ecx+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ObpWaitForMultipleObjects+14e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0x8E_nt!ObpWaitForMultipleObjects+14e
BUCKET_ID: 0x8E_nt!ObpWaitForMultipleObjects+14e
Followup: MachineOwner
---------