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: 912d83b8, The address that the exception occurred at
Arg3: b223bbd0, Exception Record Address
Arg4: b223b7a0, Context Record Address
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
HSX_CNXT+a43b8
912d83b8 c780ebfc010003000000 mov dword ptr [eax+1FCEBh],3
EXCEPTION_RECORD: b223bbd0 -- (.exr 0xffffffffb223bbd0)
ExceptionAddress: 912d83b8 (HSX_CNXT+0x000a43b8)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 0001fceb
Attempt to write to address 0001fceb
CONTEXT: b223b7a0 -- (.cxr 0xffffffffb223b7a0)
eax=00000000 ebx=86e09eb4 ecx=86357800 edx=873be32c esi=86e09dd8 edi=863578b8
eip=912d83b8 esp=b223bc98 ebp=b223bca4 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
HSX_CNXT+0xa43b8:
912d83b8 c780ebfc010003000000 mov dword ptr [eax+1FCEBh],3 ds:0023:0001fceb=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 0001fceb
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81c19470
Unable to read MiSystemVaType memory at 81bef080
0001fceb
FOLLOWUP_IP:
HSX_CNXT+a43b8
912d83b8 c780ebfc010003000000 mov dword ptr [eax+1FCEBh],3
BUGCHECK_STR: AV
LAST_CONTROL_TRANSFER: from 912d8710 to 912d83b8
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b223bca4 912d8710 86357800 86e09dd8 86e09ed0 HSX_CNXT+0xa43b8
b223bccc 81a9c580 86357800 8635f648 86e09dd8 HSX_CNXT+0xa4710
b223bce4 81ad6cb2 b223bd08 912ec843 86357800 nt!IopPoHandleIrp+0x30
b223bcec 912ec843 86357800 86e09dd8 86e09dd8 nt!IoCallDriver+0x10
b223bd08 81a9c9ee 86354ae8 86e09dd8 873be300 modem!ModemPower+0xcf
b223bd74 81a845a5 846b10b0 be177f09 00000000 nt!PopIrpWorker+0x265
b223bdb0 81b35619 81a9c789 846b10b0 00000000 nt!PspSystemThreadStartup+0x4a
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: HSX_CNXT+a43b8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HSX_CNXT
IMAGE_NAME: HSX_CNXT.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45366d81
STACK_COMMAND: .cxr 0xffffffffb223b7a0 ; kb
FAILURE_BUCKET_ID: AV_HSX_CNXT+a43b8
BUCKET_ID: AV_HSX_CNXT+a43b8
