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: ffffffffc0000006, The exception code that was not handled
Arg2: fffff80002d76b2a, The address that the exception occurred at
Arg3: fffff880009a96c8, Exception Record Address
Arg4: fffff880009a8f20, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000076f1020c
EXCEPTION_PARAMETER3: 00000000c000000e
IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
BUGCHECK_STR: 0x7E
EXCEPTION_STR: 0xc0000006_c000000e
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
DPC_STACK_BASE: FFFFF880009B0FB0
FOLLOWUP_IP:
+3a
00000000`76f1020c ?? ???
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware_disk
IMAGE_NAME: hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0x7E_IMAGE_hardware_disk
BUCKET_ID: X64_0x7E_IMAGE_hardware_disk