Windows XP Stop Errors

Stop errors can be caused by just about anything, including poor quality audio drivers, incompatible video drivers, bad or corrupt hard disks, and faulty hardware such as bad RAM, dying motherboards, failing power supplies, etc. Stop errors may be triggered by an event such as plugging in a USB device, or they may appear to occur at regular intervals, or in association with some other event. Sometimes a stop error might appear to be completely random. If a stop error identifies a driver, the fault may not lie with the driver that was reported. Worse still, some errors can mask other critical errors, which means you fix one stop error and get another in return. In short, a stop error may be a symptom of some other problem. The real problem is to find the root cause.

Page Index

Tips to Help Track the Problem Down
0x00000003 UNSYNCHRONIZED_ACCESS
0x05 INVALID_PROCESS_ATTACH_ATTEMPT
0x0000000A IRQL_NOT_LESS_OR_EQUAL 0xA
0x0000001E KMODE_EXCEPTION_NOT_HANDLED 0x1E
0x00000023 FAT_FILE_SYSTEM & 0x00000024 NTFS_FILE_SYSTEM
0x0000002E DATA_BUS_ERROR 0x2E
0x0000003F NO_MORE_SYSTEM_PTES 0x3F
0x00000044 MULTIPLE_IRP_COMPLETE_REQUESTS
0x00000050 PAGE_FAULT_IN_NONPAGED_AREA 0x50
0x00000051- 0x51
0x0000006B PROCESS1_INITIALIZATION_FAILED
0x00000073 CONFIG_LIST_FAILED 0x73
0x00000074 BAD_SYSTEM_CONFIG_INFO 0x74
0x00000076 PROCESS_HAS_LOCKED_PAGES
0x00000077 KERNEL_STACK_INPAGE_ERROR 0x77
0x00000079 MISMATCHED_HAL 0x79
0x0000007A KERNEL_DATA_INPAGE_ERROR 0x7A
0x0000007B INACCESSIBLE_BOOT_DEVICE 0x7B
0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x7E
0x0000007F UNEXPECTED_KERNEL_MODE_TRAP 0x7F
0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x8E
0x0000009C MACHINE_CHECK_EXCEPTION 0x9C
0x0000009F DRIVER_POWER_STATE_FAILURE 0x9F
0x000000A5 - 0xA5
0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY 0xBE
0x000000C2 BAD_POOL_CALLER 0xC2
0x000000C4 DRIVER_VERIFIER_DETECTED_VIOLATION
0x000000CA PNP_DETECTED_FATAL_ERROR
0x000000CB
0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING... 0xCE
0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0xD1
0x000000D5 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000D8 DRIVER_USED_EXCESSIVE_PTES 0xD8
0x000000E3 - 0xE3
0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER 0xEA
0x000000ED UNMOUNTABLE_BOOT_VOLUME 0xED
0x000000F2 HARDWARE_INTERRUPT_STORM 0xF2
0x000000F4 - 0xF4
0x000000FE BUGCODE_USB_DRIVER - 0xFE
0x4000008A
0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED 0x21A
0xC0000218 UNKNOWN_HARD_ERROR 0x218 & C0000135
0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH 0x221
0xC0000244 STATUS_AUDIT_FAILED
0xC000026C
0xC0000415

Tips to help track the problem down

	If a Stop error is preventing you from starting Windows XP, see Cannot Start Windows XP on this site before you try anything else.
	Use Troubleshooting Tools Use device manager to remove device drivers. Use msconfig to disable services associated with any hardware and startup services that are not essential. You may also find these articles helpful: Windows XP Resource Kit: Troubleshooting the Startup Process
	Use Diagnostics Techniques SiSoftware Sandra (the System ANalyser, Diagnostic and Reporting Assistant) - Sandra Lite is free for personal use. x64 is supported. Perform RAM Error Checking Quite often, stop errors are associated with dud RAM. That includes main memory, video and CPU cache memory. If you have more than one stick of RAM, start ripping the sticks out one at a time. If you only have one stick, you will need to find someone who can help you out with a spare stick that fits your machine. Corrupt disks and viruses can cause all kinds of stop errors. Perform Virus Checking, even if you don't believe you have a virus or other malware, eliminate it as a cause early. Also perform disk error checking. In this session, we will cover the basics of "blue screen" errors, what they mean, and some common methods to troubleshoot the problems. We will provide some background information about blue screen errors, and we will talk about how to interpret the information, as well as how to recover from these errors. If you believe that you have a memory problem, try How to Troubleshoot RAM Installations.

	Think About Getting Desperate Remove any new hardware such as RAM, hard disks and modems, etc. Disable any new drivers and remove any recently installed software.
	Get Desperate Disable all BIOS caching and speed-up options. Disable power management. If you are over-clocking, don't. Try a standard Microsoft VGA driver. Ensure drivers and BIOS are the latest versions. Visit the manufacturer’s website and try to locate up-to-date drivers.
	Tear Your Hair Out Disable any disk intensive applications such as antivirus software, disk or file defragmenters and backup programs. Check the Event Viewer to see if there are any additional errors or warnings that might provide a clue.
	Tear Someone Else's Hair Out Take the machine to a dealer.

0x00000003 UNSYNCHRONIZED_ACCESS - 0x03

Your Microsoft Windows XP-based computer stops responding unexpectedly, and you receive a Stop error message that is similar to the following:

A problem has been detected and Windows has been shut down to prevent damage to your computer...

Technical information:

*** STOP: 0x00000003 (0x03C91000, 0x00000134, 0x00000CF0, 0x00000000)
UNSYNCHRONIZED_ACCESS

Note The four parameters in this error message may vary based on the cause of the Stop error.

When you use Event Viewer, you may see that an access violation in the Vidcap.ax Universal Video Class (UVC) driver file is logged.

0x05 INVALID_PROCESS_ATTACH_ATTEMPT

A computer that is running Microsoft Windows XP Service Pack 2 (SP2), Microsoft Windows XP Tablet PC Edition 2005, or Microsoft Windows Server 2003 unexpectedly stops. Additionally, the following Stop error message appears on a blue screen:

Stop 0x05 (INVALID_PROCESS_ATTACH_ATTEMPT)

Note: The Windows XP SP2 features and components are included in Windows XP Tablet PC Edition 2005.

Note: In typical Microsoft style, the error code for this message is 0x05, which is not standard in comparison to other stop error codes.

0x0000000A IRQL_NOT_LESS_OR_EQUAL 0xA

	Drivers are using improper memory addresses. Check for buggy device drivers. Note: Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL messages are very similar to 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL messages and the same troubleshooting principles apply. If you cannot resolve your 0x0000000A IRQL_NOT_LESS_OR_EQUAL then try the 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL section.
	On a Microsoft Windows XP Service Pack 2 (SP2)-based computer, you run a filter driver that calls the CmRegisterCallback routine to register a RegistryCallback routine. In this situation, Windows XP with SP2 may crash. When this problem occurs, you receive a stop error message that resembles the following: STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL
	When you try to hibernate a Windows XP-based computer, you may receive a "Stop 0xA0" error message on a blue screen.
	This article describes how to use a sample debugging session to determine the specific driver that is causing the following error message: Stop Error IRQL_NOT_LESS_OR_EQUAL (0xA)
	You may receive the following Stop error message during or after the installation of Microsoft Windows XP: Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL*** Address x has base at x - filename The parameters refer to the specific issues that are involved.
	After you use the Fast User Switching feature to change users on a Windows XP-based computer, the computer may restart or you may receive the following error message if the new user attempts to use the special buttons on the keyboard: IRQL_NOT_LESS_OR_EQUAL Stop 0x0000000a (0x0227001d, 0x00000002, 0x00000000, 0x804eba3a) NOTE: The first and fourth parameters in the error message may be different, depending on the computer.
	When you change between AC power and DC power on your laptop computer, you may receive a "STOP 0x0000000A" error message on a blue screen. This is more likely to occur when you unplug or re-plug the power supply into the computer while it is in Standby mode, and then resuming.
	When you try to use a Hewlett-Packard (HP) 5100C ScanJet scanner, you may receive the following stop message: Stop: 0x0000000a (0x8061D594, 0x00000002, 0x00000000, 0x805BFD2B)
	When you are upgrading your computer from Microsoft Windows 98 or Microsoft Windows Millennium Edition (Me) to Windows XP, you may receive the following error message: Stop 0x0000000A irql_not_less_or_equal
	When you shut down your Microsoft Windows XP-based computer, your computer may restart instead of shutting down, and a Stop error may briefly appear before the computer restarts.
	After you upgrade your computer (with Easy CD Creator Platinum 5.02b and the DirectCD component installed) to Windows XP, you may experience one of the following symptoms: Your computer may automatically restart when you try to shut down; When you shut down your computer, you may receive the following error message on a blue screen: STOP 0x0000000A (0x000002DC, 0X000000FF, 0X00000000, 0X804E9D48) IRQ_NOT_LESS_OR_EQUAL
	You may receive an error message on your computer that is running Microsoft Windows Server 2003, Microsoft Windows 2000 Server, Microsoft Windows Small Business Server 2003, Microsoft Small Business Server 2000, or Microsoft Windows XP. When this issue occurs, your computer may stop responding. (STOP 0x0000007b or STOP 0x0000000a, with Pqv2i.sys driver [V2i Protector 2.0] from Symantec)
	You may receive a Stop error message after you insert media into a removable disk device that is connected to a computer that is running one of the following operating systems: Microsoft Windows Server 2003; Microsoft Windows XP; Microsoft Windows 2000 Professional. The message may also occur if you start the computer when a removable disk device that contains media is connected to the computer. The Stop error message is similar to one of the following messages: STOP 0x0000000A (0x00000004, 0x0000001c, 0x00000001, 0x804324ac) STOP 0x000000D1 (0xffffff20, 0x00000002, 0x00000000, 0xbfe5d810) STOP 0x000000C4 (0x00000013, 0x00000fb6, 0x88efb2c0, 0x00000000) STOP 0x00000050 (0xff391000, 0x00000001, 0x804d1017, 0x00000000) Note The parameters for these Stop error messages may vary.
	If you start Microsoft Windows XP by using the /3GB switch, you may receive a "Stop" error message that is similar to one of the following: Stop 0x50 PAGE_FAULT_IN_NONPAGED_AREA Stop 0x0A IRQL_NOT_LESS_OR_EQUAL
	A computer that is running Microsoft Windows XP with Service Pack 2 crashes. You may receive one of the following Stop error messages: Error message 1 STOP 0x0000001a: MEMORY_MANAGEMENT Error message 2 STOP 0x0000000a: IRQL_NOT_LESS_OR_EQUAL
	f you connect to the Internet by using an Ericsson HIS modem, your computer may stop responding (hang) during a heavy load. When this occurs, you receive the following Stop code: IRQL_NOT_LESS_OR_EQUAL or DRIVER_CORRUPTED_EXPOOL
	When you use an IEEE 1394-based scanner and run a 32-bit scanning program on a computer that is running Microsoft Windows XP 64-bit, Microsoft Windows Server 2003, you receive an error message on a blue screen that resembles one of the following: 0x0000000A: IRQL_NOT_LESS_OR_EQUAL 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY This problem occurs when the scanning program calls the DeviceIoControl function to send a IOCTL_SCSISCAN_CMD control code to the kernel mode driver. In Windows Vista, you may not experience the blue screen. When your scanning program calls the DeviceIoControl function to send an IOCTL_SCSISCAN_CMD control code to the kernel mode driver in Windows Vista, this call may not be completed successfully, and your scanning program does not work as expected. The exact symptom that is observed in the user interface depends on how your scanning software works when the DeviceIoControl function fails.
	When the operating system sends an interrupt signal on a Microsoft Windows XP Service Pack 1-based computer, you may receive a Stop error that is similar to the following: STOP: Ox0000000a in HalpDismissLevel
	When you change the IPX frame type for your network connection from Auto Detect to any other IPX frame type, you may receive a "STOP 0x0000001D" or "STOP 0x000000A" Stop error that occurs in Ndis.sys. This problem may occur if you installed the NWLink IPX/SPX/NetBIOS Compatible Transport protocol on your computer and you are using the Driver Verifier Manager to troubleshoot your Ndis.sys driver's Special Pool feature.

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.

0x00000023 FAT_FILE_SYSTEM & 0x00000024 NTFS_FILE_SYSTEM

	A problem occurred in the file system. Usually this error is caused by disk corruption or disk defragmenters.
	When you use the DiskPart.exe tool to delete a partition, you may receive a "Stop 0x23" error message on a blue screen. This error may occur when you run a script that uses the DiskPart.exe tool to delete a partition.
	A computer that is running Microsoft Windows XP may stop responding when you suddenly remove a storage device. For example, the computer may stop responding if you suddenly remove a Secure Digital card from a USB card reader. When this problem occurs, you receive a Stop error message that resembles the following: STOP 0x00000023 FAT_FILE_SYSTEM (Param1, Param2, Param3, Parame4)
	Also see: , which is for win2k, however the information in the article is generic and can be applied to XP.
	You insert and then remove a removable storage media, such as a Secure Digital (SD) card, on a Microsoft Windows XP-based computer. You receive a Stop error message in Fastfat.sys that resembles the following: STOP 0x00000023 (Parameter1, Parameter2, Parameter3, Parameter4) FAT_FILE_SYSTEM

0x0000002E DATA_BUS_ERROR

	System memory has a parity error.
	The Stop 0x2E message indicates a system memory parity error. The cause is typically failed or defective RAM (including motherboard, Level 2 cache, or video memory), incompatible or mismatched memory hardware, or when a device driver attempts to access an address in the 0x8xxxxxxx range that does not exist (does not map to a physical address). A Stop 0x2E message may also indicate hard disk damage caused by viruses or other problems. If Shadow RAM is enabled, try disabling it. If new RAM has been added, remove it.

0x0000003F NO_MORE_SYSTEM_PTES

	A driver did not release Page Table Entries. The Stop 0x3F message indicates one or more of the following problems: The system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output (I/O) actions. A faulty device driver is not managing memory properly. An application, such as a backup program, is improperly allocating large amounts of kernel memory.
	Your Windows Server 2003-based, Windows XP-based, or Windows 2000-based computer may generate one of the following error messages on a blue screen: STOP: 0x0000003F (0xA,0xB,0xC,0xD) NO_MORE_SYSTEM_PTES STOP: 0x000000D8 (0xW,0xX,0xY,0xZ) DRIVER_USED_EXCESSIVE_PTES This article describes how to troubleshoot these error messages.

0x00000044 MULTIPLE_IRP_COMPLETE_REQUESTS

	Consider the following scenario: On a Microsoft Windows XP-based computer, you apply the hotfix that is described in the following Microsoft Knowledge Base (KB) article: (http://support.microsoft.com/kb/918005/) Battery power may drain more quickly than you expect on a Windows XP SP2-based portable computer You put the computer into hibernation (the S4 sleep state). You resume the computer from hibernation. In this scenario, the computer crashes. Additionally, you receive a Stop error message that resembles the following: A problem has been detected and Windows has been shut down to prevent damage to your computer. MULTIPLE_IRP_COMPLETE_REQUESTS Technical information: *** STOP: 0x00000044 (0xFB8AA008, 0x00001BBF, 0x00000000, 0x00000000)
	Microsoft Windows XP Professional may stop unexpectedly, and you may receive an error message that is similar to the following error message: STOP 0x00000044 (0x822ad2a0, 0x00000d60, 0x00000000, 0x00000000) MULTIPLE_IRP_COMPLETE_REQUESTS.

0x00000050 PAGE_FAULT_IN_NONPAGED_AREA

	Drivers are using improper memory addresses. As odd as it may seem, if this error occurs in a Remote Desktop or Terminal Services session, check third-party printer drivers.
	When you upgrade your computer to Microsoft Windows XP Service Pack 2 (SP2) or to Microsoft Windows XP Tablet PC Edition 2005, when you restart your computer during the installation, the computer stops unexpectedly and you receive the following error message: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: *** STOP: 0x00000050 (0x905108010, 0x00000000, 0x80509443, 0x00000000) PAGE_FAULT_IN_NONPAGED_AREA
	When you try to run one of the following diagnostic programs, the program may immediately close: Registry Editor (Regedit.exe) Task Manager (Taskmgr.exe) System Configuration Utility (Msconfig.exe) System Information (Msinfo32.exe) You may also experience any one of the following symptoms: The computer automatically restarts After you log on, you receive the following error message Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here.
	In Microsoft Windows Server 2003 and in Microsoft Windows XP, when you copy an image to the clipboard, Windows may crash. In this scenario, you receive the following Stop error message: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: *** STOP: 0x00000050 (bc7cf000, 00000000, bf964404, 00000001) Note The parameters in this error message may vary depending on the location in memory where this Stop error occurred.
	When you try to use Roxio Easy CD Creator 5.0, any of the following symptoms may occur: Your computer may automatically restart, stop responding (hang), or May stop functioning correctly After you log on, you receive the following error message Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. You may receive a "Stop" error message that is similar to one of the following error messages: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: * STOP: 0x00000050: (0xAAAAAAAA, 0xBBBBBBBB, 0xCCCCCCCC, 0xDDDDDDDD) PAGE_FAULT_IN_NONPAGED_AREA A problem has been detected and Windows has been shut down to prevent damage to your computer... * STOP: 0x0000007E: (0xAAAAAAAA, 0xBBBBBBBB, 0xCCCCCCCC, 0xDDDDDDDD) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED After you receive this error message, your computer restarts.
	You may experience any of the following symptoms: Your computer automatically restarts After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. If the error message still appears and if you want to see the data that the error report contains, click the "click here" link at the bottom of the message box. You then see error signature information that may be similar to: BCCode : 00000050 BCP1 : 0xffffffe0 BCP2 : 0x00000001 BCP3 : 0xf30da010 BCP4 : 0x00000000 OSVer : 5_1_2600 SP : 0_0 Product : 256_1 You receive the following stop error message on a blue screen: A problem has been detected and Windows has been shut down to prevent damage to your computer Technical information: *** STOP: 0x00000050 (0xffffffe0, 0x0x00000001, 0xf30da010, 0x00000000) PAGE_FAULT_IN_NONPAGED_AREA
	You may experience one of more of the following symptoms: The computer automatically restarts; After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. If the error message remains on the screen, click the "click here" link at the bottom of the message box if you want to see the data that the error report contains. If you do this, you see error signature information that may be similar to the following: BCCode : 00000050 BCP1 : 0xeb7ff002 BCP2 : 0x00000000 BCP3 : 0x8054af32 BCP4 : 0x00000001 OSVer : 5_1_2600 SP : 0_0 Product : 256_1 You receive the following Stop error message: A problem has been detected and Windows has been shut down to prevent damage to the computer Technical information: STOP: 0x00000050 (0xeb7ff002, 0x00000000, 0x8054af32, 0x00000001) PAGE_FAULT_IN_NONPAGED_AREA nt!ExFreePoolWithTag+237
	You may experience one or more of the following symptoms on a Microsoft Windows Server 2003-based, Microsoft Windows XP-based, or Microsoft Windows 2000-based computer: The computer automatically restarts After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here.
	When you try to add a small computer system interface (SCSI) device or a Peripheral Component Interconnect (PCI) storage device to a computer that is running Microsoft Windows XP Service Pack 2 (SP2), a Stop 0x00000050 error may occur in Scsiport.sys.
	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 try to add a small computer system interface (SCSI) device or a Peripheral Component Interconnect (PCI) storage device to a computer that is running Microsoft Windows XP Service Pack 2 (SP2), a Stop 0x00000050 error may occur in Scsiport.sys.
	If you start Microsoft Windows XP by using the /3GB switch, you may receive a "Stop" error message that is similar to one of the following: Stop 0x50 PAGE_FAULT_IN_NONPAGED_AREA Stop 0x0A IRQL_NOT_LESS_OR_EQUAL
	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 install Microsoft Windows XP, you may receive a Stop Error message that is similar to one of the following while the Setup program is running: STOP 0x0000008e STOP 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA Additionally, if you troubleshoot by removing all unnecessary hardware devices that are installed on the computer, and then you run the Setup program, you may receive an error message that is similar to the following: Setup cannot copy the file Setupdd.sys.

0x00000051 - 0x51

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.

0x0000006B PROCESS1_INITIALIZATION_FAILED

	If you try to install a Microsoft Windows Server 2003 image, or a Microsoft Windows XP client image with slipstreamed Windows XP Service Pack 1 (SP1) or Windows XP Service Pack 2 (SP2) from a Remote Installation Services (RIS) server, Setup stops responding at the "Setup is Starting Windows" message. Or, you may receive the following Stop error message on a blue screen: STOP: 0x0000006b (0xC000020A, 0x00000002, 0x0000000, 0x00000000) PROCESS1_INITIALIZATION_FAILED Note: The four parameters that are inside the parentheses can vary according to the configuration of the computer.
	When you are upgrading to Windows XP, you may receive the following error message: An unexpected error (768) occurred at line 5118 in <drive letter>\xpclient\base\boot\setup\setup.c Press any key to continue. Once you hit any key, the system then starts to load Windows, after which you receive the following: A problem has been detected and windows has been shutdown to prevent damage to your computer. PROCESS1_INITIALIZATION_FAILED Note: It is not known if this particular error message is related STOP: 0x0000006B. The referenced article may contain extraneous text.
	When you try to repair your Windows XP installation or when your computer first restarts after you upgrade to Windows XP, you may receive the following STOP error message on a blue-screen: A problem has been detected and Windows has been shut down to prevent damage to your computer. PROCESS1_INITIALIZATION_FAILED If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps: Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need. If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode. Technical information: *** STOP: 0x0000006B (0x0000003A, 0x00000002, 0x00000000, 0x00000000)

0x00000073 CONFIG_LIST_FAILED

	Problem with core registry hives. This Stop error indicates that one of the core Windows system hives (the SAM hive, the SECURITY hive, the SOFTWARE hive, or the DEFAULT hive) cannot be linked in the Windows registry. However, this error does not mean that the hive is damaged or that it was not loaded successfully.
	You receive a Stop error message that is similar to the following message: STOP: 0x00000073 (0x00000001, 0xc000017d, 0x00000002, 0xfc96fcc0) CONFIG_LIST_FAILED

0x00000074 BAD_SYSTEM_CONFIG_INFO

	Faulty or misconfigured RAM.
	When you start your Windows XP-based computer, you may receive a STOP error message on a blue screen that is similar to the following error message: STOP 0x00000074 (0x00000003, 0x00000002, 0x80087000) BAD_SYSTEM_CONFIG_INFO When you try to start your computer from the Windows XP CD-ROM, you may receive the following error message: The following file is corrupted: toside.sys

0x00000076 PROCESS_HAS_LOCKED_PAGES

	When you quit your backup software in Windows 2000 or Windows XP, you may receive a stop error on a blue screen that is similar to one of the following stop errors: 0x00000076 (PROCESS_HAS_LOCKED_PAGES) Or 0x000000CB (DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS)
	A Windows 2000-based computer may display one of the following error messages on a blue screen: STOP: 0x00000076 (0xY,0xY,0xY,0xY) PROCESS_HAS_LOCKED_PAGES STOP: 0x000000CB (0xY,0xY,0xY,0xY) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS The parameters in these error messages vary, depending on the programs in use and the system configuration. Note: This article refers to win2k, however it is applicable to Microsoft Windows XP Professional.

0x00000077 KERNEL_STACK_INPAGE_ERROR

	Kernel data could not be read from the paging file into memory. The Stop 0x77 message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. This Stop message can also indicate disk hardware failure, disk data corruption, or possible virus infection.
	STOP Messages 0x00000077 and 0x0000007A are related kernel traps that are caused when the operating system tries to load a page into memory from the paging file on the hard disk, but cannot access the page because of either a software or hardware failure.
	When you are running Windows XP, you may receive the following error message: Stop 0x00000077 KERNEL_STACK_INPAGE_ERROR This article describes how to troubleshoot these error messages.

0x00000079 MISMATCHED_HAL

	Incorrect Hardware Abstraction Layer. The Stop 0x79 message indicates that the hardware abstraction layer (HAL) and the kernel type for the computer do not match. This error most often occurs when ACPI firmware settings are changed. For example, you might install Windows XP Professional on an x86-based computer with the firmware ACPI enable option enabled and later decide to disable it. This error can also result when you try to run an existing installation on new hardware.
	The source and destination computers must use the same type of HAL. There is one exception to this rule. If one of the computers contains the Advanced Configuration and Power Interface (ACPI) multiprocessor HAL, the other computer can have the ACPI uniprocessor HAL. The same rule applies to MPS multiprocessor and MPS uniprocessor HALs.
	This article describes Hardware Abstraction Layer (HAL) options that are listed in Device Manager and the options that are available after you run Microsoft Windows XP Setup or Microsoft Windows Server 2003 Setup.
	This article describes how to force in a system Hardware Abstraction Layer (HAL) during an upgrade or an installation of Microsoft Windows XP.

0x0000007A KERNEL_DATA_INPAGE_ERROR

	The requested page of kernel data from the paging file could not be read into memory. The Stop 0x7A message indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. This might be due to incompatible or defective disk drivers, firmware, or hardware, bad sector in a paging file, a virus, or failing RAM.
	STOP Messages 0x00000077 and 0x0000007A are related kernel traps that are caused when the operating system tries to load a page into memory from the paging file on the hard disk, but cannot access the page because of either a software or hardware failure.
	A computer that is running Microsoft Windows XP or a later operating system stops responding during resume from standby, and you receive one of the following stop error messages: KERNEL_DATA_INPAGE_ERROR 0x0000007a (e163a3e4,c000000e,bf8e9313,0697f860) 0x000000F4 (0x00000003, Parameter2, Parameter3, Parameter4)

0x0000007B INACCESSIBLE_BOOT_DEVICE

	A problem occurred during the initialization of the I/O system; often the startup device or the file system. Windows XP lost access to the system volume or boot volume during the startup process. Initialisation of the I/O system failed (usually the boot device or the file system), Windows lost access to the system volume or boot volume during the startup process. This error always occurs while the system is starting and is often caused by one of the following: Hardware problems e.g. A failed boot device Corrupted or incompatible storage drivers SCSI, RAID, UDMA IDE, SATA File system problems Boot sector viruses Outdated firmware During I/O system initialisation, this error can occur when the controller or driver for the startup device (typically the hard disk) failed to initialise the necessary hardware; The file system initialisation failed because the system did not recognise the data on the boot device. This error can also be caused by an incorrect Advanced RISC Computing (ARC) path in BOOT.INI. ARC paths are used to define the path to the Windows installation on Intel x86-processor-based machines. See: .
	When you start your computer from a Microsoft Windows Preinstall Environment (WinPE) CD-ROM, or from a Microsoft Windows Server 2003 CD-ROM, by using a USB CD-ROM device, the computer may restart. You may receive the following Stop error message on a blue screen: STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE Fatal System Error
	When you start your computer, you may receive one of the following error messages: STOP: 0x0000007B (parameter1, parameter2, parameter3, parameter4) INACCESSIBLE_BOOT_DEVICE Setup has encountered a fatal error that prevents it from continuing. Contact your product support representative for assistance. The following status will assist them in diagnosing the problem. (0x4, 0x1, 0, 0) Setup cannot continue. Power down or reboot your computer now.
	When you start your Microsoft Windows XP-based computer after you replace the motherboard on the computer, you may receive a Stop error message that is similar to the following: STOP 0x0000007B INACCESSABLE_BOOT_DEVICE
	After you move the Microsoft Windows XP system (boot) disk to a backup computer, you may receive the following Stop error when you try to start the Windows XP-based backup computer: STOP: 0x0000007B (0xF741B84C, 0xC0000034, 0x00000000, 0x00000000) INACCESSIBLE_BOOT_DEVICE
	When you restart your computer after you remove Roxio Easy CD Creator 5 Platinum Edition, you may receive a STOP error message on a blue screen that is similar to the following: A problem has been detected and Windows has been shut down to prevent damage to your computer. *** STOP: 0x0000007B (0xF9E62640, 0xC0000034, 0x00000000, 0x00000000)
	You may receive an error message on your computer that is running Microsoft Windows Server 2003, Microsoft Windows 2000 Server, Microsoft Windows Small Business Server 2003, Microsoft Small Business Server 2000, or Microsoft Windows XP. When this issue occurs, your computer may stop responding. (STOP 0x0000007b or STOP 0x0000000a, with Pqv2i.sys driver [V2i Protector 2.0] from Symantec)
	When you are installing Microsoft Windows XP or Microsoft Windows Server 2003 on a new computer or on a computer that has the latest SCSI or IDE controller technology, you may have to use an OEM device driver to support, for example, a new mass storage controller, to continue with the installation. The symptoms that you have to install an OEM device driver include the following: The computer may keep restarting and never start the GUI installation after the text mode Setup is finished. The Setup program may stop, and you may receive an error message if the Setup program does not correctly detect the controller. If you are booting from the installation floppy disks or CD-ROM disc, you receive the following error message: Setup did not find any hard disk drives installed in your system. If you are upgrading by using the Winnt32.exe file, or if you are performing a new installation by using the Winnt.exe file, you receive the following Stop error: Stop 0x0000007B Inaccessible_boot_device
	You may experience one or more of the following symptoms: After the first reboot of Windows XP Setup, you may receive one of the following error messages: No operating system Setup has determined that Drive C: is corrupted and cannot be repaired. To quit setup press F3 Windows could not start because of the following ARC firmware boot configuration problem. Did not properly generate ARC name for HAL and System path. Please check the windows documentation about ARC configuration options and your hardware reference manuals for additional information Stop: 0x0000007b (0xf898963c, 0xc0000034, 0x00000000, 0x00000000) Windows XP Setup may stop responding (hang) and display a blank black screen after the first reboot; After you install Windows XP, secondary hard drives that worked and appeared correctly in the following operating systems may appear to be damaged or have a size of zero bytes: Microsoft Windows Millennium Edition (Me); Microsoft Windows 98 Second Edition; Microsoft Windows 98; Microsoft Windows 95.
	During an unattended setup of Windows XP where you have set the Repartition option to Yes, when you press F6 to load drivers, the process may generate a STOP 7b error after the text mode portion of setup.
	Related Articles The source and destination computers must use the same type of HAL. There is one exception to this rule. If one of the computers contains the Advanced Configuration and Power Interface (ACPI) multiprocessor HAL, the other computer can have the ACPI uniprocessor HAL. The same rule applies to MPS multiprocessor and MPS uniprocessor HALs. This step-by-step article describes how to prepare to upgrade from Microsoft Windows 98 or Microsoft Windows Millennium Edition to Microsoft Windows XP. The information in this article may be useful to help you avoid some common upgrade-related issues. This article describes Hardware Abstraction Layer (HAL) options that are listed in Device Manager and the options that are available after you run Microsoft Windows XP Setup or Microsoft Windows Server 2003 Setup. This article describes how to force in a system Hardware Abstraction Layer (HAL) during an upgrade or an installation of Microsoft Windows XP.

0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

	A driver is incompatible or it is damaged.

	A "stop 0x7E" error that may occur during startup on some systems that are running an older Pentium 5 CPU.
	A 0x7E Stop error occurs on your Microsoft Windows XP-based portable computer. This error may occur after you close a program that has an open handle to a file on a universal serial bus (USB) 2.0 flash storage device. For example, a 0x7E Stop error may occur if you do the following: You connect a USB 2.0 flash storage device to your portable computer by using a USB port on your docking station. You use a program, such as Microsoft WordPad, to save a file to the USB 2.0 flash storage device. You change the file but do not save it. You disconnect the USB 2.0 flash storage device. You disconnect the portable computer from the docking station. You close the program. You are not prompted to save the file, and a 0x7E Stop error occurs.
	After you upgrade your computer to Windows XP, you may receive the following STOP error message: STOP: 0x0000007E (0xC0000005, 0x804E518E, 0xFC938104, 0xFC937E04) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Note The four parameters in this error message may vary depending on the cause of the STOP error.
	When you disconnect a CardBus Compact Flash (CF) adapter, your computer may stop unexpectedly, and you may receive the following stop error in Pci.sys on a blue screen: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: STOP: 0x0000007E (0xAAAAAAAA, 0xBBBBBBBB, 0xCCCCCCCC, 0xDDDDDDDD) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Note The four parameters in this error message may vary depending on the cause of the stop error.
	After you upgrade a computer that uses a processor other than an Intel processor to Microsoft Windows XP Service Pack 2 (SP2), you may receive the following error message after you restart the computer: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: STOP: 0x0000007E (0xC0000005, 0xFC5CCAF3, 0xFC90F8C0, 0xFC90F5C0) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
	When you try to shut down Windows XP, you may receive the following Stop error: Stop: 0x0000007E (0xC0000005, 0xFC7F1945, 0xFC9589B0, 0xFC9586B0) Kbdclass.sys- address Fc7F1945 base at FC7F1000, Datestamp 3b7d82f3
	If you connect a Universal Serial Bus (USB) input device (such as a keyboard or mouse) to a Windows XP-based computer on which Windows XP Service Pack 1 (SP1) or the USB 2.0 update is installed, you may receive the following error message while you are streaming USB audio or video: STOP: 0x0000007E (0xC0000005, address, address, address) usbhub.sys Note that the second, third, and fourth parameters in the error message may vary.
	You may experience one or more of the following symptoms: Your computer automatically restarts. After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. You receive the following Stop error message on a blue screen: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: STOP: 0x0000007E (0xC0000005, 0xFC5CCAF3, 0xFC90F8C0, 0xFC90F5C0) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
	When you try to use Roxio Easy CD Creator 5.0, any of the following symptoms may occur: Your computer may automatically restart, stop responding (hang), or may stop functioning correctly; After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. You may receive a "Stop" error message that is similar to one of the following error messages: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: STOP: 0x00000050: (0xAAAAAAAA, 0xBBBBBBBB, 0xCCCCCCCC, 0xDDDDDDDD) PAGE_FAULT_IN_NONPAGED_AREA A problem has been detected and Windows has been shut down to prevent damage to your computer... STOP: 0x0000007E: (0xAAAAAAAA, 0xBBBBBBBB, 0xCCCCCCCC, 0xDDDDDDDD) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED After you receive this error message, your computer restarts.
	After you wake a Windows XP-based computer from standby or from hibernation, you may receive the following error message: Stop 0x0000007E (c0000005, Parameter2, Parameter3, Parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED This problem occurs if you remove a USB device when the computer is on standby or in hibernation.
	You may receive a Stop error message that is similar to the following on a Microsoft Windows XP Service Pack 2 (SP2)-based computer: STOP 0x0000007e (parameter1, parameter2, parameter3, parameter4) aec.sys Note The parameter values may vary. This error may occur during startup or after you have started the computer.
	On a Microsoft Windows XP-based computer that has the ConnectMultiplePorts registry entry configured, you may receive a Stop error message that resembles the following: Stop 0x0000007E (parameter1, parameter2, parameter3, parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Note The parameter values may vary.
	When you perform a new Microsoft Windows XP installation or a repair installation, your computer may restart when Setup reaches the hardware detection phase.
	Related Article After you install a new hardware device or new software, your computer may start to restart spontaneously, or you may receive error messages on a blue screen.
	When you try to install Windows XP by using a disk image, you may receive an error message on a blue screen similar to the following: STOP: 0x0000007E (0xc0000005, 0xF9E2BB72, 0xF9FD30E4, 0xF9FD2DE4) usbccgp.sys - Address F9E2BB72 base at F9E28000, DateStamp 3d6ddc33
	On a computer that is running Microsoft Windows XP, you may receive the following Stop error message after you enable the Event Tracing for Windows (ETW) trace log for an application: 0x0000007E (0xC0000005, parameter2, parameter3, parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED The problem does not occur if the same application runs on a computer that is running Windows Server 2003.

0x0000007F UNEXPECTED_KERNEL_MODE_TRAP

	There is a hardware or software problem. One of three types of problems occurred in kernel-mode: A condition that the kernel is not allowed to have or intercept (also known as a bound trap), e.g. the CPU generated an error that the kernel did not catch. Software problems Hardware failures This error is usually caused by a hardware failure, more often than not, faulty RAM. If you have SCSI equipment installed, disable sync negotiation in the SCSI BIOS and check SCSI termination. This error may also be caused by over-clocking.
	When you touch the screen with a stylus pen on a Microsoft Windows XP Tablet PC Edition 2005-based computer, you receive a Stop error message that is similar to the following: STOP 0x0000007F(parameter1, parameter2, parameter3, parameter4) UNEXPECTED_KERNEL_MODE_TRAP
	Microsoft is aware of an issue that affects a limited number of printer drivers. When you try to print by using one of these drivers after you install security update 925902, you may experience the following symptoms: Your computer automatically restarts. After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. You receive the following Stop error message: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: *** Stop 0x0000007f (0x00000000, 0x00000000, 0x00000000, 0x00000000) UNEXPECTED_KERNEL_MODE_TRAP
	You may receive the following error message while running Windows: STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)
	Your Windows 2000-based computer or Windows XP-based computer that is running Terminal Services may stop responding, and then you receive the following error message on a blue screen: 0x0000007f (0x00000008) error STOP 0x7f The Win32k.sys file is listed as the source of the Stop error. When you shut down and restart your computer, the computer starts normally. However, the Stop error recurs regularly.
	When you try to install or upgrade to Microsoft Windows XP Professional or Microsoft Windows XP Home Edition on a Hewlett Packard Pavilion 7840 computer, you may notice the following behavior. The first time that you restart the computer, you may receive the following error message: STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)
	When you run Symantec AntiVirus Corporate Edition 8.0 and NSI Software's Double-Take on your computer, you may experience one or both of the following symptoms: You receive the following Stop error message: STOP 0x0000007F (0x00000008, 0x00000000, 0x00000000, 0x00000000) (UNEXPECTED_KERNEL_MODE_TRAP) Your computer unexpectedly restarts.
	On a computer that is running one or more Intel Xeon processors, or that is running other processors, Windows may display a Stop error message that is similar to the following STOP 0x0000007F (0x00000008, 0x00000000, 0x00000000, 0x00000000) UNEXPECTED_KERNEL_MODE_TRAP
	When performing a clean installation of Windows XP, you may experience one of the following symptoms during the text-mode portion of Setup: You may receive a "STOP 0x0000007f" error message The Welcome screen may appear, and your computer may then turn off

0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED

	This is a very common bug check. To interpret it, you must identify which exception was generated. May also be reported as 0x1000008E. Possible causes: Hard disk damage or failure Configuration problems with the BIOS, memory, hard disk, or other devices Incompatible device driver Incompatible software
	You use either Microsoft Office Visio 2007 or Microsoft Office Visio 2003 on a computer that is running Microsoft Windows XP. You start to print a large drawing in Visio. When you click Cancel in the Print dialog box to cancel the print job, you experience one or both the following symptoms: Visio stops responding (hangs). You receive a Stop error message that resembles the following: ***Stop: 0x0000008e (parameter1, parameter2, parameter3, parameter4) KERNEL_MODE_EXCEPTION_NOT_HANDLED
	When you try to transfer data to a USB (universal serial bus) device, you may receive an 8E Stop error message on a blue screen. You may see reference to the Usbser.sys file on the blue screen.
	When you try to change the Hardware Acceleration setting in the Display tool in Control Panel from None to Full, you may receive the following Stop error message in Win32k.sys: STOP: 0x0000008E (c0000005, bf875fc3, f07bcd48, 00000000) KERNEL_MODE_EXCEPTION_NOT_HANDLED
	When you resume your laptop computer, Windows XP may stop unexpectedly (crash), and you may receive the following error message: Stop 0x0000008E
	When you install Microsoft Windows XP, you may receive a Stop Error message that is similar to one of the following while the Setup program is running: STOP 0x0000008e STOP 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA Additionally, if you troubleshoot by removing all unnecessary hardware devices that are installed on the computer, and then you run the Setup program, you may receive an error message that is similar to the following: Setup cannot copy the file Setupdd.sys.
	On your Microsoft Windows XP-based computer, you receive a Stop error message that is similar to the following: STOP 0x0000008E The Stop error occurs in the Win32k.sys driver. You may receive the Stop error when you use the keyboard to activate and control the menu items of some programs.
	When you try to install Microsoft Windows XP, you may receive an error message similar to one or both of the following error messages: Failed to install product catalog. STOP 0x0000008E (0x00000005, 0xBF869F22, 0xF9470688, 0x00000000)
	A "STOP 0x0000008E" error message may occur in Wdmaud.sys.
	When you run Microsoft Windows XP, you may randomly receive an error message on a blue screen that references a bugcheck ID 0x0000008E (KERNEL_MODE_EXCEPTION_NOT_HANDLED) error.
	You are using a computer that is running either Microsoft Windows XP Home Edition or Microsoft Windows XP Professional Edition, and you print a document. If you click Cancel in the Printing dialog box, you may receive a 0x0000008E Stop error message.
	You may experience one or more of the following issues after you remove an IEEE 1394 storage device, such as a CD-ROM or external disk drive, from your Windows XP Service Pack 1 (SP1)-based computer: When you put your computer into hibernation, you may receive a Stop error message similar to the following on a blue screen: *** STOP: 0x0000008E (0xC00000005, 0x804EF844, 0xF89463FC,0x00000000) When you put your computer into standby, the monitor turns off as expected, however the computer does not enter standby. The power indicator on your computer indicates that the computer is not on standby.
	When you use the highlighter feature and the font color feature in Microsoft Windows XP programs, your computer may stop responding and you may receive a "0x0000008E" error message on a blue screen.
	After you upgrade your computer to Windows XP, you may experience one or more of the following symptoms: Your computer unexpectedly restarts at random intervals; When you start your computer, you receive the following error message: Windows could not start because the following file is missing or corrupt: System32\DRIVERS\pci.sys; When you start your computer by using the Windows XP Recovery Console or by starting from the Windows XP CD-ROM, you receive one of the following error messages: Setupdd.sys could not be loaded. Error code 4. Setupdd.sys could not be loaded. Error code 7.
	You may experience one or more of the following symptoms on a Microsoft Windows Server 2003-based, Microsoft Windows XP-based, or Microsoft Windows 2000-based computer: The computer automatically restarts; After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here.
	On a computer that has a Creative Technology Audigy sound card installed, you may receive the following error message on a blue screen after you upgrade the computer from Microsoft Windows 2000 to Windows XP: STOP: 0x1000008E (c0000005, f80ef98c, f02f3b94, 00000000) In EMUPIA2K.SYS KERNEL_MODE_EXCEPTION_NOT_HANDLED_M The four parameters in the parentheses may vary, depending on the configuration of your computer.
	In Microsoft Windows Server 2003 or in Microsoft Windows XP, you drag an item that is on a menu. When you do this, you receive a Stop error message that resembles the following ***Stop: 0x0000008e (0xc0000005, 0xbf8f5be1, 0xb8f57b08, 0x00000000) Note The Stop error message occurs in the win32k!xxxMenuWindowProc+0xb4f process.
	When you start a Microsoft Windows Server 2003-based computer or a Microsoft Windows XP-based computer, you may receive a Stop error message on a blue screen. The Stop error message is similar to the following Stop error messages: STOP 0x1000008E STOP 0x0000008E
	After you install the Microsoft Windows Server 2003 Scalable Networking Pack on a Microsoft Windows Server 2003-based computer, you may receive a Stop error message that resembles one of the following: x64-based versions STOP: 0x0000003B (0xc0000005, parameter2, parameter3, parameter4) STATUS_ACCESS_VIOLATION x86-based versions STOP 0x0000008E (0xc0000005, parameter2, parameter3, parameter4) STATUS_ACCESS_VIOLATION Note: This article also applies to Microsoft Windows XP Professional x64 Edition
	After you install the base station, the Broadband Network Utility (BNU) software, or the software for the MN-100 or MN-500 device on your Windows XP-based computer, your computer may suddenly restart or become unresponsive. If the "Automatically Restart" feature in Startup and Recovery Settings is disabled, you may receive the following error message on a blue screen: STOP 0x0000008E { 0xC0000005, 0xB252B2CA, 0xB19D7978, 0x00000000} pcc_pfw.sys
	When you run Windows XP, you may receive a "Stop 0x0000008E" error message on a blue screen. This error message may appear randomly. You may receive this error message during the Windows XP Setup program or after Windows XP is installed.

0x0000009C MACHINE_CHECK_EXCEPTION

	STOP: 0x0000009C (0x00000030, 0x00000002, 0x00000001, 0x80003CBA) The Pentium and Pentium Pro [and later] processors provide a mechanism to detect and to report hardware-related problems such as memory parity errors and cache errors. To signal a hardware error, the processor signals the detection of a machine check error by generating a machine check exception (Interrupt 18). Note: This article refers to "Windows NT Server or Workstation". Both XP and Vista are versions of "Windows NT", however in the context of this article "Windows NT Server" refers to the much older NT 4.0. This article is fully applicable to Windows XP but Microsoft fail to make that point clear.
	You may receive the following Stop error message in Windows XP: STOP: 0x0000009C (0x00000004, 0x00000000, 0xb2000000, 0x00020151) "MACHINE_CHECK_EXCEPTION" The four parameters inside the parentheses may vary.
	When you shut down a computer that is running the Microsoft Storport storage driver (Storport.sys) in Microsoft Windows Server 2003 Service Pack 2 (SP2), you may receive a "Stop 0x0000009C" error message that resembles the following: *** STOP: 0x0000009C (parameter1, parameter2, parameter3, parameter4) MACHINE_CHECK_EXCEPTION The problem also occurs if you install the updated Storport storage driver that is described in the following article: (http://support.microsoft.com/kb/932755/) An updated Storport storage driver (version 5.2.3790.4021) is available for Windows Server 2003 Note: In typical Microsoft fashion, this article is titled to target Windows Server 2003 SP2, however both the error and the fix apply to x64-based Windows XP. It is not known if this error occurs on 32-bit Windows XP, and if your problem is a Storport driver on a 32-bit XP then there is nothing to stop you from trying the driver fix for 32-bit Windows Server 2003.

0x0000009F DRIVER_POWER_STATE_FAILURE

	A driver is in an inconsistent or invalid power state. 0x0000009F errors are caused when drivers do not handle power state transition requests properly. 0x0000009F occur usually when you are shutting down the machine, resuming from standby or hibernation mode. Specific things to look at include CD/DVD burning software and your machine's power management compatibility and settings.
	You may receive the following error: STOP 0x0000009F DRIVER_POWER_STATE_FAILURE
	You may experience any of the following symptoms: After you click Start, click Shut Down, and then click either Restart or Shut down in the Shut Down Windows dialog box, the computer may begin to shut down but then stop responding (hang). When this occurs, the computer stops at a blank screen. The mouse pointer is displayed, but you cannot move it. The computer does not respond either to mouse movements or to keyboard input; If your floppy disk drive is not present in My Computer, the Standard Floppy Disk Controller device in Device Manager may display the following error status: This device cannot find enough free resources that it can use. (Code 12) The following STOP error message may appear when you shut down from Safe mode: STOP 0x0000009F Driver_Power_State_Failure
	When a computer enters or leaves hibernation or standby, you receive a Stop message that is similar to the following: 0x0000009F: DRIVER_POWER_STATE_FAILURE

0x000000A5 - 0xA5

	You may experience any one of the following symptoms: Your computer automatically restarts. After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. You receive the following "Stop" error message on a blue screen: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: *** STOP: 0x000000A5 (0x00000011, 0x00000006, 0x00000000, 0x00000000) Bug Check Symbolic Name
	When you are installing Windows XP, you may receive the following Stop error: STOP: 0x000000A5 (Parameter1, Parameter2, Parameter3, Parameter4) The ACPI Bios in this system is not fully compliant to the specification. Please read the Readme.txt for possible workarounds, or contact your system vendor for an updated bios. The bios in this system is not fully ACPI compliant. Please contact your system vendor for an updated bios. If you are unable to obtain an updated bios or the latest bios supplied by your vendor is not ACPI compliant, you can turn off ACPI mode during text mode setup. To do this, simply press the F7 key when you are prompted to install storage drivers. The system will not notify you that the F7 key was pressed--it will silently disable ACPI and allow you to continue your installation." The parameters Parameter1, Parameter2, Parameter3, and Parameter4 vary from computer to computer.
	When you are installing Windows XP, you may receive the following Stop error: STOP: 0x000000A5 (Parameter1, Parameter2, Parameter3, Parameter4) The ACPI Bios in this system is not fully compliant to the specification. Please read the Readme.txt for possible workarounds, or contact your system vendor for an updated bios. The bios in this system is not fully ACPI compliant. Please contact your system vendor for an updated bios. If you are unable to obtain an updated bios or the latest bios supplied by your vendor is not ACPI compliant, you can turn off ACPI mode during text mode setup. To do this, simply press the F7 key when you are prompted to install storage drivers. The system will not notify you that the F7 key was pressed--it will silently disable ACPI and allow you to continue your installation." The parameters Parameter1, Parameter2, Parameter3, and Parameter4 vary from computer to computer.

0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY

	A device driver attempted to write to read-only memory.
	When you upgrade a computer that has a Xircom Rex 6000 installed that uses the universal serial bus (USB) cradle, you may receive the following error message when the computer starts in Windows XP for the first time: A Fatal System Error has occurred: 0x000000be (0x80129768, 0x00129121, 0xF96A4754, 0x0000000B) This error may also occur if you connect the USB cradle for the Xircom Rex 6000 to a computer that is running Windows XP, and then you begin the installation process during the hardware identification phase.
	When you try to install the Qwestdex Dex toolbar to your Windows XP-based computer, you may receive the following error message: 0xBE (ATTEMPTED_WRITE_TO_READONLY_MEMORY) in xSides.sys.
	When you use an IEEE 1394-based scanner and run a 32-bit scanning program on a computer that is running Microsoft Windows XP 64-bit, Microsoft Windows Server 2003, you receive an error message on a blue screen that resembles one of the following: 0x0000000A: IRQL_NOT_LESS_OR_EQUAL 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY This problem occurs when the scanning program calls the DeviceIoControl function to send a IOCTL_SCSISCAN_CMD control code to the kernel mode driver. In Windows Vista, you may not experience the blue screen. When your scanning program calls the DeviceIoControl function to send an IOCTL_SCSISCAN_CMD control code to the kernel mode driver in Windows Vista, this call may not be completed successfully, and your scanning program does not work as expected. The exact symptom that is observed in the user interface depends on how your scanning software works when the DeviceIoControl function fails.

0x000000C2 BAD_POOL_CALLER

	Kernel-mode process or driver problem. The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways: By allocating a memory pool size of zero bytes By allocating a memory pool that does not exist By attempting to free a memory pool that is already free By allocating or freeing a memory pool at an IRQL that was too high This Stop message is typically due to a faulty driver or software.
	This article describes how to interpret or read Stop 0xC2 error messages in Microsoft Windows XP. The Stop 0xC2 error message indicates that a kernel-mode process or driver incorrectly tried to perform a memory operation. Typically, faulty device drivers or device software cause this error message.
	This article describes how to debug Stop C2 error messages. Note: This is a Windows 2000 article, however it contains information that can be applied to troubleshooting the same issue in Windows XP.
	After you upgrade to Windows XP on a computer that has an ATI Graphics RAGE FURY MAXX video adapter, your computer may stop responding, and you may receive the following error message: STOP: 0x000000c2 A problem has been detected and Windows has been shut down to prevent damage to your computer. BAD_POOL_CALLER
	You may receive a "0x000000c1" or a "0x000000c2" Stop error message when network traffic is initiated and a filter driver is loaded. For example, this error may occur when you are using firewall software or virtual private network (VPN) software in the following situations: You connect a wireless network adapter by using 802.1X authentication Your firewall is using a filter driver You try to use Microsoft NetMeeting over a VPN connection
	When you upgrade your Compaq Professional Workstation AP550 computer from Microsoft Windows 2000 Professional to Windows XP, either of the following symptoms may occur... DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
	When you work with a network share on a Windows XP-based computer, you may receive the following error message: STOP: 0x000000C2 (Parameter1, Parameter2, Parameter3, Parameter4) BAD_POOL_CALLER

0x000000C4 DRIVER_VERIFIER_DETECTED_VIOLATION - 0xC4

	You may receive the following Stop error message on a blue screen: Fatal System Error: 0x000000C4 (0x00001003, param2, param3, param4) DRIVER_VERIFIER_DETECTED_VIOLATION (c4) Note The three parameters after 0x00001003 that are listed in the parentheses can vary according to the computer's configuration.
	When you use a computer that is running any one of the operating systems that are listed in the "Applies to" section, and you try to use a scanner to scan a document, you may receive the following Stop error message: STOP 0x000000C4 DRIVER_VERIFIER_DETECTED_VIOLATION
	You may receive a Stop error message after you insert media into a removable disk device that is connected to a computer that is running one of the following operating systems: Microsoft Windows Server 2003; Microsoft Windows XP; Microsoft Windows 2000 Professional. The message may also occur if you start the computer when a removable disk device that contains media is connected to the computer. The Stop error message is similar to one of the following messages: STOP 0x0000000A (0x00000004, 0x0000001c, 0x00000001, 0x804324ac) STOP 0x000000D1 (0xffffff20, 0x00000002,0x00000000, 0xbfe5d810) STOP 0x000000C4 (0x00000013, 0x00000fb6, 0x88efb2c0, 0x00000000) STOP 0x00000050 (0xff391000, 0x00000001, 0x804d1017, 0x00000000) Note The parameters for these Stop error messages may vary.

0x000000CA PNP_DETECTED_FATAL_ERROR

On a Microsoft Windows Server 2003-based computer, you may receive an error message that resembles the following:

*** STOP: 0x000000CA (parameter1, parameter2, parameter3, parameter4)
PNP_DETECTED_FATAL_ERROR

You may notice this problem on computers that have native PCI-Express (PCI-E) support enabled in the basic input/output system (BIOS).

Note: This article applies to Microsoft Windows XP Professional x64 Edition.

0x000000CB DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS

See 0x00000076 PROCESS_HAS_LOCKED_PAGES

0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

	A device driver failed to cancel pending operations before exiting.
	When you perform a surprise removal of a universal serial bus (USB) device on a Windows XP Service Pack 2-based computer, you may receive an error message that resembles the following: STOP 0x000000CE (parameter1, parameter2, parameter3, parameter4) DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS Notes: The values of the parameters may vary. A surprise removal means that you remove the device without first notifying the operating system.
	After you start a computer where the video adapter has the TV tuner or video capture feature, the computer may generate the following error message on a blue screen: STOP: 0x000000CE (0xHEXNUM1, 0xHEXNUM2, 0xHEXNUM3, 0xHEXNUM4) in DXAPI.SYS DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
	When you stop the Microsoft Windows Services for Unix version 2.0 NFS Client service that is installed on your Windows XP-based computer, you may receive the following error message on a blue screen: STOP 0x000000ce DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (0xfaa6ad9a, 0x00000000, 0xfaa6ad9a, 0x00000000) The Nfsrdr.sys file may generate the preceding error message while the SFU system is unloading.
	Consider the following scenario. You are using a Bluetooth radio that is connected to a Microsoft Windows XP-based computer. A Bluetooth keyboard or a Bluetooth mouse is connected or has been connected to this radio. Additionally, one or more of the following conditions are true: You connect the radio to the computer. You disconnect the radio from the computer. You use a feature on a portable computer to disable or to re-enable wireless devices. The computer resumes from hibernation. In this scenario, you receive a stop error message that resembles the following: DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP: 0x000000D1 (0X00000410, 0x00000002, 0x00000000,0xF89D6DC7) HIDCLASS.SYS – Address F89D6DC7 base at F89D6000, DateStamp 41107d52 Additionally, you may receive this error message if the 6.02 or a later version of Microsoft IntelliType Pro or Microsoft IntelliPoint software is installed on this computer.

0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL

	The system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error. Note: Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL messages are very similar to 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL messages and the same troubleshooting principles apply. If you cannot resolve your 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL then try the 0x0000000A IRQL_NOT_LESS_OR_EQUAL section.

	On a Microsoft Windows XP-based computer that is using certain network adapter drivers and certain host firewall software, you may receive a Stop 0xD1 error message that resembles the following: STOP 0x000000D1(parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL HTTP.SYS Note: In this message, the parameters that are represented by parameter1, parameter2, and parameter3 may vary.
	When you set the ConnectOnRequestedInterfaceOnly registry entry to 1 on a computer that is running Microsoft Windows XP, you may receive a Stop error message that resembles the following: STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
	Consider the following scenario: You install two network adapters on a computer that is running Microsoft Windows XP. You create a network bridge that uses both of the network adapters. You install network driver interface specification (NDIS) intermediate drivers on the computer. In this scenario, you may receive a Stop error message that resembles the following: STOP 0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL
	When you work with a Windows XP Service Pack 2-based multiprocessor computer, you may receive an error message that resembles the following: STOP 0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL
	On a Microsoft Windows XP Service Pack 1 (SP1)-based computer that has certain wireless network devices installed, you may receive an error message that resembles the following: STOP 0x000000D1(parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL ar5211.sys Note: The parameters that are represented by parameter1, parameter2, and parameter3 in this message may vary.
	When you shut down your computer that has one or more universal serial bus (USB) devices attached to it, you may receive the following error message on a blue screen: Stop 0x000000D1 (0x00000040, 0x00000002, 0x00000000, 0xfc96a9dc)
	When you try to shut down your computer, you may receive a STOP error message on a blue screen that is similar to the following: STOP 0x000000D1, (0x0000002b, 0x00000002, 0x00000000, 0xEEEE1b01) IRQL_NOT_LESS_OR_EQUAL Kbdclass.sys. After you receive this error message, the computer restarts.
	When you switch your Microsoft Windows XP Service Pack 2 (SP2)-based portable computer from AC (utility) power to DC (battery) power, or vice versa, you may receive a Stop error message that is similar to the following: STOP 0x000000D1 (0x0000000C, 0x00000002, 0x00000000, 0xF8E26A89) gv3.sys – Address F8E26A89 base at F8E26000, Datestamp 3dd991eb This problem may also occur at other times, depending on how your system was designed.
	You may receive the following error message on a blue screen on your Windows XP-based computer with the WRQ AtGuard firewall program installed: STOP: 0x000000D1 (0x0200000c, 0x00000002, 0x00000000, 0xf617c2c6) DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
	After you establish a virtual private network (VPN) connection, your computer stops responding unexpectedly. You receive the following Stop error message: STOP: 0x000000D1 (0x00000020, 0x00000002, 0x00000000, 0xf5bf0f68)
	If you add a second Mylex AcceleRAID controller to a Windows XP-based computer, you receive the following error message on a blue screen after the Found New Hardware Wizard starts: STOP 0x000000D1 (0xf8a5802c, 0x00000006, 0x00000000, 0xf847f8a4) DRIVER_IRQL_NOT_LESS_OR_EQUAL When you receive this error message, the computer stops responding (hangs).
	When you copy large files over the network, your computer can restart if Startup And Recovery is set to Automatically Reboot under the System Properties Advanced tab. Otherwise, your computer may generate the following STOP error message: Stop 0X000000D1 (0XBE70D600, 0X00000000,0X00000000,0XBE92F13C) DRIVER_IRQL_NOT_LESS_OR_EQUAL Address BE92F13C Base at BE92C000, date Stamp 394006612 BLACKDRV.SYS
	When you back up data to a tape device on a computer that has a MegaRAID controller and that is running Microsoft Windows Server 2003, Microsoft Windows XP, or Microsoft Windows 2000, you receive a Stop error message that is similar to the following: Stop 0x000000D1 (parameter1, parameter2, parameter3, parameter4) Scsiport.sys
	When your computer resumes from standby, you occasionally receive the following Stop error message: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: *** STOP: 0x000000D1 (0x0000000C, 0x00000002, 0x00000001, 0xF96C49ED) DRIVER_IRQL_NOT_LESS_OR_EQUAL
	When you start or shut down a Microsoft Windows XP-based computer or a Microsoft Windows Server 2003-based computer, you may occasionally receive a Stop error message that is similar to the following: A problem has been detected and Windows has been shut down to prevent damage to your computer... STOP 0x000000D1 (0x00000000, 0x00000002, 0x00000001, 0xf7167161) DRIVER_IRQL_NOT_LESS_OR_EQUAL
	When you start your computer, you may receive the following error message: STOP:0xD1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)
	After you install Laplink PCsync version 2.0 and specify the USB transfer software, when you try to start the PCsync program, the computer displays the following error message and then spontaneously restarts: *** Fatal System Error: 0x000000d1 (0x0000000A,0x00000002,0x00000000,0xFC37664A) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred.
	When you start your Microsoft Windows XP-based computer you may receive the following Stop error message after the Windows XP splash screen appears: Stop 0x000000D1 (0x0000001c, 0x00000002, 0x00000000, 0xf75ba58e) DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.
	When you try to establish a TCP/IP session, your computer may stop responding, and you may receive a "Stop 0xD1" error message.
	You are using a computer that is running Microsoft Windows XP with Service Pack 1 (SP1) or Windows XP with Service Pack 2 (SP2); A program on the computer tries to connect to a Loopback adaptor IP address other than 127.0.0.1. For example, the program may try to connect to IP address 127.0.0.2. When the program tries to connect to the IP address, you may receive the following error message for the Tcpip.sys driver: STOP: 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)
	When your computer restarts after you install Windows XP Home Edition, you may receive either of the following error messages: System has recovered from a serious error DRIVER_IRQL_NOT_LESS_OR_EQUAL
	You may receive a Stop error message after you insert media into a removable disk device that is connected to a computer that is running one of the following operating systems: Microsoft Windows Server 2003; Microsoft Windows XP; Microsoft Windows 2000 Professional. The message may also occur if you start the computer when a removable disk device that contains media is connected to the computer. The Stop error message is similar to one of the following messages: STOP 0x0000000A (0x00000004, 0x0000001c, 0x00000001, 0x804324ac) STOP 0x000000D1 (0xffffff20, 0x00000002,0x00000000, 0xbfe5d810) STOP 0x000000C4 (0x00000013, 0x00000fb6, 0x88efb2c0, 0x00000000) STOP 0x00000050 (0xff391000, 0x00000001, 0x804d1017, 0x00000000) Note: The parameters for these Stop error messages may vary.
	When you shut down a Microsoft Windows XP-based computer, you may receive a "Stop 0xD1 in TCPIP.SYS" error message. You must then turn off and then turn on the computer to recover. User profile changes may be lost. When you restart the computer, you may receive the following error: Windows has recovered from a serious error These symptoms may not occur every time that you shut down the computer.
	On a computer that is running Microsoft Windows XP, you may experience any of the following symptoms: Symptom 1 Your computer restarts unexpectedly. Symptom 2 After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. Symptom 3 You receive the following Stop error message: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: *** STOP: 0x000000D1 (0xDBDBDBF9, 0x00000002, 0x00000000, 0xED3A6DF2 DRIVER_IRQL_NOT_LESS_OR_EQUAL The symptoms of a Stop error vary according to your computer's system failure options. Additionally, the four parameters may vary according to the computer's configuration. These parameters appear in the error signature information and within the parentheses of the Stop error message.
	On a Windows Server 2003-based computer, you receive the following Stop error message on a blue screen: 0x000000D1 (parameter1, parameter2, parameter3, parameter4) DRIVER_IRQL_NOT_LESS_OR_EQUAL Notes: The parameters in this error message vary, depending on the computer's configuration. Not all "0x000000D1" Stop errors are caused by this problem. This problem occurs when the Storport.sys driver is called to pause or to resume an adapter in a Windows Server 2003-based computer. Additionally, storage driver developers may encounter symptoms of this issue when their drivers perform similar operations. Note: In typical Microsoft fashion, this article is titled to target Windows Server 2003 SP2, however both the error and the fix apply to x64-based Windows XP. It is not known if this error occurs on 32-bit Windows XP, and if your problem is a Storport driver on a 32-bit XP then there is nothing to stop you from trying the driver fix for 32-bit Windows Server 2003.
	After you use the Safely Remove Hardware feature to remove a USB storage device, you receive the following error message when you disconnect the device from the computer: *** STOP: 0x000000D1 (0x00000014, 0x00000002, 0x00000000, 0xb777a275) DRIVER_IRQL_NOT_LESS_OR_EQUAL You experience this problem if the following conditions are true: The computer is running Microsoft Windows Server 2003 Service Pack 1 (SP1). The storage device contains an encrypted volume that uses the FAT file system. Note: As with the previous article, this also applies to x64-based Windows XP.

0x000000D5 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL - 0xD5

	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 use an IP Phone program on a Toshiba computer that is running Microsoft Windows XP Service Pack 2 (SP2) or on a Tablet PC that is running Microsoft Windows XP Tablet PC Edition 2005, and then you try to close the connection, the IP Phone may not hang up. Note The Windows XP SP2 features and components are included in Windows XP Tablet PC Edition 2005. If you repeatedly try to close the connection, the computer may quit unexpectedly. You may also experience one or more of the following symptoms: Your computer automatically restarts. After you log on, you receive the following: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. If you click the click here link at the bottom of the message box, you receive error signature information that is similar to the following: BCCode : 000000D5 BCP1 :82672F60 BCP2 :00000001 BCP3 :F85A04DD BCP4 :00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

0x000000D8 DRIVER_USED_EXCESSIVE_PTES

The Stop 0xD8 message typically occurs if your computer runs out of page table entries (PTEs) due to a driver that requests large amounts of kernel memory. See 0x0000003F

0x000000DA SYSTEM_PTE_MISUSE

A computer with the /3GB switch in the Boot.ini file and multiple small computer system interface (SCSI) controllers stops responding and a SYSTEM_PTE_MISUSE (0xDA) stop error occurs. This problem does not occur on a computer with one controller or a computer that does not have /3GB switch in the Boot.ini file.

0x000000E3 - 0xE3

After you install Windows XP Service Pack 2, you may experience any one of the following symptoms when you safely remove an encrypted USB storage device:

Your computer automatically restarts.
After you log on, you receive the following error message:

Microsoft Windows

The system has recovered from a serious error.

A log of this error has been created.

Please tell Microsoft about this problem.

We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous.

To see what data this error report contains, click here.

You receive the following Stop error message:

A problem has been detected and Windows has been shut down to prevent damage to your computer...

Technical information:

*** STOP: 0x000000E3 (0x82175704, 0x82282da8, 0x00000000, 0x00000002)
Bug Check Symbolic Name

0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER

	A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver.
	You may receive one of the following Stop error messages: STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER STOP: 0x100000EA THREAD_STUCK_IN_DEVICE_DRIVER_M
	When you run a video-intensive program, such as a movie or a video game, you may receive one of the following stop error messages and bugcheck information: STOP 0x000000EA, (0x81774538, 0x81a8fc78, 0x8193e490,0x00000001) THREAD_STUCK_IN_DEVICE_DRIVER Note that the four parameters after the stop code may be different.
	After you enter and resume from standby, hibernate, or both multiple times, you may receive a "Stop 0xEA" error message.

0x000000ED UNMOUNTABLE_BOOT_VOLUME

	The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This error might also occur during an upgrade to Windows XP on systems that use higher throughput ATA disks or controllers with incorrect cabling. In some cases, your system might appear to work normally after you restart. This error is closely related to 0x0000007B. You may also have to perform disk error checking.
	When you use volumes that use the NTFS file system on integrated device electronics (IDE) drives with caching enabled, you may receive the following error message during startup: Stop 0x000000ED Unmountable_Boot_Volume
	When you first restart your computer during the upgrade to Windows XP or when you start Windows XP, you may receive the following error message, where aaaaaaaa, bbbbbbbb, cccccccc, and dddddddd are hexadecimal numbers that may vary: STOP 0x000000ED (0xaaaaaaaa, 0xbbbbbbbb, 0xcccccccc, 0xdddddddd) UNMOUNTABLE_BOOT_VOLUME
	When booting up to Win XP you may get a error that reads "Unmountable Boot Volume".
	The bootcfg command is a Microsoft Windows XP Recovery Console command that manipulates the Boot.ini file. This command has a function that can scan your hard disks for Microsoft Windows NT 4.0, Microsoft Windows 2000, and Windows XP installations, and then add them to an existing Boot.ini file. The function can also rebuild a new Boot.ini file if one does not exist. With the bootcfg command, additional Boot.ini file parameters can be added to existing or new entries.

0x000000F2 HARDWARE_INTERRUPT_STORM

	The kernel has detected an interrupt storm. An interrupt storm occurs when a level-interrupt-triggered device fails to release an interrupt request (IRQ). This can result from a number of causes.
	Your computer may hard hang (it may be completely frozen and unresponsive) and you may receive the following error message: STOP: 0x000000F2 (0xFCA7C55C, 0x817B9B28, 0x817D2AA0, 0x00000002) An interrupt storm has caused the system to hang. Address FCA7C55C base at FCA72000, Datestamp 3A72BDEF - ACPI.sys

0x000000F4 - 0xF4

	A computer that is running Microsoft Windows XP or a later operating system stops responding during resume from standby, and you receive one of the following stop error messages: 0x0000007a (e163a3e4,c000000e,bf8e9313,0697f860 0x000000F4 (0x00000003, Parameter2, Parameter3, Parameter4)
	When you click a window or when you resize a window, Windows XP stops responding (hangs). You experience this symptom if the following conditions are true: The window overlaps another window. The computer has a dual-core processor or a hyper-threading processor. The Windows Classic theme is applied. Note: To determine whether the Windows Classic theme is applied, right-click an empty area on the desktop, click Properties, and then click the Themes tab. The current desktop theme is listed in the Theme box.

0x000000FC ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

When you use a Microsoft Windows XP Service Pack 2 (SP2)-based computer or Windows XP Tablet PC Edition 2005, you may receive an error message that is similar to the following:

0x000000FC (ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY)

Or, you may receive a Stop error after you install new hardware on a computer that supports hardware Data Execution Prevention (DEP).

0x000000FE BUGCODE_USB_DRIVER - 0xFE

	When you try to start a third-party Internet Protocol (IP) telephone program, you may receive a Stop 0x000000FE error message on a blue screen.
	When a computer that is running Windows XP is accessing USB 2.0 hard disks under heavy stress conditions, you may receive a bugcheck 0xFE message similar to the following: BUGCODE_USB_DRIVER (fe)
	If you use two universal serial bus (USB) streaming-video cameras at the same time on a Microsoft Windows XP Service Pack 2 (SP2)-based computer, you may receive the following Stop error message: STOP 0x000000FE (Parameter1, Parameter2, Parameter3, Parameter4) This problem occurs when the capture program that you use closes.
	When your Microsoft Windows XP-based computer returns from standby or from hibernation, you may receive a "STOP 0xFE" error message. This problem may occur if all the following conditions are true: You are using Windows XP Professional with Service Pack 1. You installed the update that is described in the following Microsoft Knowledge Base article: (http://support.microsoft.com/kb/822603/) Availability of the Windows XP S822603 USB 1.1 and 2.0 update You removed the universal serial bus (USB) 2.0 Enhanced Host Controller (EHCI) controller from Device Manager. For example, you may have removed the controller because Device Manager displayed an exclamation point in a yellow circle next to the listing for the controller. The details report displayed "Code 10". Note: The name of your USB 2.0 EHCI controller may vary.

0xC0000218 UNKNOWN_HARD_ERROR

	One of the core Windows system hives (the SAM hive, the SECURITY hive, the SOFTWARE hive, or the DEFAULT hive) is corrupt.
	This article describes how to recover a Windows XP system that does not start because of corruption in the registry. This procedure does not guarantee full recovery of the system to a previous state; however, you should be able to recover data when you use this procedure.
	This article describes how to troubleshoot registry corruption issues. If your computer does not restart, the registry hives may be corrupted. The error messages may vary. They can include any of the following: Windows could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEM.ced Windows could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEM Windows could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SOFTWARE System hive error Stop 0xc0000218 (0xe11a30e8, 0x00000000, 0x000000000, 0x00000000) UNKNOWN_HARD_ERROR Stop: 0xc0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\CorruptHive or its log or alternate. It is corrupt, absent, or not writable.
	When a registry hive becomes damaged, your computer may become unbootable, and you may receive one of the following Stop error messages on a blue screen: Unexpected Shutdown; Stop:0xc0000135 Also see: After you install Microsoft Windows XP Service Pack 2 (SP2), your computer repeatedly restarts with the following Stop error: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: STOP: c0000135 {Unable To Locate Component} This application has failed to start because winsrv was not found. Re-installing the application may fix this problem. Note Your computer may restart immediately if it is configured to automatically restart when a system failure occurs. To turn off this option so that your computer does not restart, press F8 at startup, use the arrow keys to select the Disable automatic restart on system failure option, and then press ENTER.
	When you try to install Microsoft Windows XP on a new hard disk that is formatted with the NTFS file system, you may receive the following error: Stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\SOFTWARE or its log or alternate This error occurs after Windows XP copies the installation files to the hard disk and the computer restarts.

0x4000008A

If you install Windows XP by using a Pre-Boot Execution Environment (PXE) network adapter or by using a remote boot floppy from a Remote Installation Services (RIS) server, the installation process may stop responding (hang) at the "Setup is Starting Windows" screen. A few seconds after this message appears, the screen may suddenly go black. You may also receive the following Stop error message on a blue screen:

STOP: 0x4000008a (0x822bcda8, 0x823978b0, 0x00000000, 0x00000000)
A kernel thread terminated to protect your system mutax.

NOTE: The four parameters that are inside the parentheses can vary according to the computer's configuration.

0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED

	Problem when switching from kernel mode to user-mode. The Stop 0xC000021A message occurs when Windows XP switches into kernel mode and a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is compromised and security can no longer be guaranteed. Because Windows XP cannot run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can cause the system to stop responding. You cannot use the kernel debugger in this situation because the error occurred in a user-mode process. A Stop 0xC000021A message can also occur when the computer is restarted after a system administrator has modified permissions in such a way that the SYSTEM account no longer has adequate permissions to access system files and folders.
	You may receive the following error message: STOP: c000021a {Fatal System Error} The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000034 (0x00000000 0x0000000) The system has been shutdown. Note The parameters in parentheses are specific to your computer configuration and may be different for each occurrence.
	If Microsoft Internet Explorer maintenance policies are being applied, you may receive a "Stop C000021A" error message on a blue screen on a Windows XP-based client computer during the logon process. Or, the client computer may restart. This problem may not occur until you log on and log off several times. You may also receive the following error message: STOP: 0xc000021a STATUS_SYSTEM_PROCESS_TERMINATED {Fatal System Error} The Windows Logon Process system process terminated unexpectedly with a status of 0xaaaaaa (0xbbbbbb 0xcccccc) The system has been shutdown.
	This article describes error messages that you may receive after you modify some security permissions on your computer that is running Microsoft Windows Server 2003, Windows XP, or Windows 2000. This article discusses how to resolve these issues on each operating system. It also discusses how to resolve a paging file issue that you may experience after you resolve the security permissions issue.
	You use a smart card for user authentication on a computer that is running either Microsoft Windows XP Service Pack 1 (SP1) or Windows XP Service Pack 2 (SP2). You insert the smart card in to the reader and type the PIN to initiate the log on process. You remove the smart card before the log on process is completed. You insert the smart card again. In this scenario, a stack corruption occurs, and the computer stops responding (hangs). Additionally, you receive the following error message: STOP: 0xc000021a {Fatal System Error}
	After you install Roxio GoBack (included with Norton System Works), and attempt to start your computer, you may receive an error message similar to the following: C000021a (fatal system error). The session manager initialization system process terminated unexpectedly with a status of 0xc000003a (0x00000000, 0x00000000) Your computer starts normally in Safe mode, but a clean boot from MSConfig has no effect.
	When you try to unlock your computer by pressing CTRL+ALT+DELETE, your computer restarts unexpectedly. You may receive the following Stop error: STOP: c000021a (Fatal System Error) The Windows Logon Process System process terminated unexpectedly with a status of 0xc0000005 (0x0000000 0x00000000).The system has been shut down.

0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH

	This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory and other hardware such as hard disks can also cause this Stop message to appear.
	When you start Windows XP, you may receive one of the following error messages: STOP: 0xc000026C [Unable to load device driver] DriverName STOP: 0xc0000221 [Unable to load device driver] DriverName STOP: 0xc0000221. Bad image check sum, the image user32.dll is possibly corrupt. The header check sum does not match the computed check sum.
	You may receive any one of the following Stop error messages: STOP: C0000221 unknown hard error Path\File_name STOP: 0xC0000221 unknown hard error C:\Winnt\System32\Ntdll.dll (or another specific file or driver) STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH Path\File_name
	When you upgrade your computer to Windows XP, you may receive an error message that is similar to one of the following: C0000221 (Bad Image Checksum) STOP: C0000221 - Bad Image Checksum in ModuleName STOP: C0000221 - Bad Image Checksum. User32.dll is possibly corrupt. The header check sum does not match the computed check sum.

0xC0000244 STATUS_AUDIT_FAILED

	Consider the following scenario: You have a Microsoft Windows XP-based computer. In Windows XP, the value for the following registry subkey is set to 1: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ Lsa\crashonauditfail You log on to the computer as a non-administrative user. You try to clear or to back up the Security log. Exactly at the same time, an event is logged in the Security log. In this scenario, you receive a Stop error message that resembles the following: Stop 0xC0000244 (STATUS_AUDIT_FAILED) You receive the Stop error message even though the Security log is not full.
	During the graphical user interface (GUI) portion of an upgrade from Microsoft Windows 2000 Professional to Windows XP, you may receive the following error message on a blue screen: Stop 0xC0000244 Unable to generate security events.

0xC000026C

See: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH

0xC0000415

Microsoft Windows XP may shut down unexpectedly, and you may receive the following Stop error:

0xc0000415 0xe1035170 0x00000000 0x00000000 0x00000000

Other Stop Errors

When a SCSI miniport driver initializes on your computer, your computer may stop responding, and you may receive a Stop error in the Scsiport.sys file.

This article does not specify a stop error code.