Why does my Dell laptop keep getting DRIVER_IRQL_NOT_LESS_OR_EQUAL after a Windows Update?

Windows Updates sometimes push driver updates that are not fully compatible with your specific Dell hardware configuration. The update may install a generic Intel, NVIDIA, or Killer network driver that conflicts with Dell's customized firmware. To fix this, open Device Manager, locate the recently updated driver (check 'Driver Date' in Properties), and use 'Roll Back Driver'. You can also pause Windows Updates temporarily via Settings → Windows Update → Advanced Options → Pause Updates, then manually install the correct driver from Dell's support site.

How do I find which driver caused the IRQL_NOT_LESS_OR_EQUAL BSOD on my Dell?

The most reliable method is to analyze the minidump file at C:\Windows\Minidump\. Use the free tool WhoCrashed (resplendence.com) for an easy summary, or use WinDbg with the command '!analyze -v' for detailed output. The 'IMAGE_NAME' field in WinDbg output will show the exact driver filename (e.g., Netwtw08.sys, nvlddmkm.sys, or tcpip.sys). If no minidump exists, configure Small Memory Dump in System Properties first.

Can bad RAM cause DRIVER_IRQL_NOT_LESS_OR_EQUAL on a Dell PC?

Yes. Faulty or incompatible RAM sticks can corrupt the memory addresses that drivers attempt to access, causing the kernel to throw a 0x000000D1 stop code even when the driver itself is fine. Run Windows Memory Diagnostic (mdsched.exe) for a basic check, or use MemTest86 from a bootable USB for a thorough multi-pass test. If errors are found, try reseating your RAM modules or replacing the faulty stick. Dell provides the compatible RAM specifications for each model on its support site.

My Dell shows IRQL_NOT_LESS_OR_EQUAL with ndis.sys — what does that mean?

ndis.sys is the Windows Network Driver Interface Specification file, which acts as an intermediary between the OS and your network adapter drivers. When ndis.sys appears in the crash dump, it usually means a network driver (Wi-Fi, Ethernet, or VPN adapter driver) is the real culprit. Update or roll back your Wi-Fi adapter driver first (Intel Wi-Fi drivers are common offenders on Dell). Also check for VPN client drivers (e.g., Cisco AnyConnect, NordVPN TAP adapter) and update or remove them.

Does Dell SupportAssist cause DRIVER_IRQL_NOT_LESS_OR_EQUAL errors?

Dell SupportAssist itself rarely causes the BSOD directly, but its automatic driver update feature can install driver versions that are not yet validated for your specific hardware configuration, triggering the error. If BSODs began after SupportAssist ran an automatic update, go to Settings → Apps, find 'Dell SupportAssist', and disable automatic driver updates. Then manually review and install only the drivers your system needs from dell.com/support. You can also use System Restore to revert to the state before SupportAssist made changes.

How to Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL Blue Screen on Dell PCs (Complete Guide)

Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD on Dell laptops and desktops with step-by-step driver updates, WinDbg analysis, and registry fixes.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,116 words

Key Takeaways

Root cause 1: A Dell-specific or third-party driver (commonly ndis.sys, nvlddmkm.sys, or Killer network drivers) is attempting to access pageable memory at an elevated IRQL, triggering the kernel stop code 0x000000D1.
Root cause 2: Outdated, corrupted, or incompatible drivers installed after a Windows Update or Dell SupportAssist auto-update cycle cause memory address violations that Windows cannot recover from.
Quick fix summary: Boot into Safe Mode, identify the offending driver from the minidump file using WinDbg or WhoCrashed, roll back or update that driver via Device Manager or Dell's official support site, then verify system stability with Driver Verifier.

Fix Approaches Compared
Method	When to Use	Time	Risk
Roll Back Driver via Device Manager	After a recent Windows Update or Dell SupportAssist driver push caused the BSOD	5–10 min	Low
Update Driver from Dell Support Site	Driver is outdated and a newer version is available for your model	10–20 min	Low
Uninstall & Reinstall Driver (Clean)	Driver files are corrupted or partially installed	15–30 min	Low-Medium
Run SFC and DISM Repair	System files are corrupted alongside the driver issue	20–40 min	Low
Use Driver Verifier to Isolate Culprit	Multiple drivers suspected; crash dumps not conclusive	1–2 hrs (monitoring)	Medium — can trigger additional BSODs intentionally
Perform System Restore	Issue appeared after a specific update and restore point exists	15–30 min	Low-Medium
Reinstall Windows (In-place Upgrade)	All other methods failed; system is repeatedly unbootable	60–120 min	Medium

Understanding the DRIVER_IRQL_NOT_LESS_OR_EQUAL Error on Dell Systems

When Windows displays a blue screen with the stop code DRIVER_IRQL_NOT_LESS_OR_EQUAL (bug check code 0x000000D1), the kernel has detected that a driver attempted to access pageable memory at an Interrupt Request Level (IRQL) that was too high. At elevated IRQLs (DISPATCH_LEVEL or above), the memory manager cannot page in memory on demand, so any access to pageable addresses causes an immediate kernel panic.

On Dell hardware, this BSOD is commonly triggered by:

Killer Networking (Rivet Networks) drivers — frequently cited in Dell XPS, G-series, and Inspiron models.
NVIDIA GPU drivers (nvlddmkm.sys) on Dell laptops with discrete graphics.
Intel Wi-Fi / Bluetooth drivers (netwtw06.sys, netwtw08.sys).
Dell Thunderbolt or USB-C drivers after firmware updates.
Third-party antivirus kernel drivers interacting badly with Dell hardware.

The full stop message you will see on screen looks like this:

Your PC ran into a problem and needs to restart.

Bug Check String:  DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code:    0x000000D1
Parameter 1:       <memory address that was referenced>
Parameter 2:       <IRQL at time of access>
Parameter 3:       0 (read) or 1 (write)
Parameter 4:       <address of the instruction that caused the fault>
Causing Driver:    [e.g., Netwtw08.sys or nvlddmkm.sys]

Step 1: Boot Into Safe Mode and Collect the Minidump

If your Dell is stuck in a BSOD loop, you need to reach Safe Mode first.

Force-interrupt three consecutive boot attempts (hold power button during Windows logo) to trigger the Windows Recovery Environment (WinRE).
Navigate to Troubleshoot → Advanced Options → Startup Settings → Restart.
Press F4 to enable Safe Mode or F5 for Safe Mode with Networking.

Once in Safe Mode, locate your crash dump files:

Small memory dumps (minidumps): C:\Windows\Minidump\*.dmp
Full kernel dump: C:\Windows\MEMORY.DMP

If no minidump files exist, configure Windows to generate them:

Press Win + R, type sysdm.cpl, press Enter.
Go to Advanced → Startup and Recovery → Settings.
Under Write debugging information, select Small memory dump (256 KB).
Set the path to %SystemRoot%\Minidump.
Click OK and reboot to capture the next crash.

Step 2: Analyze the Crash Dump with WinDbg or WhoCrashed

Option A — WhoCrashed (beginner-friendly): Download WhoCrashed from Resplendence Software, run it, and it will parse all minidumps and show you the offending driver name in plain English.

Option B — WinDbg (authoritative): Install WinDbg from the Microsoft Store or Windows SDK, then run:

windbg -z C:\Windows\Minidump\<filename>.dmp

In the WinDbg command window, type:

!analyze -v

Look for the IMAGE_NAME and MODULE_NAME fields in the output. For example:

IMAGE_NAME:  Netwtw08.sys
MODULE_NAME: Netwtw08
FAILURE_BUCKET_ID: AV_Netwtw08!unknown_function

This tells you exactly which driver caused the crash.

Step 3: Identify and Fix the Offending Driver

If the culprit is an Intel Wi-Fi driver (Netwtw06.sys / Netwtw08.sys):

Open Device Manager (devmgmt.msc).
Expand Network Adapters.
Right-click your Intel Wi-Fi adapter → Properties → Driver tab.
Click Roll Back Driver if a previous version is available.
If not, go to https://www.dell.com/support/home, enter your Service Tag, and download the latest recommended Wi-Fi driver for your model.
Use DDU (Display Driver Uninstaller) in Safe Mode if you need a fully clean reinstall.

If the culprit is an NVIDIA driver (nvlddmkm.sys):

Boot into Safe Mode.
Download DDU from https://www.guru3d.com/files-details/display-driver-uninstaller-download.html.
Run DDU, select GPU → NVIDIA, and choose Clean and restart.
After reboot, install the latest NVIDIA Game Ready or Studio driver from https://www.nvidia.com/Download/index.aspx or from Dell's support page for your specific model (Dell-customized drivers are preferred for Optimus laptops).

If the culprit is the Killer Networking driver:

Open Device Manager, locate Killer Wi-Fi or Killer Ethernet under Network Adapters.
Right-click → Uninstall device → check Delete the driver software for this device.
Download the latest Killer drivers from Dell's support page for your model.
Alternatively, replace Killer drivers with the standard Intel Wi-Fi drivers (Killer hardware is rebadged Intel), which are often more stable.

Step 4: Run System File Checker and DISM

Corrupted Windows system files can compound driver issues. Run these in an elevated Command Prompt:

sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

Reboot after completion and monitor for recurrence.

Step 5: Use Driver Verifier to Catch Elusive Culprits

If the crash dump doesn't clearly name a driver, use Driver Verifier to stress-test drivers:

verifier /standard /all

Reboot. Windows will now apply strict checks to all non-Microsoft drivers. The next BSOD will contain far more detail about the offending driver. Warning: Your system will be less stable during this period. Once you've identified the driver, disable Verifier:

verifier /reset

Step 6: Check for Dell BIOS and Firmware Updates

Outdated BIOS firmware can cause hardware-driver IRQL conflicts, especially on Dell systems with Thunderbolt, NVMe, or hybrid GPU setups.

Press Win + R, type msinfo32, and note your current BIOS version.
Go to https://www.dell.com/support/home, enter your Service Tag.
Under Drivers & Downloads, filter by BIOS.
If a newer version is available, download and run the .exe updater (ensure your Dell laptop is plugged in during BIOS update).

Step 7: Check RAM with Windows Memory Diagnostic

Faulty RAM can cause IRQL errors that mimic driver bugs:

mdsched.exe

Select Restart now and check for problems. Windows will run two full passes. Review results on next login via Event Viewer → Windows Logs → System, filter for source MemoryDiagnostics-Results.

For more thorough testing, use MemTest86 (bootable USB) and run at least 2 full passes.

Step 8: Perform a System Restore (If Available)

If the BSOD started after a specific update:

Boot into WinRE → Troubleshoot → Advanced Options → System Restore.
Select a restore point dated before the issue began.
Review which programs and drivers will be affected.
Confirm and allow Windows to restore.

This will revert driver installations without affecting personal files.

Step 9: In-Place Upgrade Repair (Last Resort)

If all else fails and your Dell is repeatedly crashing:

Download the Windows 11 or Windows 10 Media Creation Tool from Microsoft.
Mount the ISO and run setup.exe.
Choose Upgrade this PC now → Keep personal files and apps.
This replaces all system files while preserving your data, acting as a non-destructive reinstall.

Frequently Asked Questions

powershell

# ============================================================
# Dell DRIVER_IRQL_NOT_LESS_OR_EQUAL Diagnostic Script
# Run as Administrator in PowerShell
# ============================================================

# 1. List all minidump files with timestamps
Write-Host "=== Minidump Files ==="
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue |
    Sort-Object LastWriteTime -Descending |
    Select-Object Name, LastWriteTime, @{N='SizeMB';E={[math]::Round($_.Length/1MB,2)}} |
    Format-Table -AutoSize

# 2. Display recent critical errors from System Event Log
Write-Host "`n=== Recent Critical/Error Events (Last 24 Hours) ==="
Get-WinEvent -FilterHashtable @{
    LogName   = 'System'
    Level     = 1,2
    StartTime = (Get-Date).AddHours(-24)
} -MaxEvents 20 -ErrorAction SilentlyContinue |
    Select-Object TimeCreated, Id, ProviderName, Message |
    Format-List

# 3. List all third-party (non-Microsoft) kernel drivers currently loaded
Write-Host "`n=== Third-Party Kernel Drivers Loaded ==="
Get-WmiObject Win32_SystemDriver |
    Where-Object { $_.PathName -notlike "*\system32\drivers\*" -or
                   (Get-Item $_.PathName -ErrorAction SilentlyContinue).VersionInfo.CompanyName -notmatch "Microsoft" } |
    Select-Object Name, State, StartMode,
        @{N='Company';E={(Get-Item $_.PathName -ErrorAction SilentlyContinue).VersionInfo.CompanyName}},
        PathName |
    Sort-Object Company |
    Format-Table -AutoSize

# 4. Check Driver Verifier status
Write-Host "`n=== Driver Verifier Status ==="
verifier /querysettings 2>&1

# 5. Run SFC scan (output to log)
Write-Host "`n=== Running System File Checker ==="
$sfcLog = "$env:TEMP\sfc_result.txt"
Start-Process -FilePath "sfc.exe" -ArgumentList "/scannow" -Wait -NoNewWindow
Write-Host "SFC complete. Review CBS.log at C:\Windows\Logs\CBS\CBS.log for details."

# 6. Check DISM image health
Write-Host "`n=== DISM Image Health Check ==="
DISM /Online /Cleanup-Image /CheckHealth

# 7. List recently installed drivers (last 30 days)
Write-Host "`n=== Drivers Installed in Last 30 Days ==="
Get-WmiObject Win32_PnPSignedDriver |
    Where-Object { $_.DriverDate -ne $null } |
    Select-Object DeviceName, DriverVersion,
        @{N='InstallDate';E={[Management.ManagementDateTimeConverter]::ToDateTime($_.DriverDate)}},
        Manufacturer |
    Where-Object { $_.InstallDate -gt (Get-Date).AddDays(-30) } |
    Sort-Object InstallDate -Descending |
    Format-Table -AutoSize

# 8. Export network adapter driver info (common IRQL culprits)
Write-Host "`n=== Network Adapter Driver Details ==="
Get-WmiObject Win32_PnPSignedDriver |
    Where-Object { $_.DeviceClass -eq 'Net' } |
    Select-Object DeviceName, DriverVersion, Manufacturer,
        @{N='Date';E={[Management.ManagementDateTimeConverter]::ToDateTime($_.DriverDate)}} |
    Format-Table -AutoSize

Write-Host "`n=== Diagnostic Complete ==="
Write-Host "Next step: Open C:\Windows\Minidump with WinDbg or WhoCrashed to identify the crash driver."

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers and Windows systems specialists with 10+ years of experience diagnosing kernel-level failures, BSOD root-cause analysis, and enterprise driver management across Dell, HP, and Lenovo hardware fleets. Our guides combine WinDbg crash analysis, live lab testing, and real-world SRE incident data to deliver actionable, hardware-specific troubleshooting content.

Sources

Explore More windows Guides

Acer Aspire Blue Screen of Death Fix: How to Stop BSOD Crashes on Acer Laptops

Fix Acer Aspire Blue Screen of Death errors fast. Step-by-step guide covering driver updates, RAM checks, overheating, and Windows repair commands.

Acer Aspire Blue Screen of Death Fix: Step-by-Step Troubleshooting Guide (BSOD Errors Solved)

Fix Acer Aspire blue screen of death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK and more. Step-by-step commands included.

Acer Aspire Blue Screen of Death Fix: Stop Codes, Causes & Complete Solutions

Fix Acer Aspire Blue Screen of Death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK_FAILURE & more with exact commands.