-->
![Windows Windows](/uploads/1/2/5/2/125290820/834571580.png)
Please enable JavaScript to view the comments powered by Disqus.
Driver_irql_not_less_or_equal The iaStorA.sys file is a software component related to Intel Rapid Storage Technology by Intel. It is a software solution supported by Intel Smart Response Technology.
The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory while the process IRQL that was too high.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
DRIVER_IRQL_NOT_LESS_OR_EQUAL parameters
Parameter | Description |
---|---|
1 | Memory referenced. |
2 | IRQL at time of reference. |
3 |
|
4 | Address that referenced memory. Use ln (list nearest symbols) on this address to see the name of the function. |
Cause
Typically, when this error occurs, a driver has tried to access an address that is pageable (or that is completely invalid) while the interrupt request level (IRQL) was too high. This can be caused by:
- Dereferencing a bad pointer (such as a NULL or freed pointer) while executing at or above DISPATCH_LEVEL.
- Accessing pageable data at or above DISPATCH_LEVEL.
- Executing pageable code at or above DISPATCH_LEVEL.
If a driver that is responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver. You can use dx (display debugger object model expression), a debugger command, to display this: dx KiBugCheckDriver.
This bug check is usually caused by drivers that have used improper memory addresses.
Possible causes for the page fault include the following events:
![Windows Windows](/uploads/1/2/5/2/125290820/834571580.png)
- The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
- The function call was made to a function in another driver, and that driver was unloaded.
- The function was called by using a function pointer that was an invalid pointer.
Resolution
If the problem is caused by the driver that you are developing, make sure that the function that was executing at the time of the bug check is (1) not marked as pageable or (2) does not call any other inline functions that could be paged out.
The !analyze debugger extension displays information about the bug check and can be helpful in determining the root cause. The following example is output from !analyze.
If a trap frame is available in the dump file, use the .trap command to set your context to the provided address.
To start debugging this type of bug check, examine the stack trace by using the k, kb, kc, kd, kp, kP, kv (display stack backtrace) commands.
In the debugger, run the !irql command to display information about the IRQL of a processor on the target computer before the debugger break. For example:
In the majority of cases of this type of bug check, the issue is not the IRQL level, but rather the memory that is being accessed.
Because this bug check is usually caused by drivers that have used improper memory addresses, use parameters 1, 3, and 4 to investigate further.
Use ln (list nearest symbols) with parameter 4 to see the name of the function that was called. Also examine the !analyze output to see if faulting code is identified.
Use !pool on the parameter 1 address to see whether it is paged pool. Use !address and the advanced !pte command to learn more about this area of memory.
Use the display memory commands to examine the memory referenced in command in parameter 1.
Use the u, ub, uu (unassemble) commands to look at the code in the address which referenced the memory in parameter 4.
Use the command
lm t n
to list modules that are loaded in the memory. Use !memusage and to examine the general state of the system memory.Driver Verifier
Driver Verifier is a tool that runs in real time to examine the behavior of drivers. For example, Driver Verifier checks the use of memory resources, such as memory pools. If it identifies errors in the execution of driver code, it proactively creates an exception to allow that part of the driver code to be further scrutinized. Driver Verifier Manager is built into Windows and is available on all Windows PCs.
To start Driver Verifier Manager, type verifier at a command prompt. You can configure which drivers to verify. The code that verifies drivers adds overhead as it runs, so try to verify the smallest number of drivers possible. For more information, see Driver Verifier.
Remarks
If you are not equipped to use the Windows debugger to work on this problem, you can use some basic troubleshooting techniques.
- Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing this bug check.
- If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
- Confirm that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about required hardware at Windows 10 Specifications.
For additional general troubleshooting information, see Blue screen data.
Sep. 18, 2018 / Updated by Bessie Shaw to Windows 10
DRIVER_IRQL_NOT_LESS_OR_EQUAL (error code 0x000000D1) is a stop error Windows users recently came around after the Windows 10 upgrade or the Windows 10 anniversary update. The error often comes with a Blue Screen of Death (BSoD), displaying error message 0x000000D1 as you can see in the picture below.
Some may also show you the driver file names, indicating the faulty drivers that cause the DRIVER_IRQL_NOT_LESS_OR_EQUAL error, like rtwlane.sys (Realtek PCIE Wireless LAN PCI-E NIC driver), igdkmd64.sys (Intel Graphics driver), athw8x.sys (Atheros Wireless LAN Driver), etc.
What Causes DRIVER_IRQL_NOT_LESS_OR_EQUAL (Error 0x000000D1)
Error 0x000000D1, or DRIVER_IRQL_NOT_LESS_OR_EQUAL, means the PC fails to identify the driver that has used improper address. There are several reasons for Windows 10 DRIVER_IRQL_NOT_LESS_OR_EQUAL error:
1. Corrupted, outdated or improperly configured drivers
2. Newly installed hardware or software that causes conflicts
3. Damaged hard disk
4. Corrupted system files
5. Malware or virus infection
6. Other reasons
In reality, the reasons above also result in many system issues, like 100% Disk Usage after Windows 10 Upgrade, ghost touch screen, slow boot problem, etc. So it is necessary to pay attention to each of them.
How to Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL (Error 0x000000D1) in Windows 10
Here we’ll show you how to troubleshoot Windows 10 DRIVER_IRQL_NOT_LESS_OR_EQUAL error with the solutions below:
Solution 1: Check the Hardware or Software
If you fail to enter Windows 10 after seeing the DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen, take a check on the hardware added or changed recently. For example, clean the accumulated dust out of the RAM slots.
If you are able to enter the Windows, try a Windows 10 clean boot to figure out the programs that cause the error 0x000000D1. Or remove the software you’ve installed recently, which may also result in the blue screen.
Solution 2: Perform a Malware and Virus Scan
Files or folders infected with malware or virus can also cause Windows 10 DRIVER_IRQL_NOT_LESS_OR_EQUAL error, so perform a scan and delete the infected files or folders on the PC.
Solution 3: Repair Corrupted Drivers that Causes DRIVER_IRQL_NOT_LESS_OR_EQUAL Error in Windows 10
After the basic check, it is extremely necessary to uninstall and reinstall the driver for Windows 10.
If the blue screen error does show you the .sys file name, find out that driver and reinstall it. But if the screen just shows you 0x000000D1 error only with “DRIVER_IRQL_NOT_LESS_OR_EQUAL”, it will be hard for you to diagnose the corrupted driver.
To diagnose and repair the broken driver, use Driver Talent recommended below, which is a professional driver troubleshooter. Click the button to get it directly.
Steps to repair driver issues with Driver Talent:
1. Click Scan to detect the problematic drivers.
2. Click Repair or Update to fix driver issues.
3. Restart the PC to make the newly installed drivers take effect.
Note: After the Windows 10 anniversary update, users cannot install a third-party driver manually. For more information, see Fix: Driver Signature Issue in Windows 10 Anniversary.
Solution 4: Use Command Prompt to Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL Error
In this method, you need to enter the System Recovery Options and use the Command Prompt to fix 0x000000D1 blue screen issue. Take the steps:
1. Use Windows shortcut keysWin + I to open Settings, and then select Update and recovery.
2. Select Recovery from the left column and then click the button Restart now from the right column.
3. Select Troubleshoot on reboot screen, then Advanced options, and then choose Command Prompt.
4. Log in with admin account and then type the command below and hit Enter.
DEL /F /S /Q /A 'C:WindowsSystem32drivers'
Note: The faulty driver name should be the one you see on the DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen, such as rtwlane.sys, igdkmd64.sys, usbuhci.sys, etc.
After the steps above, you will be able to enter Windows 10 normally. Don’t forget to update other drivers with Solution 3 when you finish this.
Solution 5: Use System File Checker
System File Checker is a tool in Windows 10 that can help to scan for corrupted system files and fix the DRIVER_IRQL_NOT_LESS_OR_EQUAL error. Here are the steps:
1. Use Windows shortcut keys Win + X to launch the Jump List, and then select Command Prompt (Admin).
2. Type SFC /scannow into the dialog box and press Enter.
3. If you receive “Windows Resource Protection found corrupt files but was unable to fix some of them”, do a system restore to completely fix the DRIVER_IRQL_NOT_LESS_OR_EQUAL error.
Also See:How to Use System Restore to Fix Windows 10 Issues
In fact, there are many Windows errors resulting in BSoD after the Windows OS upgrade or update. For more information, click
- How to Fix DPC_Watchdog_Violation Error in Windows 10
- Fix 0x0000003B System_Service_Exception in Windows 10
- Fix VIDEO_SCHEDULER_INTERNAL_ERROR in Windows 10
Hope the 5 methods above are helpful to resolve the DRIVER_IRQL_NOT_LESS_OR_EQUAL error in Windows 10 or the 0x000000D1 blue screen. If you have any questions on the subject of how to fix DRIVER_IRQL_NOT_LESS_OR_EQUAL in Windows 10, let us know by typing your questions in the comment section below.
Recommended Download
ExplorerMax | Driver Talent for Network Card |
Smart and advanced file explorer tool for Windows platforms | Download & Install Network Drivers without Internet Connection |
30-day Free Trial | Free Download |