IRQL_NOT_LESS_OR_EQUAL Windows 11: Complete Fix Guide (BSOD Stop Code)

Understanding the IRQL_NOT_LESS_OR_EQUAL Error on Windows 11

When Windows 11 displays a blue screen with the stop code IRQL_NOT_LESS_OR_EQUAL (or its driver-specific variant DRIVER_IRQL_NOT_LESS_OR_EQUAL), the kernel has detected that a driver or system component tried to access a memory address at an interrupt request level (IRQL) that is too high. In plain terms: a piece of code reached into memory it should not touch at that moment, and Windows killed the session to prevent data corruption.

The exact message you see on the crash screen will be one of:

• STOP CODE: IRQL_NOT_LESS_OR_EQUAL
• STOP CODE: DRIVER_IRQL_NOT_LESS_OR_EQUAL (with an offending file listed below)
• What failed: tcpip.sys — network stack driver
• What failed: ntoskrnl.exe — Windows kernel itself (often points to RAM or a kernel-mode driver bug)
• What failed: nvlddmkm.sys — NVIDIA display driver
• What failed: dxgkrnl.sys — DirectX kernel

Common root causes include:

1. Outdated, corrupted, or incompatible device drivers — most frequent cause on Windows 11
2. Faulty or incompatible RAM — especially after hardware changes
3. Corrupted Windows system files — often after failed updates
4. Overclocking or aggressive XMP/EXPO memory profiles
5. Conflicting third-party security or antivirus software

Step 1: Read the Crash Screen and Dump File

Before touching anything, capture the exact stop code and failing module. If the PC reboots too fast:

1. Go to Settings → System → About → Advanced System Settings → Startup and Recovery → Settings.
2. Uncheck Automatically restart under System failure.
3. Set Write debugging information to Small memory dump (256 KB).

Dump files land in C:\Windows\Minidump\. Use WhoCrashed (free tool) or WinDbg to read them.

In WinDbg (open as Administrator, File → Open Crash Dump):

!analyze -v

Look for the MODULE_NAME and IMAGE_NAME fields — these identify the faulting driver.

Step 2: Boot into Safe Mode (if PC won't stay up)

If Windows 11 keeps crashing on boot:

1. Force-power-off the PC 3 times in a row. Windows will enter Automatic Repair mode.
2. Choose Advanced options → Startup Settings → Restart.
3. Press 4 (Safe Mode) or 5 (Safe Mode with Networking).

All subsequent steps can be run from Safe Mode.

Step 3: Update or Roll Back the Offending Driver

If a driver filename was shown on the BSOD:

• tcpip.sys → Update your network adapter driver. Open Device Manager (devmgmt.msc), expand Network Adapters, right-click your adapter → Update driver. Also check for Windows Update (tcpip.sys is part of the OS — a cumulative update often fixes it).
• nvlddmkm.sys / atikmdag.sys → Uninstall your GPU driver fully using DDU (Display Driver Uninstaller) in Safe Mode, then reinstall the latest stable version from NVIDIA/AMD.
• ntoskrnl.exe → Skip to Step 5 (RAM check) and Step 6 (SFC/DISM), as the kernel image itself rarely corrupts independently.

To roll back a driver:

1. Open Device Manager.
2. Right-click the device → Properties → Driver tab → Roll Back Driver.
3. Restart and monitor.

Step 4: Run SFC and DISM to Repair System Files

Corrupted Windows files — especially after a botched update — can cause the kernel (ntoskrnl.exe) to fault at the wrong IRQL. Open an elevated Command Prompt or PowerShell:

# Step 1: Repair the Windows component store
DISM /Online /Cleanup-Image /RestoreHealth

# Step 2: Scan and repair protected system files
sfc /scannow

Both commands require Administrator privileges. After completion, restart and check Event Viewer (eventvwr.msc) → Windows Logs → System for critical errors.

Step 5: Test Your RAM

Faulty RAM is a silent killer for IRQL errors. Run the built-in Windows Memory Diagnostic:

1. Press Win + R, type mdsched.exe, press Enter.
2. Choose Restart now and check for problems.
3. Let it complete (one pass ≈ 15-30 minutes).

For deeper testing, use MemTest86 (bootable USB, runs outside Windows). Run at least 2 full passes. Any errors = RAM is faulty. Try reseating the sticks first; if errors persist, replace the failing module.

If you have an XMP or EXPO profile enabled in BIOS (common on DDR5 systems paired with Windows 11), try disabling it to run RAM at its default JEDEC speed. This alone resolves the BSOD for many users.

Step 6: Uninstall Problematic Windows Updates

If the BSOD started right after a Windows Update:

1. Go to Settings → Windows Update → Update History → Uninstall Updates.
2. Sort by date and remove the most recent cumulative or driver update.
3. After uninstalling, go to Windows Update → Advanced Options → Pause Updates temporarily.

Alternatively, use DISM from an elevated prompt:

# List recently installed packages
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

# Remove a specific update (replace KB number)
wusa /uninstall /kb:5034765 /quiet /norestart

Step 7: Perform a Clean Boot

Third-party software — VPNs, antivirus, gaming overlays, virtual audio drivers — can inject kernel-mode code that triggers IRQL violations.

1. Press Win + R, type msconfig, press Enter.
2. Under Services tab, check Hide all Microsoft services, then click Disable all.
3. Under Startup tab, open Task Manager and disable all startup items.
4. Restart. If the BSOD stops, re-enable services in small batches to isolate the culprit.

Common offenders on Windows 11: Malwarebytes real-time protection, older versions of Norton/McAfee, Killer Network software, Nahimic audio service, MSI Afterburner/RivaTuner.

Step 8: Check for Hardware Issues

If all software fixes fail:

• Reseat GPU, RAM sticks, and storage cables — poor contact causes intermittent faults.
• Run SMART diagnostics on your SSD/HDD: wmic diskdrive get status or use CrystalDiskInfo.
• Check CPU temperatures under load (HWiNFO64). Overheating causes erratic memory access patterns.
• Test with one RAM stick at a time if you have dual-channel setup.

Step 9: Last Resort — Reset Windows 11

If BSOD persists even in Safe Mode and you've exhausted all other options:

1. Go to Settings → System → Recovery → Reset this PC.
2. Choose Keep my files (safer) or Remove everything.
3. Select Cloud download for a clean OS image.

Always back up your data before resetting.