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: 8053cc71, The address that the exception occurred at
Arg3: a89e1c90, Trap Frame
Arg4: 00000000
STACK_TEXT:
a89e1d50 805426cc 0000023c 00000000 a89e1d1c nt!_SEH_epilog+0x6
a89e1d50 7c92e514 0000023c 00000000 a89e1d1c nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
01c6feec 00000000 00000000 00000000 00000000 0x7c92e514