Blue screen of Death
- Thread starter Tharivolt
- Start date
Solution
logang
Honorable
- Mar 29, 2012
- 503
- 0
- 11,160
i got this from dmp file:
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: 95f9dd71, The address that the exception occurred at
Arg3: 9adccb98, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!HmgLockEx+67
95f9dd71 0fb74f08 movzx ecx,word ptr [edi+8]
TRENDING THREADS
-
-
-
Question Intel Arc A750 for around $190. Is it worth it?
- Started by Dolphing Kujog
- Replies: 2
Facebook
Twitter
Instagram