Export (0) Print
Expand All

Troubleshooting specific Stop messages

Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Troubleshooting specific Stop messages

This topic discusses how to troubleshoot specific Stop messages. For general information about troubleshooting Stop messages, and for a list of other sources of information, see Troubleshooting Stop messages: general strategies.

You can use the System Information tool to gather important information about system settings, problem devices, and hardware resources. For more information, see System Information.

What Stop message are you receiving?

Stop message 0x0000001E Descriptive text: KMODE_EXCEPTION_NOT_HANDLED

Usual cause: This message has several possible causes.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. Check that you have adequate disk space, especially for new installations.

  3. Disable any newly installed drivers. You might also want to disable a service associated with the driver or any newly installed programs.

  4. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

  5. Ensure that you have the latest system BIOS (for x86-based and x64-based computers) or the correct firmware (for Itanium architecture-based computers). Contact your hardware manufacturer if you need assistance in performing this step.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x0000001E.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0x000000D1 Descriptive text: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual cause: An attempt was made to touch pageable memory at a process internal request level (IRQL) that was too high. This is usually caused by drivers using improper addresses. Kernel-mode drivers are forbidden to access pageable memory at a high IRQL.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. Use the File Signature Verification tool, which identifies unsigned drivers and incompatible system files on your computer. The system files and device driver files that are provided with the Windows Server 2003 family have a Microsoft digital signature, which indicates that the files are original, unaltered system files or that they have been approved by Microsoft for use with Windows. For more information, see Using File Signature Verification.

  3. Use Device Manager to roll back to a previous version of the driver. For more information, see Roll back to the previous version of a driver.

  4. Disable the driver identified in the Stop message or any newly installed drivers.

  5. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

  6. Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, go to the see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x000000D1.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0x000000EA Descriptive text: THREAD_STUCK_IN_DEVICE_DRIVER

Usual cause: The display driver is caught in an infinite loop. This usually indicates a problem with the video hardware or with the display driver.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. Disable the driver identified in the Stop message or any newly installed drivers.

  3. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

  4. Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x000000EA.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0x00000050 Descriptive text: PAGE_FAULT_IN_NONPAGED_AREA

Usual cause: Requested data is not found in memory. This might be caused by a printer driver or remote access driver.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. Use Device Manager to roll back to a previous version of the driver. For more information, see Roll back to the previous version of a driver.

  3. Disable any newly installed drivers.

  4. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

  5. Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x00000050.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0x000000BE Descriptive text: ATTEMPTED_WRITE_TO_READONLY_MEMORY

Usual cause: A device driver attempted to write to read-only memory. This problem can occur during an upgrade, although it is not limited to upgrades.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.

  3. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x000000BE.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0x0000000A on an existing installation Descriptive text: IRQL_NOT_LESS_OR_EQUAL

Usual cause: Drivers are using improper memory addresses.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. If you can start the operating system, check the System Log in Event Viewer for additional information that might help determine the device or driver that is causing the problem. To open Event Viewer, click Start, click Control Panel, double-click Administrative Tools, and then double-click Event Viewer.

  3. Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.

  4. Disable any newly installed drivers and remove any newly added programs.

  5. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

  6. Remove any newly installed hardware (RAM, adapters, hard disks, modems, and so on).

  7. Ensure that you have updated drivers for your hardware devices. Also, ensure that you have the latest system BIOS (for x86-based and x64-based computers) or the correct firmware (for Itanium architecture-based computers). The device manufacturers can assist you in obtaining these items.

  8. Run system diagnostics supplied by your hardware vendor, especially a memory check.

  9. Disable memory caching in the BIOS (for x86-based and x64-based computers) or EFI (for Itanium architecture-based computers). Contact your hardware manufacturer if you need assistance in performing this step.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x0000000A.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0x0000000A on a new installation Descriptive text: IRQL_NOT_LESS_OR_EQUAL

Usual cause: Drivers are using improper memory addresses.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. During the installation process, at the "Setup is inspecting your computer's hardware configuration" message, press F5. Select the correct computer type when you are prompted. For example, if you have a single-processor computer, select Standard PC.

  3. Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.

  4. Disable memory caching in the BIOS (for x86-based and x64-based computers) or EFI (for Itanium architecture-based computers). Contact your hardware manufacturer if you need assistance in performing this step.

  5. Remove all adapters and disconnect all hardware devices that are not essential.

  6. If you are using a SCSI adapter, obtain the latest driver from the adapter vendor, disable sync negotiation, check termination, and check the SCSI IDs of the devices.

  7. If you are using Integrated Device Electronics (IDE) devices, define the onboard IDE port as the primary channel. Check the master/subordinate settings for the IDE devices. Remove all IDE devices except for the hard disk. See your hardware manufacturer's documentation for more information.

  8. Run the system diagnostics supplied by your hardware vendor, especially the memory check.

  9. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x0000000A.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop messages 0x00000023 and 0x00000024 Descriptive text: FAT_FILE_SYSTEM or NTFS_FILE_SYSTEM

Usual cause: The hard disk is fragmented or there is excessive file I/O. This Stop error may also be cause by drive-mirroring or some antivirus software.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. Disable any antivirus or backup programs, and disable any defragmentation utilities.

  3. Check for hard disk corruption by running chkdsk and then restarting the computer. If you cannot run chkdsk, you might have to move the hard disk to another computer that is running a product in the Windows Server 2003 family and then run the chkdsk command. For more information, see chkdsk. (Note that chkdsk is available, with a limited set of options, in Recovery Console.)

  4. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

Note

  • You can search the Microsoft Web site for updated information on these Stop messages. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x00000023 or stop 0x00000024.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0x0000007B Descriptive text: INACCESSIBLE_BOOT_DEVICE

Usual cause: A problem occurred during the initialization of the I/O system (usually the startup device or the file system).

Solution:

  1. Check for viruses on your computer. This Stop message is frequently displayed when there is a virus in the boot sector.

  2. Repair or recover the hard disk. For ways to fix the hard disk, see Repair overview and Recovery Console overview.

  3. Remove any newly added hard disks or controllers.

  4. If you are using a SCSI adapter, obtain the latest driver from the adapter vendor, disable sync negotiation, check termination, and check the SCSI IDs of the devices.

  5. If you are using Integrated Device Electronics (IDE) devices, define the onboard IDE port as the primary channel. Check the master/subordinate settings for the IDE devices. Remove all IDE devices except for the hard disk. See your hardware manufacturer's documentation for more information.

  6. Check for hard disk corruption by running chkdsk. If you cannot run chkdsk, you might have to move the hard disk to another computer that is running a product in the Windows Server 2003 family and then run the chkdsk command. For more information, see chkdsk. (Note that chkdsk is available, with a limited set of options, in Recovery Console.)

  7. If the computer will not start normally, try starting it in Last Known Good Configuration. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x0000007B.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0x0000007F Descriptive text: UNEXPECTED_KERNEL_MODE_TRAP

Usual cause: There is a hardware or software problem. This is usually caused by a hardware failure.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. Run system diagnostics supplied by your hardware vendor, especially a memory check. This Stop message is often displayed in the case of faulty or mismatched memory.

  3. Disable memory caching in the BIOS (for x86-based and x64-based computers) or EFI (for Itanium architecture-based computers). Contact your hardware manufacturer if you need assistance in performing this step.

  4. Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.

  5. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x0000007F.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0x0000009F Descriptive text: DRIVER_POWER_STATE_FAILURE

Usual cause: A driver is in an inconsistent or invalid power state.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. Disable the driver identified in the Stop message or any newly installed drivers.

  3. Update any software that uses filter drivers, such as antivirus or backup programs.

  4. Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.

  5. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, go to the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0x0000009F.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0xC000021A Descriptive text: FATAL_SYSTEM_ERROR

Usual cause: The Windows Logon Process system process terminated unexpectedly.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. Disable the driver identified in the Stop message or any newly installed drivers.

  3. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

  4. Confirm that your hardware is designed for the Windows Server 2003 family by clicking the appropriate link in Support resources.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0xC000021A.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0xC0000221 Descriptive text: BAD_IMAGE_CHECKSUM

Usual cause: This message might be caused by a corrupted system file or driver or a hardware problem.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. Replace the identified file.

  3. If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then replace the file. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0xC0000221.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Stop message 0xC0000218 Descriptive text: UNKNOWN_HARD_ERROR

Usual cause: A registry file might be corrupted.

Solution:

  1. Use the Online Crash Analysis tool at the Microsoft Web site. You can use this tool to send error reports to Microsoft and track their status by using your Microsoft Passport information. You can access the Online Crash Analysis Web site by using the Error Reporting service or by using your Web browser. When it is enabled, the Error Reporting service monitors your system for kernel and user mode faults that are related to operating system components and applications. With kernel-mode reporting, you can obtain more information about the problem or condition that caused the Stop error. For more information, see System and program error reporting overview.

  2. If the computer will not start normally, try starting it in Last Known Good Configuration. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

    Important

    • When you use Last Known Good Configuration, system setting changes made after the last successful startup are lost.

  3. If you have an Automated System Recovery (ASR) backup, you might need to use this recovery option. For more information, see Automated System Recovery (ASR) overview.

Note

  • You can search the Microsoft Web site for updated information on this Stop message. To do this, see Welcome to Microsoft Help and Support at the Microsoft Web site, click a search option, and then follow the instructions on the page. When typing keywords, use stop 0xC0000218.

    For more information about articles, troubleshooting wizards, and items you can download, see Updated technical information.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft