Troubleshooting Stop Messages : Common Stop Messages (part 4)

15. Stop 0xCE or DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

This Stop message indicates that a driver failed to cancel pending operations before exiting.

15.1. Interpreting the Message

This Stop message has four parameters:

15.2. Resolving the Problem

Stop 0xCE messages can occur after you install faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to resolve the error. If disabling or removing drivers resolves the error, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

Note:

MORE INFO For more information about Stop 0xCE messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x000000CE and 0xCE.

16. Stop 0xD1 or IRQL_NOT_LESS_OR_EQUAL

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.

16.1. Interpreting the Message

This Stop message has four parameters:

16.2. Resolving the Problem

Stop 0xD1 messages can occur after you install faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to resolve the error. If disabling or removing drivers resolves the error, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

Note:

MORE INFO For more information about Stop 0xD1 messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x000000D1 and 0xD1.

17. Stop 0xD8 or DRIVER_USED_EXCESSIVE_PTES

The Stop 0xD8 message typically occurs if your computer runs out of PTEs because a driver requests large amounts of kernel memory.

17.1. Interpreting the Message

Depending on the configuration of your system, the number of parameters returned might vary. The four possible values are:

17.2. Resolving the Problem

Note:

MORE INFO For more information about Stop 0xD8 messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x000000D8 and 0xD8.

18. Stop 0xEA or THREAD_STUCK_IN_DEVICE_DRIVER

In Stop 0xEA errors, 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.

18.1. Interpreting the Message

This Stop message has four parameters:

18.2. Resolving the Problem

Stop 0xEA messages can occur after you install faulty drivers (especially video drivers) or system services. If a driver is listed by name, disable, remove, or roll back that driver to resolve the error. If disabling or removing drivers resolves the error, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

Note:

MORE INFO For more information about Stop 0xEA messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x000000EA and 0xEA.

19. Stop 0xED or UNMOUNTABLE_BOOT_VOLUME

The kernel-mode I/O subsystem attempted to mount the boot volume and failed. This error might also occur during an upgrade to Windows 7 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.

19.1. Interpreting the Message

This Stop message has two parameters:

19.2. Resolving the Problem

The following suggestions are specific to Stop 0xED errors. For additional troubleshooting suggestions that apply to all Stop errors.

• If you are using higher-throughput ATA disks and controllers, which are those capable of data transfer rates above 33.3 MB/sec, replace the standard 40-pin cable with an 80-pin cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3 MB/sec, but it is mandatory for higher transfer rates. The additional grounded pins are required to avoid data loss.

• Some firmware allows you to force higher transfer rates even when you are using the incorrect cable type. Your firmware might issue a warning but allow the startup process to proceed. Restore the default firmware setting for ATA cable detection.

• Problems that cause 0xED errors might also cause Stop 0x7B errors.
  

Note:

MORE INFO For more information about Stop 0xED messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x000000ED and 0xED.

20. Stop 0xFE or BUGCODE_USB_DRIVER

The Stop 0xFE message occurs if the kernel detects an error in a USB driver.

20.1. Interpreting the Message

This Stop message has four parameters. Parameter 1 indicates the type of violation, whereas parameters 2 through 4 provide more information specific to that error type. Typically, only parameter 1 is useful to system administrators, although parameters 2 through 4 might be useful to Microsoft developers, who will be able to extract that information from the memory dump.

Parameter 1 can have a value of 0x1 to 0x5, as described here:

20.2. Resolving the Problem

The following suggestions are specific to Stop 0xFE errors. For additional troubleshooting suggestions that apply to all Stop errors.

To resolve this problem, follow these procedures:

Note:

MORE INFO For more information about Stop 0xFE messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x000000FE and 0xFE. Specifically, refer to Knowledge Base article 934374.

21. Stop 0x00000124

The Stop 0x00000124 message occurs when Windows has a problem handling a PCI-Express device. Most often, this occurs when adding or removing a hot-pluggable PCI-Express card; however, it can occur with driver- or hardware-related problems for PCI-Express cards.

21.1. Resolving the Problem

To troubleshoot 0x00000124 stop errors, first make sure you have applied all Windows updates and driver updates. If you recently updated a driver, roll back the change. If the stop error continues to occur, remove PCI-Express cards one by one to identify the problematic hardware. When you have identified the card causing the problem, contact the hardware manufacturer for further troubleshooting assistance. The driver might need to be updated, or the card itself could be faulty.

Note:

MORE INFO For more information about Stop 0x00000124 messages, see the Knowledge Base at http://support.microsoft.com/. Search using the keyword 0x00000124.

22. Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATED

The Stop 0xC000021A message occurs when Windows 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 cannot run without Winlogon or CSRSS, this is one of the few situations in which 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.

22.1. Interpreting the Message

This Stop message has three parameters:

22.2. Resolving the Problem

The following suggestions are specific to Stop 0x21A errors. For additional troubleshooting suggestions that apply to all Stop errors.

• Stop 0xC000021A messages occur in a user-mode process. The most common causes are third-party applications. If the error occurs after you install a new or updated device driver, system service, or third-party application, you need to remove, disable, or roll back the driver or uninstall the new software. Contact the software manufacturer about a possible update.

• A system file mismatch caused by partially restoring the system from backup media might cause this error. (Some backup programs do not restore files that they determine are in use.) Always use backup software that is Windows 7 compatible.

Note:

MORE INFO For more information about Stop 0xC000021A messages, see the Knowledge Base at http://support.microsoft.com/. Search using the keyword 0xC000021A.

23. Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

The Stop 0xC0000221 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.

23.1. Interpreting the Message

This Stop message typically displays the name of the damaged file as follows.

STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH <path>\<file name>
- or -
Unable to load device driver <driver_name>

23.2. Resolving the Problem

The following suggestions are specific to Stop 0xC0000221 errors. For additional troubleshooting suggestions that apply to all Stop errors.

• You can use Driver Rollback or System Restore from safe mode to restore a previous driver. You can also use Windows 7 recovery features, such as the Last Known Good Configuration startup option, Backup, or Automated System Recovery, to restore a previous working configuration. 

• If the Stop message names the specific file, try replacing it manually with a fresh copy from another Windows computer using safe mode or Startup Repair. 

• Stop message 0xC000026C, caused by similar conditions, provides the name of the system file. You can also use the preceding suggestions to resolve this error.

Note:

MORE INFO For more information about Stop 0xC0000221 messages, see the Knowledge Base at http://support.microsoft.com/. Search using the keyword 0xC0000221.