"Stop: 0x0000001E" Error Message During Setup

 Last reviewed: February 4, 1998
Article ID: Q161703
The information in this article applies to:
  • Microsoft Windows NT Server versions 3.1, 3.5, 3.51, and 4.0
  • Microsoft Windows NT Workstation versions 3.1, 3.5, 3.51, and 4.0

SUMMARY

Windows NT generates a bug check code on a blue screen when a problem is encountered. These codes can assist you in troubleshooting the problem. For additional information about bug check codes, see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q103059
   TITLE     : Descriptions of Bug Codes for Windows NT
This article describes only the following bug check code: 

   STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED

MORE INFORMATION

The STOP 0x1E code is a common bug check code. The exception address usually pinpoints the driver or function that caused the problem. You should note this address as well as the link date of the driver or image that contains this address to assist Microsoft Support Engineers if it becomes necessary to contact Microsoft.

Example

STOP: 0x0000001E (0x80000003, 0xBFC0304, 0x0000000, 0x0000001) 

[bug check code] ([1st],      [2nd],     [3rd],     [4th])
Parameter definitions: 

   1st = The exception code that was not handled
   2nd = The address at which the exception occurred
   3rd = Parameter 0 of the exception
   4th = Parameter 1 of the exception
On non-Intel-based computers, 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 occurs frequently, contact the hardware's manufacturer.

Possible Cause and Workaround

The STOP 1E message may occur after the first reboot during Windows NT Setup, or after Setup is finished. Three possible causes of the problem are:

  1. Lack of disk space for installation.

  2. Third-party video drivers (and the Microsoft Windows NT Win32k.sys driver).

  3. System BIOS incompatibilities.

To resolve this issue, use the appropriate method below:

  1. Reinstall on another hard disk when disk space is low.

  2. Remove the third-party video driver.

  3. Upgrade the system BIOS.

This problem should not occur very often. If it occurs repeatedly, make sure a debugger is connected and the computer is booted with the /debug switch. Refer to the following Microsoft Knowledge Base article for more information: 

   ARTICLE-ID: Q148954
   TITLE     : How To Set Up A Remote Debug Session Using A Modem

Additional query words: 3.10 3.50 3.51 4.00
Keywords : kbhw kbsetup kbfaq
Version : 3.1 3.5 3.51 4.0
Platform : winnt
Issue type : kberrmsg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 4, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.