The "KMODE_EXCEPTION_NOT_HANDLED" error usually indicates a system-level problem (i.e., device driver or memory address conflict). You may receive the same error when you start other applications (e.g., Adobe Photoshop, Adobe Illustrator). Microsoft has published some information about this error on its Web site at http://www.microsoft.com. However, recommend you contact Microsoft or your computer manufacturer for help troubleshooting this error.
Check your Software Drivers, Printer Spooler and reapply Service Pack. This is very unlikely to be a hardware issue. If you using Terminal Server Edition try running in VGA or updating the Video Driver.
In this case, the Microkernel's processor exception handler has detected that a driver or subsystem has tried to execute an illegal processor instruction, or a software instruction that NT cannot interpret. The cause can be a faulty memory module or a driver that has corrupted memory. The module information on the blue screen is usually misleading in this case, making it difficult to identify the source of the problem.
Troubleshooting a STOP 0X0000001E KMODE_EXCEPTION_NOT_HANDLED Error Message A "STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" error message indicates that the kernel detected an unrecoverable error. The problems that can cause this kind of error are similar to the problems that cause a "STOP 0x0000000A" error messageùbad pointers, invalid addresses, and other types of access violations. The STOP 0x0000001E bug check identifies an error that occurred in a section of code that doesn't have error handling routines. The system directly generates most exceptions in the section of code that's running. Check out Microsoft article Q275678 for more details about the STOP message's structure and how to debug it.
Win2K Blue Screen A bug in the Win2K redirector causes Win2K to crash and display the message, "Stop 0x0000001E ( C0000005, 80444028, 00000000, 00000018 ) KMODE_EXCEPTION_NOT_HANDLED." Microsoft article Q264959 indicates that the system crashes because the redirector doesn't inform the Cache Manager when it extends a range of memory addresses. You must restart the crashed system; no workaround or bug fix is available.
Talk To Other Members