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
Possible Resolutions to Stop 0x0a, 0x01e and 0x50 Errors:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q183169
Gathering Blue Screen Information After Memory Dump in Windows 2000 or
Windows NT:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q192463
Crash Dump Analysis:
http://www.win2000mag.com/Articles/Index.cfm?ArticleID=16425
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
Regards,
/Jimmy
--
Jimmy Andersson, Q Advice AB
Microsoft MVP - Directory Services
----------
www.qadvice.com ----------
Ilir D said:
Server computer is rebooting and giving a blue screen.
Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
(0xc0000005, 0xed5c68b2, 0x00000000, 0x0023f1da).
