*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck E1, {fffff8000337bd50, 2, fffffa800935fac0, fffffa800935fac0}
Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WORKER_THREAD_RETURNED_AT_BAD_IRQL (e1)
Arguments:
Arg1: fffff8000337bd50, address of worker routine (do ln on this to find guilty driver)
Arg2: 0000000000000002, IRQL returned at (should have been 0, but isn't).
Arg3: fffffa800935fac0, workitem parameter
Arg4: fffffa800935fac0, workitem address
Debugging Details:
------------------
FAULTING_IP:
nt!IopProcessWorkItem+0
fffff800`0337bd50 fff3 push rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xE1
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff8000310bef8 to fffff80003083c00
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!IopProcessWorkItem+0
fffff800`0337bd50 fff3 push rbx
SYMBOL_NAME: nt!IopProcessWorkItem+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5147d9c6
FAILURE_BUCKET_ID: X64_0xE1_nt!IopProcessWorkItem+0
BUCKET_ID: X64_0xE1_nt!IopProcessWorkItem+0
Followup: MachineOwner
---------