The Stop 0x1E message indicates that the Windows Server 2003 kernel detected an illegal or unknown processor instruction. The problems that cause Stop 0x1E messages share similarities with those that generate Stop 0xA errors, in that they can be caused by invalid memory and access violations. The default Windows Server 2003 error handler typically intercepts these problems if error-handling routines are not present in the code itself.
Interpreting the Stop 0x1E Message
This Stop message has four parameters, as listed below.
Parameter DescriptionParameter 1 Exception code that was not handled
Parameter 2 Address at which the exception occurred
Parameter 3 Parameter 0 of the exception
Parameter 4 Parameter 1 of the exception
The first parameter identifies the exception generated. Common exception codes are listed below.
Exception Code and Description
0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered. The trap frame supplies additional information. Generally, Stop errors with this exception code are resolved by replacing the driver named in the Stop message.
0x80000003: STATUS_BREAKPOINT
A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system. This generally occurs when a debug version of a driver is used. If you are not intentionally using a debug version of a driver, replace the driver with the free version.
0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred. Parameter 4 of the Stop message (which is parameter 1 of the exception) is the address that the driver attempted to access. When the Stop message indicates this exception code, the driver identified as the cause of the Stop error might be faulty. You should take additional steps to identify the faulty driver.
For a complete list of exception codes, see the Ntstatus.h file located in the Inc directory of the Windows Driver Development Kit (DDK). For more information about the DDK, see the Driver Development Kits link on the Web Resources page at
http://www.microsoft.com/windows/reskits/webresources.The second parameter identifies the address of the module in which the error occurred. Frequently, the address points to an individual driver or faulty hardware pointed to by the third parameter of the Stop message. Make a note of this address and the link date of the driver or image that contains it.
The last two Stop message parameters vary, depending on the exception that has occurred. You can typically find a description of the parameters that are included in the Ntstatus.h file. If the error number has no parameters, the last two parameters of the Stop message are listed as 0x00000000.
Troubleshooting the Stop 0x1E Error
First, use the Event Viewer to review the System log for error events that identify the problem. The following sections list the most common sources for this Stop error and suggest some troubleshooting solutions.
Driver, service, or hardware issuesStop 0x1E messages typically occur after faulty drivers or system services have been installed, or they can indicate hardware problems such as memory and IRQ conflicts. If a Stop message lists a driver by name, and that driver has been recently updated, use Device Manager to roll back or update the driver to correct the problem. If the device is not critical to the functionality of the system (for example, the keyboard driver), you can also uninstall or disable the driver.
Incompatible remote control programs If the Stop message mentions the file Win32k.sys, the source of the error might be an incompatible third-party remote control program. Win32k.sys is a kernel component that performs graphics functions involving the user interface. If such software is installed, you might be able to disable it by starting the system in Safe Mode. If not, use Recovery Console to manually disable the system service file that is causing the problem. If removing the remote control software solves the problem, contact the manufacturer to obtain a Windows Server 2003–compatible update.
Kernel memory leaks You can use Poolmon (Poolmon.exe) to isolate the Windows Server 2003 components that are causing kernel memory leaks. The problem might be a memory leak caused by an application or service that is not releasing memory correctly. Although memory leaks cannot directly cause Stop errors, they can cause problems with drivers that can result in a Stop error. Poolmon helps you to isolate the components that cause kernel memory leaks.
Firmware incompatibility Problems can result from system firmware incompatibilities. Using outdated firmware might cause several problems, including issues with installing Windows Server 2003. Many Advanced Configuration and Power Interface (ACPI) issues can be resolved by updating to the latest firmware. Check the computer or motherboard manufacturer’s Web site for updated system firmware.
