STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED

	A kernel mode process tried to execute an illegal or unknown processor instruction.
	When you run Windows XP Setup, you may receive an error message similar to the following: STOP: 0x0000001E (0x80000003, 0xBFC0304, 0x0000000, 0x0000001) [bugcheck code] ([1] [2] [3] [4])
	When you are using Windows XP, the following error message may be displayed: STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED The STOP screen lists Aspi32.sys as the source of the STOP error.
	When you run Windows 2000 or Windows XP Professional, you may receive the following error message: STOP 0x0000001E (c00000005, 000000000, 000000000, 000000000) Note The last three sets of numbers in the error message may vary.
	After you upgrade the factory-installed Microsoft Windows 2000 operating system on a Toshiba Tecra 8100 to Microsoft Windows XP, when you attempt to undock (eject) the Toshiba Tecra 8100 from a docking station, you may receive one of the following stop messages: STOP 0x00000050 (0xFF000087, 0x00000000, 0xBFD38104, 0x00000000) STOP 0X0000001E (0X???????, 0X???????, 0X??????, 0X???????) Note: The parameters may vary, but the specific stops "0X1e" and "0x50" do not.
	When you use a 32-bit program to print a document from a 64-bit version of Microsoft Windows, you may receive a Stop error message that is similar to one of the following: STOP 0x0000001E (parameter1, parameter2, parameter3, parameter4) KMODE_EXCEPTION_NOT_HANDLED STOP 0x00000050 (parameter1, parameter2, parameter3, parameter4) PAGE_FAULT_IN_NONPAGED_AREA STOP 0x000000D5 (parameter1, parameter2, parameter3, parameter4) DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL. Note The parameter values vary. The problem may occur only occasionally because the timing of the issue is very specific.
	When you are using Windows XP, the following error message may be displayed: STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED The STOP screen lists Aspi32.sys as the source of the STOP error.
	When you start Configuration Manager on a Microsoft Windows 2000 Server-based computer or on a Microsoft Windows XP-based computer, you may receive either of the following error messages on a blue screen: STOP 0x00000051 (0x0000000c, 0xc0000005, 0x????????, 0x????????) STOP 0x0000001E,{0xc0000005, 0x8046c40e, 0x00000000, 0x????????} Note Each "?" character represents a variable value.
	When you try to switch the Microsoft Flight Simulator 2000 Professional Edition window to full-screen mode, the computer may crash, generating the following error message: Bugcheck 0x1E The computer has the latest Windows 2000 video driver, an NVIDIA RIVA TNT2 Ultra video adapter, and the Flight Simulator 2000 update patch installed. Note: This articles refers to win2k video drivers but is applicable to XP.