KMODE_EXCEPTION_NOT_HANDLED

  • Thread starter Thread starter Peter
  • Start date Start date
P

Peter

I keep getting the blue screen with this message:

STOP 0x0000001E (0x00000005, 0xA008DB42, 0x00000001,
0x0000021D)

Address A008BB42.

What can I do to remedy this problem?

Thanks in advance,
Peter
 
KMODE_EXCEPTION_NOT_HANDLED (0x1E)

This is a very common bug code. Usually the exception address pinpoints the
driver or function that caused the problem. Always note this address as
well as the link date of the driver or image that contains this address. A
common error is exception code 0x80000003. This error means a hard-coded
breakpoint or assertion was hit, but the system was booted with the /NODEBUG
switch. This problem should not occur very often. If it occurs repeatedly,
make sure a debugger is connected and the system is booted with the /DEBUG
switch.

On non-Intel systems, if the address of the exception is 0XBFC0304, the bug
code is the result of a cache-parity error on the CPU. If the problem
reoccurs frequently, contact the hardware manufacturer.

Parameters:
1 - The exception code that was not handled
2 - The address at which the exception occurred
3 - Parameter 0 of the exception
4 - Parameter 1 of the exception

Here's 3 good articles to learn how to debug. Hope this will help.

Q183169 - Possible Resolutions to Stop 0x0A, 0x01E, 0x050:
http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q183169

Windows NT Kernel Debugging Resources
http://www.win2000mag.com/Articles/Index.cfm?ArticleID=5132

Using Microsoft's x86 Kernel Debugger
http://www.win2000mag.com/Articles/Index.cfm?ArticleID=5131

Demystifying the 'Blue Screen of Death'
http://www.microsoft.com/TechNet/winnt/bsod.asp

Regards,
/Jimmy
 
Thanks for the reply.

Yes, it does occur frequently, and is happening on an
Intel Based machine. I'll try to note the Address of the
exception the next few times I see it happen.

If I were to reformat the HD and reinstall the OS, would
that remedy the problem? I've never used a Windows OS
debugger (and hope I never have to).

Thanks,

Peter
 
Well, it might remedy the problem, but I would try to find more info on the
BSOD first.

Regards,
/Jimmy
 
Back
Top