How to fix the Driver IRQL_NOT_LESS_OR_EQUAL error in Windows

If your PC suddenly freezes and a blue screen appears with the message IRQL_NOT_LESS_OR_EQUAL o DRIVER_IRQL_NOT_LESS_OR_EQUALIt's normal to be scared: the computer restarts on its own, you lose what you were doing, and it seems like a serious hardware failure. The reality is that this type of BSOD (blue screen of death) is usually caused by drivers, memory, disk, or software conflicts And, in most cases, it can be made stable again without changing half the computer.

Throughout this article you will see, step by step, all the common causes of the IRQL_NOT_LESS_OR_EQUAL error in Windows 10 and Windows 11 and the most effective ways to solve itFrom updating the system and checking drivers, to checking RAM with the Memory Diagnostic Tool, running SFC and DISM, uninstalling problematic updates, checking hardware, or restoring the system to a previous point. We'll also see what to do if you've lost data due to unexpected restarts.

What does the IRQL_NOT_LESS_OR_LESS error mean and why does it appear?

When you see the message on the screen IRQL_NOT_LESS_OR_LESS or DRIVER_IRQL_NOT_LESS_OR_LESSWhat Windows is telling you is that a component (usually a driver or the kernel itself ntoskrnl.exeThe system has attempted to access a memory address it shouldn't have or one with an inappropriate priority level. This is considered a critical error, and the system protects itself by halting all operations and displaying a Blue Screen of Death (BSOD).

This stop code doesn't have a single cause; it's actually a symptom that something is wrong at a low level. Among the most frequent reasons that trigger it are... Blue screen IRQL_NOT_LESS_OR_EQUAL in Windows 10 and 11 are the following:

• Incompatible or incorrectly installed driversAfter adding new hardware or updating a driver, a conflict may occur with other drivers already present.
• Faulty or incorrectly configured RAMDamaged modules, strange memory mixes, or aggressive frequency and latency adjustments can cause random errors.
• Motherboard or memory controller failuresA faulty chipset or motherboard can cause problems that are difficult to diagnose.
• Corrupted system files: damage to Windows files, either due to sudden shutdowns, or due to malware or disk errors.
• Registration problems or failed installationsIncomplete installations or uninstallations leave behind residues that cause instability.
• Faulty Windows Updates: some system or driver updates may introduce a bug that only affects certain hardware.
• malware and virusesCertain malicious software modifies critical files or attaches itself to the kernel, triggering BSODs.
• Overheating or physical hardware failures: A very hot CPU, disks with bad sectors, or an unstable power supply may be the source of the problem.

To complicate matters further, sometimes the screenshot refers to ntoskrnl.exeThis does not mean that the kernel is broken, but rather that it is the component that "detects" the problem; the real culprit is usually a driver or a memory module that has misbehaved and forced the kernel to stop the system.

Update Windows and drivers first.

The first sensible step when the IRQL_NOT_LESS_OR_EQUAL error appears is Make sure Windows and drivers are fully updatedMicrosoft frequently corrects stability issues with new versions of the system, firmware, and drivers that it distributes. Windows Update.

To check if you have everything up to date in Windows 10 or 11, run these checks very simple:

1. Click on the Home and enters Configuration (cogwheel icon).
2. Access the section Update & Security > Windows Update.
3. Press on Search for updates and wait for the system to check for new packages.
4. If pending updates appear, download and install themThe equipment will restart if necessary.

Note that Windows doesn't always install all updates at once.Sometimes updates are released by region or hardware type to reduce risks. That's why it's important to manually click "Check for updates" and repeat the process until there are no more pending updates.

In parallel, it is advisable to update the Specific drivers from the manufacturer's websiteIdeally, you should download the drivers for your motherboard, chipset, graphics card, audio, network, and other devices directly from the official website of your motherboard or laptop manufacturer, since the Device administrator It often installs generic or older versions.

If you prefer to use Windows, you can update from Windows So:

• Right-click on the menu Home and choose Device administrator.
• Locate the device you are interested in (for example, the network adapter or the graphics card).
• Right click on it and select Update Driver.
• Let Windows search online for updated driver software.

If after having Windows and up-to-date drivers you are still experiencing screenshot IRQL_NOT_LESS_OR_EQUALIt's time to move on to more in-depth checks.

Check and repair system files (SFC and DISM)

A very common cause of this BSOD is that a Windows system file is corrupted or has been incorrectly modifiedBefore considering reinstalling everything, it is highly recommended to run the built-in SFC and DISM tools, which repair corrupted files and the system image.

To use them, you have to open a symbol of the system with elevated permissionsSince we're going to be working with critical components, do the following:

1. Press on Home, writes cmd in the search.
2. Right click on Symbol of the system and select Run as administrator.

First we will use the system file checker:

sfc /scannow

This command It analyzes all protected Windows files and replaces corrupted ones with correct copies.The process may take a while; let it finish 100% without closing the window.

When SFC is finished, it is also advisable to review the system image with DISM to make sure there are no underlying problems. In the same command prompt window with administrator privileges, run these three commands one after the other. commands:

dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /checkhealth
dism /online /cleanup-image /restorehealth

With them The system checks if the Windows image is damaged and, if so, repairs it by downloading the necessary components. from Windows Update. Depending on your computer's speed and your internet connection, this process may take several minutes.

Once SFC and DISM are complete, restart your computer and check if the IRQL_NOT_LESS_OR_EQUAL error persists. If the blue screen continues, it's quite likely that the root of the problem isn't the system files, but rather any third-party driver, update, or application.

Remove problematic Windows updates

There are times when the blue screen starts right after a specific Windows updateSince the operating system has to work with countless hardware combinations, it's not uncommon for some builds to cause conflicts with certain drivers or components.

If you suspect that the IRQL_NOT_LESS_OR_EQUAL error started right after an update, it's a good idea to... Uninstall the latest applied update and check if stability improves:

• Opens Configuration with the combination Win + I.
• Sign in Update & Security > Windows Update.
• Press on View update history.
• Click on Uninstall updates.
• Search, by date, the latest update installed, select it and click on uninstall.

After uninstalling it, restart your computer and use it for a while to see if the blue screens disappear. If they stop occurring, it's very likely that that specific update was the culprit, and you'll have to block it temporarily or wait for Microsoft to release a patch that fixes the bug.

Uninstall conflicting applications and use restore points

Another classic source of this BSOD is... third-party applications that attach themselves very deeply to the systemsuch as antivirus software, security tools, customization software, or resource-intensive programs like image and video editing suites. Often, the first blue screen appears right after installing one of these programs.

If you remember that the error started after installing a specific application, the plan is simple: Uninstall that software and check if the system returns to normal.. For it:

1. Go to Settings > Apps > Apps & features.
2. Sort the list by Instalation date to locate the last thing that was added.
3. Select the suspicious application and tap on uninstall.

If it's a complex program that modifies drivers or integrates low-level services, simply uninstalling it might not be enough. In those cases, it's very useful. restore the system to a previous point, created automatically just before installing the software.

To use System Restore, you need to have previously enabled this feature. If it was, do the following:

• Write Recover in Windows search and open the option Open restore Sistem.
• In the window that opens, click on System Restore.
• Check the box Show more restoration points to see all available dates.
• Select a restore point prior to the moment the screenshots began.
• Follow the wizard and let the computer restart and complete the process.

The system will revert to the state it was in on that date, keeping your personal documents but removing any registry changes, drivers, and software installed afterward. If the IRQL_NOT_LESS_OR_LESS error disappears when you revert to that point, you'll know that one of the subsequent changes was to blame.

Check your RAM using the Memory Diagnostic Tool

Memory is one of the first things to suspect when dealing with IRQL_NOT_LESS_OR_EQUAL, especially if the blue screen appears randomly or after upgrading the RAM. To rule out any issues, Windows includes a utility called Memory Diagnostic Tool which allows checking for errors in the modules.

To launch this tool on a computer running Windows 10 or 11, run the diagnostic following these steps:

1. On the PC with problems, Save your work and close all open applications..
2. Right-click on the menu Home and choose Run.
3. In the box that appears, write mjed and click on Accept.
4. The window will open Windows memory diagnostics. Select option Restart now and check for problems (recommended).

The computer will restart and, before entering Windows, the Memory Diagnostic Tool will automatically start. By default, it runs a set of standard tests which already detect many common faults, but if you want a more thorough check you can do this:

• When you see the blue diagnostic screen, press the key F1 to open the advanced options.
• In section Combination of testsUse the arrows to switch between Standard a Extended.
• Balance F10 to apply the changes and continue with the tests.

This extended battery is more exhaustive and can take considerably longer, but It is much more reliable for discovering problematic modules.When it finishes, the PC will restart on its own and return to the login screen.

Normally, when you log into Windows, a notification will appear next to the clock indicating if memory errors have been found. If You don't see the notification Or if you close it accidentally, you can always check the results in the Events viewer:

1. Right click on the button Home and select Events viewer.
2. In the left panel, navigate to Event Viewer (Local) > Application and Services Logs > Microsoft > Windows > MemoryDiagnostics-Results > Debug.
3. In the central part you will see one entry per memory test Done. Double-click on the one you're interested in to see the details.

If the diagnostics report errors, the IRQL_NOT_LESS_OR_EQUAL error is almost certainly caused by one or more RAM modules or the memory controller itself. In that case, you will need to... Try other modules, change slots, remove one of them, or manage the warranty. Check the motherboard if you suspect the socket is faulty.

Review hardware, RAM, and configuration changes

BSOD problems often occur after hardware changes: adding RAM, switching from a single module to dual channelInstall a new graphics card, change the motherboard or CPU, etc. If IRQL_NOT_LESS_OR_EQUAL matches There with some of these modifications, Check the compatibility carefully..

In the specific case of memory, it is relatively common that, when moving from a single module to two, the integrated memory controller (IMC) It gets a little fussy: the team can emit beeps when starting, restarting on its own and then eventually booting into Windows, or displaying blue screens in the first few minutes of use.

If something like this happens to you, Try these ideas:

• Connect the PC to the power outlet, Turn it off completely and unplug the power cord from the source.
• Wait about 10-15 minutes for the capacitors to discharge.
• Reconnect and start again.
• If the problems continue, Try testing the RAM modules one by one and in different slots. of the board to locate unstable combinations.

It is also important to verify that the The installed RAM is compatible with your motherboard and processor.Very old memory modules combined with modern chipsets, or vice versa, can cause subtle errors. Check the motherboard manufacturer's Quality Value List (QVL).

Beyond RAM, any new hardware (PCIe cards, NVMe drives, etc.) could be the cause. A good test involves... Disconnect all non-essential peripherals (printers, external hard drives, USB drives, etc.) and leave the computer with the bare minimum: motherboard, CPU, one RAM module, system drive, and graphics card. If it stabilizes after this, you can reconnect the components one by one until you find the culprit.

Analyze disk and repair logical errors

If the file system is damaged or there are bad sectors on the disk, this can eventually manifest as blue screens IRQL_NOT_LESS_OR_EQUAL or other similar codesWindows includes a utility to check the disk and repair logical errors: CHKDSK.

To run CHKDSK safely, Do the following:

1. Balance Win + X and choose Bus Terminal Windows (administrator) o Command Prompt (Administrator).
2. In the window that opens, type the following command:

chkdsk C: /f

If your system partition is not on C:, change the letter to the correct one. The parameter /f indicates that they should repair the detected logical errorsIf you also want to have bad sectors on the disk checked and marked, you can use /r instead or combined:

chkdsk C: /f /r

If you're checking the system drive, Windows will tell you it can't lock it and ask if you want to. schedule the check for the next restartAccept, restart your computer, and let the analysis complete, even if it takes a while.

When CHKDSK finishes its job and the system Boot Again, try using your PC normally to see if The cuts and screenshots have disappearedIf it continues to fail, further debugging of drivers and software will be necessary.

Run the Hardware Troubleshooter and Driver Verifier

In addition to the tools we've already seen, Windows has a hardware and device-specific troubleshooter which can help you detect basic component failures.

To launch it, Open the solver and follow the instructions on the screen.

1. Opens Configuration from the Start menu.
2. Go to Update and security > Troubleshoot.
3. In the right panel, locate Hardware and Devices.
4. Click on Run the troubleshooter and follow the instructions on the screen.

If the assistant finds something unusual, it will show it to you at the end, and in many cases, you will be able to apply an automatic correctionIf it doesn't detect anything, that doesn't rule out a hardware problem, but at least you'll have eliminated the most obvious causes.

For more stubborn cases, there is an advanced utility called DriverVerifier It's used to stress-test Windows drivers and detect which ones are causing instability. It's a powerful tool that can even cause more blue screens during testingTherefore, it is only recommended for users with some experience.

If you still want to use it, do so with caution:

• Open a Command Prompt as administrator.
• Write verifier and press Enter.
• Choose Create standard settings and click on Next.
• Choose which drivers you want to check (for example, all third-party drivers) and click on Finish.
• Restart your computer and use the system normally until the next BSOD occurs.

When the system crashes, the information of memory dump will be more precise to identify which driver has failed. However, don't leave Driver Verifier running permanently; once you've gathered data, run it again. verifier and disables the checks.

Disable third-party antivirus software and use Microsoft Defender

Third-party antivirus programs and security suites are another source of many headaches when it comes to blue screens of death. Because they work very close to the kernel, Any bug in your driver can trigger an IRQL_NOT_LESS_OR_EQUAL error..

Microsoft recommends, in its own support documentation, that in the event of this type of error, you should try to completely uninstall third-party antivirus software and be left alone with Microsoft Defenderwhich comes integrated into Windows 10 and 11 and offers a level of protection that is more than sufficient for most users.

It's important to understand that having two antivirus programs running in parallel doesn't add security; on the contrary, They fight over analyzing the same files and connectionsThey increase CPU and memory usage and multiply the chances of driver conflicts. The wisest course of action is to leave only one active.

If the problem disappears after uninstalling your external antivirus and letting Microsoft Defender handle the protection, then it's pretty clear that The origin of the BSOD was in that softwareIn that case, you can consider changing solutions or sticking with Microsoft's, which is very well integrated and consumes few resources.

Start in safe mode to narrow down the problem

A very useful trick to differentiate whether the fault is hardware or software is to boot the system in Safe ModeIn this mode, Windows only loads the controllers and basic servicesIf the PC is running smoothly in this situation, the problem is most likely with a driver or additional application.

To Enter safe mode On Windows 10/11, do the following:

1. On the login screen or in the power menu, press and hold the key Shift and, without letting go, click on Restart.
2. When the blue options screen appears, choose Solve problems.
3. On the next screen, enter Advanced.
4. Choose Startup configuration and click on Restart.
5. Upon restarting, you will see a list of numbered options: press the number corresponding to Enable safe mode.

If you don't get crashes in safe mode, browsers stop freezing, and applications that previously failed (like Discord in some reported cases) function normallyThis is a very clear symptom that the hardware itself is fine and the cause lies in drivers or third-party programs that are only loaded during normal startup.

Reset your PC or perform a clean installation of Windows

If you've gotten this far, tried updates, diagnostics, uninstalls, and hardware checks, and the IRQL_NOT_LESS_OR_EQUAL error persists, you may need to take a more drastic step: reset your computer or perform a clean installation of Windows.

The most convenient option within the system itself is to use the function Reset this PCwhich allows you to restore Windows to its freshly installed state, choosing whether or not to keep your personal files:

• Sign in Settings > Update & security > Recovery.
• In section Reset this PC, click on Contac us.
• Choose between keep my files (deletes programs but keeps documents) or Remove all (leaves the disk clean).
• Follow the instructions until the process is complete.

This reset may take a while; let it work without interrupting it. In many cases, this is sufficient for Remove corrupt drivers and programs that cannot be located.However, you will have to manually reinstall your applications afterwards.

If even a reset doesn't solve the problem, the cleanest option is forma tear the system partition and install Windows from scratch booting from an official installation USB drive. Before doing so, make sure you have a backup of all your important data and essential drivers for your motherboard, graphics card, and network.

Protect your data and recover it if you have already suffered losses.

Blue screens have a particularly annoying consequence: when the computer suddenly restarts, You lose any work you haven't saved. And in extreme cases, even entire files or partitions can become corrupted. That's why it's vital to get used to doing regular system and data backups.

In Windows you can use both the native tools (File History, Backup and Restore) and third-party solutions geared towards backup These programs allow you to schedule automatic backups of the entire system, specific disks, or key folders. Some also make it easy to create bootable media to restore a PC that won't start.

If you have already experienced the IRQL_NOT_LESS_OR_EQUAL error and have lost important documents, there is a possibility that recover some of that data with recovery programs specialized utilities scan the disk for remnants of deleted or unsaved files and, with some luck, allow you to restore them as long as the space hasn't been overwritten.

Ideally immediately stop using the affected unit To avoid overwriting sectors, launch the recovery tool on the problematic disk from another system or by booting from an external drive. The sooner you act after the loss, the better your chances of recovering something.

As you can see, although the IRQL_NOT_LESS_OR_LESS message is frightening and sometimes forces you to wrestle with drivers, memory, updates, and even reinstalls, with a combination of Diagnostic methods (SFC, DISM, Memory, CHKDSK), hardware checks, updated drivers, cleaning up conflicting software, and good backups It is possible to stabilize the system again and minimize the impact of these blue screens on your daily life.