Stop 0xA or IRQL_NOT_LESS_OR_EQUAL
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 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 the result of faulty or incompatible hardware or software.
Interpreting the Message
This Stop message has four parameters:
- Memory address that was improperly referenced
- IRQL that was required to access the memory
- Type of access (0x00 = read operation, 0x01 = write operation)
- Address of the instruction that attempted to reference memory specified in parameter 1
If the last parameter is within the address range of a device driver used on your system, you can determine which device driver was running when the memory access occurred. You can typically determine the driver name by reading the line that begins with
**Address 0xZZZZZZZZ has base at <address>- <driver name>
If the third parameter is the same as the first parameter, a special condition exists in which a system worker routine-carried out by a worker thread to handle background tasks known as work items-returned at a higher IRQL. In that case, some of the four parameters take on new meanings:
- Address of the worker routine
- Kernel IRQL
- Address of the worker routine
- Address of the work item
Resolving the Problem
The following suggestions are specific to Stop 0xA errors. For additional troubleshooting suggestions that apply to all Stop errors, see the section titled "Stop Message Checklist" later in this tutorial.
- To resolve an error caused by a faulty device driver, system service, or basic
input/output system (BIOS), follow these steps:
- Restart your computer.
- Press F8 at the character-based menu that displays the operating system choices.
- Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.
- To resolve an error caused by an incompatible device driver, system service, virus
scanner, or backup tool, follow these steps:
- Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
- Try disabling memory caching of the BIOS.
- Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
- Make sure the latest Service Pack is installed.
- If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
- For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.
- If you encounter a Stop 0xA message while upgrading to Windows 7, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows, contact the hardware manufacturer to obtain compatible updates.
- If the Stop error occurs when resuming from hibernation or suspend, read Knowledge Base articles 941492 at http://support.microsoft.com/kb/941492 and 945577 at http://support.microsoft.com/kb/945577.
- If the Stop error occurs when starting a mobile computer that has the lid closed, refer to Knowledge Base article 941507 at http://support.microsoft.com/kb/941507.
In this tutorial:
- Troubleshooting Stop Messages
- Stop Message Overview
- Identifying the Stop Error
- Finding Troubleshooting Information
- Stop Messages
- Bugcheck Information
- Technical Information
- Debug Port and Dump Status Information
- Types of Stop Errors
- Memory Dump Files
- Configuring Small Memory Dump Files
- Configuring Kernel Memory Dump Files
- Configuring Complete Memory Dump Files
- How to Manually Initiate a Stop Error and Create a Dump File
- Using Memory Dump Files to Analyze Stop Errors
- Using Windows 7 Error Reporting
- Using Symbol Files and Debuggers
- Being Prepared for Stop Errors
- Record and Save Stop Message Information
- Check Software Disk Space Requirements
- Install a Kernel Debugger and Symbol Files
- Stop 0xA or IRQL_NOT_LESS_OR_EQUAL
- Stop 0x1E or KMODE_EXCEPTION_NOT_HANDLED
- Understanding Kernel Stack Overflows
- Stop 0x24 or NTFS_FILE_SYSTEM
- Stop 0x2E or DATA_BUS_ERROR
- Stop 0x3B or SYSTEM_SERVICE_EXCEPTION
- Stop 0x3F or NO_MORE_SYSTEM_PTES
- Stop 0x50 or PA GE_FAULT_IN_NONPA GED_AREA
- Stop 0x77 or KERNEL_STACK_INPA GE_ERROR
- Stop 0x7A or KERNEL_DATA_INPA GE_ERROR
- Stop 0x7B or INACCESSIBLE_BOOT_DEVICE
- Stop 0x7F or UNEXPECTED_KERNEL_MODE_TRAP
- Stop 0x9F or DRIVER_POWER_STATE_FAILURE
- Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY
- Stop 0xC2 or BAD_POOL_CALLER
- Stop 0xCE or DRIVER_UNLOADED_WITHOUT_CANCELLING_ PENDING_OPERATIONS
- Stop 0xD1 or IRQL_NOT_LESS_OR_EQUAL
- Stop 0xD8 or DRIVER_USED_EXCESSIVE_PTES
- Stop 0xEA or THREAD_STUCK_IN_DEVICE_DRIVER
- Stop 0xED or UNMOUNTABLE_BOOT_VOLUME
- Stop 0xFE or BUGCODE_USB_DRIVER
- Stop 0x00000124
- Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATED
- Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
- Hardware Malfunction Messages
- Stop Message Checklist
- Check Your Software
- Use the Last Known Good Configuration
- Restart the System in Safe Mode
- Check Event Viewer Logs
- Install Compatible Antivirus Tools
- Report Your Errors
- Install Operating System and Driver Updates
- Install and Use a Kernel Debugger
- Check Your Hardware
- Check for Nondefault Firmware Settings
- Check for Non-Default Hardware Clock Speeds
- Check by Running Hardware Diagnostic Tools
- Check for SCSI Disk and Controller Settings
- Check Memory Compatibility
- Check by Temporarily Removing Devices
- Check by Replacing a Device