Why does my Dell laptop keep showing DRIVER_IRQL_NOT_LESS_OR_EQUAL only when connected to Wi-Fi?

This strongly points to a Wi-Fi or Killer Networking driver issue. The crash triggers when the wireless driver performs a DMA (Direct Memory Access) transfer at an elevated IRQL. Fix: Go to support.dell.com, enter your Service Tag, and download the latest Wireless LAN driver. Common culprits are killer.sys, netr28x.sys, or mrvlpcie8897.sys. If no newer driver exists, try rolling back one version or switching to the generic Microsoft Wi-Fi driver via Device Manager → Update Driver → Browse my computer → Let me pick → Microsoft Wi-Fi Direct Virtual Adapter.

My Dell shows IRQL_NOT_LESS_OR_EQUAL on boot and I cannot get into Windows. What do I do?

Boot into Windows Recovery Environment (WinRE): hold Shift while clicking Restart, or boot from Windows installation media. Navigate to Troubleshoot → Advanced Options → Startup Settings → Restart, then choose Safe Mode with Networking (option 5). Once in Safe Mode, open Device Manager and roll back or disable recently changed drivers. Alternatively, use Troubleshoot → Advanced Options → System Restore to roll back to a restore point before the crashes started.

The BSOD says 'What failed: ndis.sys' — is that the driver I need to fix?

No. ndis.sys is the Windows Network Driver Interface Specification module — it is almost never the primary cause. It appears because it was executing code on behalf of a third-party NIC or Wi-Fi driver when the crash occurred. Use WinDbg's !analyze -v output and look at the full stack trace. The actual offending module will appear in the call stack above ndis.sys — usually an Intel Ethernet, Killer Wireless, or Realtek driver.

Could a Dell BIOS update cause DRIVER_IRQL_NOT_LESS_OR_EQUAL?

Yes, in rare cases a BIOS update can change hardware initialization or power management states in a way that conflicts with existing drivers. It can also go the other way — an old BIOS may lack microcode or ACPI table fixes that a driver expects. If BSODs started immediately after a BIOS update, check Dell's BIOS release notes for known issues. You can sometimes downgrade BIOS on Dell systems by downloading an older version from support.dell.com and running it with the /forceit flag in an elevated command prompt: BIOSUpdate.exe /forceit

I replaced RAM on my Dell and now I get IRQL_NOT_LESS_OR_EQUAL blue screens. Are the sticks bad?

Possibly, but first check compatibility. Dell systems can be picky about memory specs. Verify the new RAM meets the exact DDR generation, speed (MHz), voltage, and rank requirements listed in your Dell service manual (available at dell.com/support/manuals). Also ensure the sticks are seated in the correct DIMM slots (usually slots A1 and B1 for dual-channel). Disable XMP/DOCP in BIOS and test at JEDEC base speeds first. If errors appear in MemTest86, the sticks are likely faulty or incompatible.

How to Fix DRIVER_IRQL_NOT_LESS_OR_EQUAL Blue Screen on Dell Laptops & Desktops

Fix Dell DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD fast. Step-by-step guide covering driver rollback, Windows Memory Diagnostic, verifier, and more.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,213 words

Key Takeaways

Root cause 1: A kernel-mode driver (often a network, Wi-Fi, or storage driver) is accessing an invalid memory address at an elevated IRQL, triggering the stop code DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1).
Root cause 2: Faulty, outdated, or incompatible Dell-specific drivers — particularly Intel/Killer Wireless, Realtek NIC, and Dell ControlVault drivers — are the most frequent offenders on Dell hardware.
Root cause 3: Defective RAM or BIOS settings (e.g., XMP/DOCP overclocking profiles) can cause memory address violations that mimic driver faults.
Quick fix summary: Identify the offending driver from the minidump file using WinDbg or WhoCrashed, then roll back or update that specific driver. If unclear, run Driver Verifier to isolate the culprit, check RAM with Windows Memory Diagnostic, and update Dell BIOS and chipset drivers from support.dell.com.

Fix Approaches Compared
Method	When to Use	Time	Risk
Analyze Minidump with WinDbg/WhoCrashed	First step — BSOD has occurred at least once and dump file exists in C:\Windows\Minidump	10-20 min	Low
Roll Back or Update Offending Driver	After identifying the driver name from the dump file	5-15 min	Low
Reinstall Dell Network/Wi-Fi Drivers from support.dell.com	Wi-Fi or NIC driver named in dump (e.g., e1d65x64.sys, netr28x.sys, killer.sys)	15-30 min	Low
Run Driver Verifier	Driver in dump is unknown or multiple suspects exist	30-60 min (may trigger more BSODs)	Medium
Windows Memory Diagnostic / MemTest86	BSODs occur randomly across different scenarios without a consistent driver	1-8 hours	Low
Update Dell BIOS & Chipset Drivers	System is running old BIOS; crash correlates with hardware events	20-40 min	Medium
System Restore / In-place Upgrade Repair	BSODs started after a Windows Update or software installation	30-90 min	Low-Medium
Clean Windows Reinstall	All other methods exhausted; hardware confirmed healthy	2-4 hours	High (data loss risk)

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), it means a kernel-mode driver attempted to access pageable memory at a process IRQL (Interrupt Request Level) that was too high. In plain English: a driver tried to read or write to memory it should not have touched while the CPU was handling a high-priority interrupt. Windows halts the system to prevent data corruption.

On Dell hardware specifically, the most commonly blamed drivers include:

e1d65x64.sys / e1d68x64.sys — Intel Ethernet driver
killer.sys / Rts5RfBus.sys — Killer Networking (now Intel) Wi-Fi
netr28x.sys / mrvlpcie8897.sys — Wireless LAN mini-port drivers
delldsm.sys — Dell Data Security driver
iaStorA.sys / storahci.sys — Intel Rapid Storage / AHCI driver
ndis.sys — Windows network stack (often called by a faulty NIC driver)

The full crash message you will see on screen:

Your PC ran into a problem and needs to restart.
We're just collecting some error info, and then we'll restart for you.

STOP CODE: DRIVER_IRQL_NOT_LESS_OR_EQUAL
What failed: e1d65x64.sys (or similar)

Step 1: Locate and Read the Minidump File

Windows writes a crash dump to C:\Windows\Minidump\ after every BSOD. This is your primary clue.

Option A — WhoCrashed (free, beginner-friendly):

Download WhoCrashed from https://www.resplendence.com/whocrashed.
Install and run it. Click Analyze.
Look for the "Probably caused by" line — it names the driver file (e.g., e1d65x64.sys).

Option B — WinDbg (advanced):

Install WinDbg from the Microsoft Store or Windows SDK.
Open WinDbg → File → Open Crash Dump → navigate to C:\Windows\Minidump\.
In the command window type: !analyze -v
Look for MODULE_NAME and IMAGE_NAME fields — these identify the culprit driver.

Record the exact driver filename before proceeding.

Step 2: Identify the Driver and Its Owner

Once you have the filename, map it to its software package:

Driver File	Package / Manufacturer
e1d65x64.sys	Intel Ethernet Adapter driver
killer.sys	Intel Killer Networking
netr28x.sys	Mediatek/Ralink Wi-Fi
delldsm.sys	Dell Data Security / Encryption
iaStorA.sys	Intel RST (Rapid Storage Technology)
storahci.sys	Microsoft AHCI (check BIOS SATA mode)
ndis.sys	Windows NDIS — blame the NIC driver, not this

Step 3: Roll Back or Update the Driver

To roll back:

Right-click Start → Device Manager.
Expand the relevant category (Network Adapters, Disk Drives, etc.).
Right-click the device → Properties → Driver tab → Roll Back Driver.
Reboot and monitor for stability.

To update from Dell support site:

Go to https://www.dell.com/support/home and enter your Service Tag (printed on the bottom of your laptop or back of desktop).
Click Drivers & Downloads, filter by the category matching your faulty driver.
Download and install the latest version.
Reboot.

To uninstall and reinstall cleanly (recommended for network drivers):

Download DDU (Display Driver Uninstaller) from Wagnardsoft — works for network drivers too.
Boot into Safe Mode (msconfig → Boot → Safe boot → Minimal).
Run DDU to fully remove the driver.
Reboot normally and install fresh driver from Dell.

Step 4: Run Driver Verifier (if driver is unknown)

If WhoCrashed shows ntoskrnl.exe or an ambiguous entry, use Driver Verifier to stress-test all non-Microsoft drivers:

Open an elevated Command Prompt.
Run: verifier /standard /all
Reboot. When the next BSOD occurs, the dump will now contain the exact offending driver.
After identifying the driver, disable Verifier: verifier /reset then reboot.

⚠️ Warning: Driver Verifier intentionally causes BSODs. Do not leave it enabled permanently. Save your work before using it.

Step 5: Test RAM

Defective memory can produce DRIVER_IRQL_NOT_LESS_OR_EQUAL crashes. Test your RAM:

Windows Memory Diagnostic (quick):

Press Win + R, type mdsched.exe, press Enter.
Choose Restart now and check for problems.
Review results after reboot in Event Viewer → Windows Logs → System, source MemoryDiagnostics-Results.

MemTest86 (thorough — recommended):

Download from https://www.memtest86.com/ and create a bootable USB.
Boot from USB and run at least 2 full passes (4+ passes ideal).
Any errors = faulty RAM. If you have 2 sticks, remove one and test each individually.

Also try disabling XMP/DOCP in BIOS (Dell BIOS: F2 at boot → Performance → Memory).

Step 6: Update Dell BIOS and Chipset Drivers

An outdated BIOS can cause incorrect ACPI/power management behavior that leads to these crashes.

Check current BIOS version: msinfo32 → System Summary → BIOS Version.
Visit https://www.dell.com/support/home → enter Service Tag → Drivers & Downloads → BIOS category.
Download and run the BIOS update executable (ensure laptop is plugged in).
Also download and install the Chipset driver and Intel Management Engine driver from the same page.

Step 7: Check for Windows Update Conflicts

A Windows cumulative update or driver update pushed via Windows Update can introduce regressions. Check:

Settings → Update & Security → View Update History.
Note the date of the last successful update vs. when BSODs started.
To uninstall a driver update: Settings → Windows Update → View Update History → Uninstall Updates.
To pause future driver updates temporarily:
- Run gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Windows Update.
- Enable Do not include drivers with Windows Updates.

Step 8: System File Check and DISM Repair

Corrupted system files can cause stop codes. Run these in an elevated PowerShell:

# Check and repair system files
sfc /scannow

# Restore Windows component store health
DISM /Online /Cleanup-Image /RestoreHealth

# Reboot after completion
Restart-Computer

If SFC reports corruption it cannot repair, consider an in-place upgrade repair install using the Windows 11/10 ISO mounted as a DVD or USB, running setup.exe and choosing Keep files and apps.

Frequently Asked Questions

powershell

# ============================================================
# Dell DRIVER_IRQL_NOT_LESS_OR_EQUAL Diagnostic Script
# Run in an elevated PowerShell window (Run as Administrator)
# ============================================================

# 1. List all minidump files with timestamps
Write-Host "`n--- Minidump Files ---" -ForegroundColor Cyan
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. Check recent BSOD events in System Event Log
Write-Host "`n--- Recent BSOD Events (Event ID 1001) ---" -ForegroundColor Cyan
Get-WinEvent -LogName System -FilterXPath "*[System[EventID=1001]]" -MaxEvents 5 -ErrorAction SilentlyContinue |
    Select-Object TimeCreated, Message |
    Format-List

# 3. Display current BIOS version
Write-Host "`n--- BIOS Information ---" -ForegroundColor Cyan
Get-WmiObject -Class Win32_BIOS | Select-Object SMBIOSBIOSVersion, Manufacturer, ReleaseDate | Format-List

# 4. List all third-party (non-Microsoft) kernel drivers currently loaded
Write-Host "`n--- Loaded Third-Party Drivers ---" -ForegroundColor Cyan
Get-WmiObject Win32_SystemDriver |
    Where-Object { $_.State -eq 'Running' -and $_.PathName -notmatch 'system32\\drivers\\(?:acpi|disk|ntfs|volmgr|partmgr|fltmgr|ntkrnl)' } |
    Select-Object Name, DisplayName, PathName |
    Sort-Object Name |
    Format-Table -AutoSize

# 5. Check driver signing status (unsigned drivers are high risk)
Write-Host "`n--- Checking for Unsigned Drivers ---" -ForegroundColor Cyan
$signedDrivers = Get-WindowsDriver -Online -All | Where-Object { $_.Driver -ne $null }
$unsignedDrivers = $signedDrivers | Where-Object { $_.BootCritical -eq $false -and $_.OriginalFileName -match '\.sys$' }
if ($unsignedDrivers) {
    $unsignedDrivers | Select-Object Driver, OriginalFileName, ProviderName | Format-Table -AutoSize
} else {
    Write-Host "No obviously unsigned drivers found." -ForegroundColor Green
}

# 6. Run System File Checker
Write-Host "`n--- Running System File Checker (sfc /scannow) ---" -ForegroundColor Cyan
Write-Host "This may take 5-10 minutes..."
sfc /scannow

# 7. Run DISM health check
Write-Host "`n--- Running DISM Component Store Health Check ---" -ForegroundColor Cyan
DISM /Online /Cleanup-Image /CheckHealth

# 8. Check RAM info
Write-Host "`n--- Physical Memory Information ---" -ForegroundColor Cyan
Get-WmiObject -Class Win32_PhysicalMemory |
    Select-Object BankLabel, Capacity, Speed, Manufacturer, PartNumber |
    Format-Table -AutoSize

# 9. Run Windows Memory Diagnostic (prompts to schedule on next reboot)
Write-Host "`n--- Schedule Windows Memory Diagnostic ---" -ForegroundColor Cyan
$response = Read-Host "Schedule Windows Memory Diagnostic on next reboot? (y/n)"
if ($response -eq 'y') {
    mdsched.exe
}

# 10. Enable Driver Verifier for all non-Microsoft drivers (optional - CAUTION)
Write-Host "`n--- Driver Verifier (OPTIONAL - will cause intentional BSODs) ---" -ForegroundColor Yellow
Write-Host "To enable:  verifier /standard /all" -ForegroundColor Yellow
Write-Host "To disable: verifier /reset" -ForegroundColor Yellow
Write-Host "Only use this if you could not identify the driver from minidumps." -ForegroundColor Yellow

Write-Host "`n--- Diagnostic Complete ---" -ForegroundColor Green
Write-Host "Review output above. Check C:\Windows\Minidump\ files with WhoCrashed or WinDbg for definitive driver identification."

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, Microsoft-certified system administrators, and SRE practitioners with 10+ years of experience diagnosing Windows kernel crashes, BSOD stop codes, and hardware-software compatibility issues across enterprise and consumer environments. Our guides are tested on real hardware and validated against official Microsoft and OEM documentation.

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.