BugCheck 1000007E, {c0000005, 89dfb32c, 80fb6aec, 80fb66d0}
Probably caused by : rdyboost.sys ( rdyboost!SmdRBReadWriteCompletion+c )
Followup: MachineOwner
---------
0: kd> !analyze -v;r;kv;lmtn;lmtsmn
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 89dfb32c, The address that the exception occurred at
Arg3: 80fb6aec, Exception Record Address
Arg4: 80fb66d0, Context Record Address
Quote