...
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0x8304e000 PsLoadedModuleList = 0x8318e310
Debug session time: Wed May 28 22:26:46.008 2014 (UTC - 4:00)
System Uptime: 7 days 13:40:25.108
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 830d5dce, 9e912ba0, 0}
Probably caused by : hardware ( nt!IoRetrievePriorityInfo+99 )
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: 830d5dce, The address that the exception occurred at
Arg3: 9e912ba0, 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!IoRetrievePriorityInfo+99
830d5dce d3741b0f sal dword ptr [ebx+ebx+0Fh],cl
TRAP_FRAME: 9e912ba0 -- (.trap 0xffffffff9e912ba0)
ErrCode = 00000002
eax=00000103 ebx=00000000 ecx=85f425f0 edx=00000001 esi=86f2b620 edi=86a623d8
eip=830d5dce esp=9e912c14 ebp=9e912c34 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!IoRetrievePriorityInfo+0x99:
830d5dce d3741b0f sal dword ptr [ebx+ebx+0Fh],cl ds:0023:0000000f=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: iexplore.exe
CURRENT_IRQL: 0
MISALIGNED_IP:
nt!IoRetrievePriorityInfo+99
830d5dce d3741b0f sal dword ptr [ebx+ebx+0Fh],cl
LAST_CONTROL_TRANSFER: from 83254f9f to 830d5dce
STACK_TEXT:
9e912c34 83254f9f 85f425f0 86a623d8 00000000 nt!IoRetrievePriorityInfo+0x99
9e912cd0 8325bf71 85f425f0 86f2b620 00000000 nt!IopXxxControlFile+0x6aa
9e912d04 83083856 00000784 00000edc 00000000 nt!NtDeviceIoControlFile+0x2a
9e912d04 772670f4 00000784 00000edc 00000000 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0cc2e4a0 00000000 00000000 00000000 00000000 0x772670f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!IoRetrievePriorityInfo+99
830d5dce d3741b0f sal dword ptr [ebx+ebx+0Fh],cl
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!IoRetrievePriorityInfo+99
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
Quote