IRQL_NOT_LESS_OR_EQUAL BSOD Fix for Windows 11 Guide
For an irql_not_less_or_equal bsod fix on Windows 11, first split the cause within 15 minutes: if it started after a driver, update, USB device, or RAM change, roll that back first; if not, check dump files, Driver Verifier, Memory Diagnostic, and system file repair. I have seen guesswork here trigger reboot loops, damage open files, and send people chasing parts that were never bad. This guide lays out a fast triage path for desktop access, Safe Mode recovery, and proof checks for driver faults, bad RAM, system corruption, and hardware conflicts.
Start here: the 15-minute triage for IRQL_NOT_LESS_OR_EQUAL
What the stop code means in Windows 11
IRQL_NOT_LESS_OR_EQUAL is a Windows blue screen stop error, commonly shown as stop code 0xA. Microsoft identifies the error as 0xA on Windows 11 and Windows 10. Microsoft also says it usually happens when a device driver or system memory tries to read or write an invalid memory address. (Microsoft Support)
That plain-English cause matters because it shrinks the first set of tests. In practice, this blue screen usually comes from a bad driver, faulty or unstable RAM, file corruption, or a low-level hardware conflict. Tom’s Hardware also describes it as a memory-related access violation by a process or driver, and notes that Windows collects forensic data during the blue screen.
What changed right before the first crash
Start with timing, then change history. If the first crash followed new RAM, a GPU swap, an SSD install, a USB dock, antivirus, an RGB tool, a motherboard utility, a driver updater, or a fresh Windows update, reverse that first.
This order beats working through a flat fix list. New PCs and fresh upgrades point more often to RAM, BIOS settings, or device conflicts. Older stable installs that suddenly start crashing point more often to a driver, update, or utility that changed last.
What to do first if Windows reboots too fast or will not reach the desktop
If the system flashes blue and restarts before you can read the code, force entry into recovery by interrupting boot several times, then use Troubleshoot > Advanced options > Startup Settings > Restart and choose Safe Mode or Safe Mode with Networking.
Safe Mode loads a stripped-down driver set. If the machine stays stable there, I would move third-party drivers, startup apps, security suites, VPN clients, RGB utilities, motherboard control apps, or similar background software to the top of the list.
According to IRQL_NOT_LESS_OR_EQUAL Stop Code in Windows 11/ … — DiskGenius says the guide covers Windows 11, 10, 8, and 7. (source)
What does IRQL_NOT_LESS_OR_EQUAL usually point to?
IRQL_NOT_LESS_OR_EQUAL usually points to one of three buckets: a driver touched memory it should not, system RAM is faulty or unstable, or Windows files or hardware-level settings are damaged enough to trigger invalid memory access. On Windows 11, crash timing is the fastest way to sort those buckets.
Driver access to invalid memory
Microsoft says the error usually occurs when a device driver or system memory accesses invalid memory. NeoSmart also lists incompatible device drivers as a cause, and says the error can follow a newly upgraded faulty device driver.
That makes recent driver changes the first thing to inspect. Start with GPU, chipset, storage, network, USB, and security drivers before touching everything else.
Faulty or unstable RAM
Bad or unstable RAM is one of the most common triggers for this stop code. I see it more on new builds, right after a memory upgrade, with unstable XMP or EXPO settings, under heavy load, and during file copy jobs that hit memory paths and storage at the same time.
If the machine also throws random bugchecks with different stop codes, RAM climbs the suspect list fast. If crashes are tied tightly to one device action, a driver usually moves ahead.
System file corruption and low-level hardware conflicts
NeoSmart lists corrupt system files and incompatible hardware devices as causes. Storage driver issues, broken Windows files, BIOS instability, docks, expansion cards, and flaky USB devices can all end in the same stop code even though the root issue sits below the app level.
Decision matrix: crash pattern to next action
Use this matrix before trying broad fixes
| Crash pattern | First test | Likely culprit | Next action |
|---|---|---|---|
| During boot | Boot into Safe Mode and see if the blue screens stop there | New driver, startup service, security tool, or recent hardware change | Roll back the last driver or uninstall the last app/device added; then clean boot |
| Idle desktop or soon after sign-in | Open Reliability Monitor and Event Viewer to match the first crash with a recent install or update | Background utility, VPN client, RGB app, motherboard tool, antivirus, or network driver | Disable startup apps, remove the matching utility, then reinstall or roll back its driver |
| During Windows Update | Check update history, optional driver updates, and the exact date the blue screens began | Bad driver pushed by update or corrupted system files | Uninstall the recent quality update or roll back the device driver tied to the timeline; then run DISM and SFC |
| During file copy | Run Windows Memory Diagnostic, then test RAM one stick at a time if needed | Faulty RAM, unstable memory settings, storage driver issue, or bad external device | Check Event Viewer for memory results, remove extra RAM sticks, and disconnect external storage or docks |
| Under heavy load | Return BIOS or UEFI memory settings to stock and watch for repeat crashes | Unstable RAM, overheating-adjacent instability, GPU driver, chipset driver, PSU or motherboard issue | Disable memory overclock settings, update BIOS if needed, and test with minimum hardware attached |
How to use the result
Pick one branch and follow it before moving on. If a crash matches file copy and heavy load, treat RAM and firmware settings as higher priority than cosmetic utilities. If it matches idle desktop after sign-in, move startup software and network drivers to the front.
How do I tell if this is a driver problem in Windows 11?
A driver problem becomes likely when crashes started after an update, device install, or utility install, and when Safe Mode is stable. On Windows 11, the quickest proof path is Reliability Monitor, Event Viewer, Device Manager, and minidump timing, then a targeted rollback or reinstall instead of blind driver updates.
Check Reliability Monitor, Event Viewer, and the update timeline
Open Control Panel > Security and Maintenance > Reliability Monitor and look at the first red failure on the day the BSOD began. Then open Event Viewer > Windows Logs > System and compare driver installs, update events, and shutdown errors around the same time.
This is where many generic guides stop too early. The goal is to find what changed right before the first crash, not stare at a long error list.
Use Device Manager, optional updates, and vendor downloads
In Windows 11, check Settings > Windows Update > Advanced options > Optional updates for driver updates. Then check Device Manager for a rollback option on the device tied to the crash timeline.
If Windows Update offered a driver right before the BSOD, rolling back can be smarter than chasing a newer build. For chipset, storage, network, and GPU drivers, the PC or component maker site may carry a newer or more stable package than Windows Update.
Read minidump clues without guessing
Windows often writes dump files to C:\Windows\Minidump. If the system stays up long enough, review recent dump timestamps and compare them with update and install history. A repeated driver file name, repeated device family, or repeated crash timing can narrow the suspect fast. (dell.com)
Minidumps work best as clues. If the same network, storage, USB, or GPU driver shows up more than once and the crashes match that device activity, act on that signal first.
Is IRQL_NOT_LESS_OR_EQUAL a RAM problem or a driver problem?
It can be either, but the pattern usually separates them. Repeat crashes during file copy, under heavy load, on a new build, or after enabling memory tuning lean toward RAM. Crashes after sign-in, after updates, or after app and device installs lean toward drivers or software conflicts.
Run Windows Memory Diagnostic with mdsched
Microsoft recommends checking Windows memory with the Windows Memory Diagnostic Tool. Microsoft instructs users to enter mdsched in Run to open memory diagnostics.
- Press Windows + R.
- Type mdsched and press Enter.
- Choose Restart now and check for problems.
- Let the test complete.
Microsoft says the diagnostic can run in Standard or Extended mode. Standard is the fast first pass. If the machine still crashes and RAM still looks suspicious, rerun it in Extended mode.
Find the result in Event Viewer and decide what it means
After Windows restarts, check Event Viewer > Windows Logs > System and look for the memory diagnostics result. Microsoft notes Event ID 2001 means no memory errors were detected.
No detected errors do not fully clear RAM. If the machine only crashes with both sticks installed, only under load, or only with memory tuning enabled, keep going with one-stick testing and stock memory settings.
Test RAM one stick at a time and check BIOS or UEFI memory settings
If you recently added RAM, remove the new kit first. If there are multiple sticks, test one stick at a time and rotate slots if needed.
Also check BIOS or UEFI for memory settings. Return XMP or EXPO, manual timings, and memory voltage changes to stock while diagnosing. Older guidance mentions disabling memory caching or shadowing, but on modern Windows 11 systems that is rare and secondary.
What should I do if the crashes started after an update, install, or new device?
If IRQL_NOT_LESS_OR_EQUAL began right after a Windows update, driver install, app install, or new peripheral, reverse that change before doing deep repair work. This is the fastest branch because a fresh change gives you a clear suspect, and reversing one suspect is cleaner than changing ten settings.
Reverse recent Windows updates, drivers, and app installs
For a Windows update path, open Settings > Windows Update > Update history > Uninstall updates and remove the recent quality update if the timeline fits. For a driver path, use Device Manager, open the device properties, and choose Roll Back Driver if available. (Microsoft Support)
If the crash started after a utility install, uninstall that app first. Security suites, VPN clients, RGB tools, motherboard control apps, and driver helper software are frequent conflict sources because they run deep in the system.
Remove new peripherals, docks, USB devices, and expansion hardware
NeoSmart lists incompatible hardware devices as a cause. Disconnect USB hubs, docks, printers, capture devices, external drives, and new PCIe cards. Then boot with only the keyboard, mouse, display, and the system drive connected.
On a new build, strip it down before changing half the software stack. On an older stable PC, unplug the device added closest to the first crash date.
Watch for software that commonly conflicts
If crashes happen at idle desktop or shortly after sign-in, look hard at software that hooks into drivers or startup services. The usual suspects are third-party antivirus, RGB suites, fan-control packages, motherboard utilities, VPN clients, and driver updater tools.
How do I repair Windows files and isolate startup conflicts?
Use Safe Mode when normal boot fails, then run DISM and SFC from an elevated terminal, and finish with a clean boot. This sequence helps separate damaged Windows files from third-party startup conflicts, especially when the system restarts too fast to stay usable on the desktop.
Boot into Safe Mode when normal startup fails
From recovery, choose Troubleshoot > Advanced options > Startup Settings > Restart, then select Safe Mode. If networking is needed for driver downloads, choose Safe Mode with Networking.
If the blue screen disappears in Safe Mode, that result matters. It does not prove Windows files are healthy, but it does move third-party services and drivers much higher on the list.
Run DISM and SFC from an elevated Command Prompt or PowerShell
Open Windows Terminal (Admin) or Command Prompt (Admin), then run:
DISM /Online /Cleanup-Image /RestoreHealthsfc /scannow
DISM checks and repairs the Windows image. SFC follows by checking protected system files. This branch matters more when the BSOD started during Windows Update, after a failed update, or after storage-related trouble.
Use a clean boot to isolate third-party services and startup apps
Open System Configuration, hide Microsoft services, disable the remaining non-Microsoft services, then disable startup apps in Task Manager. Restart and test.
If the crash stops, re-enable items in small groups until the BSOD returns. That narrows the offending utility far faster than updating every driver in sight.
When should I suspect BIOS, firmware, or failing hardware?
Suspect BIOS, firmware, or failing hardware when crashes continue after driver rollback, Safe Mode checks, clean boot, DISM, SFC, and Windows Memory Diagnostic, or when the pattern is strongest under load, during file copy, or on a new build. At that point, software-only fixes stop being the best use of time.
Firmware and BIOS checks that matter on Windows 11 PCs
Enter BIOS or UEFI during boot using the board or laptop maker’s firmware key. Check whether memory settings are running at stock values, whether the BIOS is current, and whether storage mode or PCIe-related settings changed recently.
Firmware updates can help when a new CPU, RAM kit, SSD, or GPU introduced instability. Apply them carefully and only from the system or board maker’s instructions.
Signs of storage, motherboard, PSU, or CPU instability
If the stop code appears during large file transfers, with random corruption, or with several different bugchecks, storage and motherboard paths need attention. If it appears only under heavy GPU or CPU load, power delivery, board stability, or cooling-related instability move higher on the list.
New PCs deserve a different triage order than long-stable ones. On a new build, stock BIOS settings and minimum hardware are the right base. On an older machine, start with the last software or driver change unless clear hardware symptoms are present.
The stop-here rule: when to escalate after clean boot and RAM testing
Stop here and escalate if crashes continue after clean boot, minidump review, driver rollback or reinstall, Windows Memory Diagnostic, one-stick RAM testing, and reversing recent hardware changes. At that point, move to deeper hardware diagnostics or professional repair.
That is the line where more random tweaking usually creates more confusion. DiskGenius lists 16 step-by-step methods for fixing the stop code, but if the core branches above have all failed, the better next move is targeted board, RAM, storage, or power testing.
Frequently asked questions
How do I fix IRQL_NOT_LESS_OR_EQUAL BSOD in Windows 11?
Start with crash timing and recent changes. Reverse the last driver, update, USB device, or RAM change first, then check Reliability Monitor, Event Viewer, and minidumps. If the pattern points to memory, run mdsched. If Windows is unstable, use Safe Mode, then run DISM, SFC, and a clean boot.
What causes IRQL_NOT_LESS_OR_EQUAL stop code?
Microsoft says this stop code, also identified as 0xA, usually occurs when a device driver or system memory accesses invalid memory. Common causes include incompatible drivers, faulty RAM, corrupt system files, unstable BIOS memory settings, and hardware conflicts from newly added devices or peripherals.
Is IRQL_NOT_LESS_OR_EQUAL a RAM problem or a driver problem?
Either is possible, so the symptom pattern matters. File copy crashes, new-build instability, and load-related failures push RAM and firmware higher. Crashes after sign-in, after Windows Update, or after a utility install push drivers and startup software higher. Use memory testing and clean boot results to separate them.
How do I check which driver is causing the BSOD?
Check the first crash date in Reliability Monitor, compare it with update and install history, then review Event Viewer and recent files in C:\Windows\Minidump. If the same device family or driver appears around each crash, roll back, reinstall, or replace that driver before changing unrelated components.
What should I do if IRQL_NOT_LESS_OR_EQUAL happens after a Windows update?
Open Settings > Windows Update > Update history and match the first blue screen with the update date. If the timing fits, uninstall the recent quality update or roll back the driver that changed with it. Then run DISM and SFC, and review optional driver updates with caution.
How do I run Windows Memory Diagnostic for this BSOD?
Press Windows + R, type mdsched, and choose Restart now and check for problems. Microsoft says the tool can run in Standard or Extended mode. After the reboot, check Event Viewer > System for the result; Event ID 2001 means no memory errors were detected.
