Microsoft KB Archive/161703

= "Stop: 0x0000001E" Error Message During Setup =

Article ID: 161703

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Datacenter Server
 * Microsoft Windows NT Advanced Server 3.1
 * Microsoft Windows NT Server 3.5
 * Microsoft Windows NT Server 3.51
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 3.1
 * Microsoft Windows NT Workstation 3.5
 * Microsoft Windows NT Workstation 3.51
 * Microsoft Windows NT Workstation 4.0 Developer Edition

-



This article was previously published under Q161703



For a Microsoft Windows XP version of this article, see 314451.



SUMMARY
Windows generates a bug check code on a blue screen when a problem is encountered. These codes can assist you in troubleshooting the problem.



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 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 Windows 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. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

148954 How To Set Up A Remote Debug Session Using A Modem

Keywords: kbfaq kbhardware kbsetup KB161703

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.