*******************************************************************************
* *
* 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: d9d1178d, The address that the exception occurred at
Arg3: cc317b70, Exception Record Address
Arg4: cc317750, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
MayPro+178d
d9d1178d 0fb74702 movzx eax,word ptr [edi+2]
EXCEPTION_RECORD: cc317b70 -- (.exr 0xffffffffcc317b70)
ExceptionAddress: d9d1178d (MayPro+0x0000178d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000002
Attempt to read from address 00000002
CONTEXT: cc317750 -- (.cxr 0xffffffffcc317750)
eax=00220007 ebx=c4e84a40 ecx=0000000f edx=c2b31658 esi=c2b31658 edi=00000000
eip=d9d1178d esp=cc317c38 ebp=cc317c90 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
MayPro+0x178d:
d9d1178d 0fb74702 movzx eax,word ptr [edi+2] ds:0023:00000002=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
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: 00000000
EXCEPTION_PARAMETER2: 00000002
READ_ADDRESS: GetPointerFromAddress: unable to read from e3984718
Unable to read MiSystemVaType memory at e3964160
00000002
FOLLOWUP_IP:
MayPro+178d
d9d1178d 0fb74702 movzx eax,word ptr [edi+2]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from e38584bc to d9d1178d
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
cc317c90 e38584bc c4e84988 c2b31658 00000000 MayPro+0x178d
cc317ca8 d9d1aad9 d9d1d13c c8db4240 cc040000 nt!IofCallDriver+0x63
cc317cd0 d9d1acff c41f6030 da74a560 c41f6030 hidusb!HumResetParentPort+0x53
cc317cec e3a3cb9d c41f6030 00000000 c29bc920 hidusb!HumResetWorkItem+0x71
cc317d00 e388a06b da74a560 00000000 c29bc920 nt!IopProcessWorkItem+0x23
cc317d50 e3a2aa55 00000001 fe5b62b6 00000000 nt!ExpWorkerThread+0x10d
cc317d90 e38dc219 e3889f5e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: MayPro+178d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: MayPro
IMAGE_NAME: MayPro.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b20efe5
STACK_COMMAND: .cxr 0xffffffffcc317750 ; kb
FAILURE_BUCKET_ID: 0x7E_MayPro+178d
BUCKET_ID: 0x7E_MayPro+178d
Followup: MachineOwner
---------
