Windows generates a bug check code on a blue screen when a problem is
encountered. These codes can assist you in troubleshooting the problem.
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.
STOP: 0x0000001E (0x80000003, 0xBFC0304, 0x0000000, 0x0000001)
[bug check code] ([1st], [2nd], [3rd], [4th])
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
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
- Lack of disk space for installation.
- Third-party video drivers (and the Windows Win32k.sys
- System BIOS incompatibilities.
To resolve this issue, use the appropriate method below:
- Reinstall on another hard disk when disk space is low.
- Remove the third-party video driver.
- 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:
How To Set Up A Remote Debug Session Using A Modem