Resources to assist in fault-finding stop errors in Windows XP. If you are unfamiliar with fault-finding Stop errors, read the Stop Message Checklist TechNet article. The Check Your Software TechNet article provides useful software-related techniques that you can use to recover from problems that cause Stop messages. Additionally the TechNet Check Your Hardware article provides similar useful information for hardware.
This article describes how to use a sample debugging session to determine which specific driver is causing the following error message: Stop Error IRQL_NOT_LESS_OR_EQUAL (0xA).
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.
This article discusses how to troubleshoot the following Stop error in Windows XP: Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL*** Address x has base at x - filename.
Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL (TechNet article)
The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.
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 XP Setup, you may receive an error message similar to the following: STOP: 0x0000001E (0x80000003, 0xBFC0304, 0x0000000, 0x0000001) [bugcheck code] (   )
When you restart your computer after you install new software or drivers, you may receive one of the following error messages on a blue screen STOP: 0x23 (0x000e0100, 0xf466a978, 0xf466a678, 0xf87c7625) or STOP: 0x24 (0x000e0100, 0xf466a978, 0xf466a678, 0xf87c7625) NOTE: The preceding parameters may vary according to the configuration of your computer.
Stop 0x00000024 or NTFS_FILE_SYSTEM (TechNet article)
The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.
0x0000002E or DATA_BUS_ERROR (TechNet article)
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 can also indicate hard disk damage caused by viruses or other problems.
0x0000003F or NO_MORE_SYSTEM_PTES (TechNet article)
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.
This is a rather nasty error that could be caused by just about anything, including busted audio drivers, incompatible video drivers, bad or corrupt hard disk, and faulty hardware such as bad RAM. The error may be triggered by an event such as plugging in a USB device, but the problem is, the fault may not lie with the device that was actually plugged in. Worse still, other errors can mask this one. The point is, the crash may be a symptom of some other problem, or another crash might prevent you from seeing this one.
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.
Also see the Cannot Start XP article on this site.
When you are running Windows XP, you may receive one of the following error messages: Stop 0x00000077 KERNEL_STACK_INPAGE_ERROR This article describes how to troubleshoot these error messages.
Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR (TechNet article)
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.
Read this article for more information on Disk Data Corruption.
0x00000079 or MISMATCHED_HAL (TechNet article)
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 mismatched single and multi-processor configuration files are copied to the system.
A Windows XP-based computer stops responding during resume from standby, and you receive the following KERNEL_DATA_INPAGE_ERROR stop error message: 0x0000007a (e163a3e4,c000000e,bf8e9313,0697f860) This problem occurs on a system where Windows XP is installed on a hard disk that is configured as a subordinate ("slave"), and no other device is connected to the same IDE controller channel (primary or secondary).
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR (TechNet article)
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 disk or controller drivers, firmware, or hardware.
When you start your Microsoft Windows XP-based computer after you replace the motherboard on the computer, you may receive a STOP error message similar to the following: STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE
This step-by-step article describes how to troubleshoot "Stop 0x0000007B" error messages in Windows XP. A "Stop 0x0000007B" error message may appear on a blue screen when you start your computer. The error message includes the following information: STOP: 0x0000007B (parameter1, parameter2, parameter3, parameter4) 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 or INACCESSIBLE_BOOT_DEVICE (TechNet article)
After you upgrade your computer to Windows XP, you may receive the following STOP error message on a blue screen: 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 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 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.
0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP (TechNet article)
The Stop 0x7F message indicates that 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); Software problems; Hardware failures.
This is a very common bug check. To interpret it, you must identify which exception was generated.
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
0x0000009F or DRIVER_POWER_STATE_FAILURE (TechNet article)
The Stop 0x9F message indicates that a driver is in an inconsistent or invalid power state.
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.
If you install the Qwestdex Dex toolbar to your Windows XP-based computer that is in Microsoft Windows Millennium Edition (Me), Microsoft Windows 98 or Microsoft Windows 95 Application Compatibility mode and you have less than 256 megabytes (MB) of RAM, you may receive the following error message on a blue screen when you restart your computer: 0xBE (ATTEMPTED WRITE_TO_READONLY_MEMORY) in xSides.sys.
0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY (TechNet article)
The Stop 0xBE message indicates that a driver attempted to write to read-only memory.
When you upgrade your Compaq Professional Workstation AP550 computer from Microsoft Windows 2000 Professional to Windows XP, either of the following symptoms may occur...
How to Debug a Stop 0xC2 or Stop 0x000000C2 Error (Windows 2000 article)
This article explains how to debug Stop C2 errors. The Stop 0xC2 error message indicates that a kernel-mode process or driver incorrectly attempted to perform a memory operation. This error message is typically caused by a faulty device driver or software.
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.
While you browse the Internet, your computer may restart unexpectedly. This behavior can occur if both of the following conditions are true: A broadband cable modem or an asymmetric digital subscriber line (ADSL) modem is installed on your system, and the modem is using drivers that cause a fatal system (STOP) error. NOTE: Depending on your system configuration, the resulting blue-screen error message may not be displayed long enough for you to record the error information. -and- The Automatically restart check box is selected under System failure in the Startup and Recovery dialog box (under System Properties).
Stop 0xC2 or BAD_POOL_CALLER (TechNet article)
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.
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.
0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (TechNet article)
This Stop message indicates that a driver failed to cancel pending operations before exiting.
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).
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
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.
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)...
When you start your computer, you may receive the following error message: STOP:0xD1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)
A Windows XP-based computer may restart after you quickly insert and remove a PC Card media adapter, and you may receive a "DRIVER_IRQL_NOT_LESS_OR_EQUAL" stop error message...
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 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.
Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL (TechNet article)
The Stop 0xD1 message indicates that 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.
0x000000D8 or DRIVER_USED_EXCESSIVE_PTES (TechNet article)
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.
You may receive one of the following error messages on a blue screen: STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER -or- 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.
Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER (TechNet article)
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.
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: 0x000000ED UNMOUNTABLE_BOOT_VOLUME...
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...
Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME (TechNet article)
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 Professional 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.
Also see the Dealing with Data Corruption article on this website. It covers Disk Error Checking , Recovery Console, System File Checker and Disaster Recovery Tools.
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.
Stop 0x000000F2 or HARDWARE_INTERRUPT_STORM (TechNet article)
The Stop 0xF2 message occurs if the kernel detects 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.
When you start Microsoft Windows XP Home Edition, you may receive the following error message: Unhandled Exception c0000005 at address: 100016b8.
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.
Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATED (TechNet article)
The Stop 0xC000021A message occurs when Windows XP Professional 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 Professional 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 any of the following STOP error messages: STOP: C0000221 unknown hard error Path\File_name -or- STOP: 0xC0000221 unknown hard error C:\Winnt\System32\Ntdll.dll (or another specific file or driver) -or- STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH Path\File_name.
When you start Windows XP, you may receive one of the following error messages: STOP: 0xc000026C [Unable to load device driver] DriverName -or- STOP: 0xc0000221 [Unable to load device driver] DriverName -or- STOP: 0xc0000221. Bad image check sum, the image user32.dll is possibly corrupt. The header check sum does not match the computed check sum. DriverName is the name of the device driver file.
0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH (TechNet article)
This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this Stop message to appear.
A Stop 0xc0000218 error message means that a necessary registry hive file could not be loaded. This error message can occur if the file is corrupt or missing. To resolve this issue, you can reinstall the operating system and restore the registry files from a backup. The registry files may have been corrupted because of hard disk corruption or some other hardware problem. This error message can also occur if the driver has corrupted the registry data while loading into memory, or the memory where the registry is loading has a parity error. In the latter case, turn off the external cache and check the memory chips.