DRIVER_IRQL_NOT_LESS_OR_EQUAL is the blue screen most Windows users will meet at least once. Unlike some cryptic stop codes, this one is refreshingly honest: a driver did something illegal with memory, and the blue screen usually tells you which driver by name. On Dell laptops the offender is most often a network, storage, or graphics driver, and the fix is usually a proper update away.
The key word is “proper.” Grabbing a random driver from a third-party updater site is how many of these crashes start. This guide shows you how to identify the driver, replace it with the correct Dell-certified version, and verify the fix. Work through the steps in order.
Why this happens
- A driver accessed paged memory at too high an IRQL. Drivers must follow strict rules about memory access levels; breaking them crashes the system by design.
- Outdated network drivers. Intel and Killer Wi-Fi drivers on Dell laptops are the single most common trigger.
- Corrupt driver files. Disk errors or interrupted installs can damage a driver binary so it misbehaves.
- Conflicting drivers. Two drivers fighting over the same device, often after mixing Dell and Windows Update drivers.
- Faulty RAM. Memory errors can make a correct driver appear to access the wrong address.
- Overclocking or unstable system. Aggressive settings cause timing violations that surface as IRQL errors.
- Recent Windows update. A kernel change can expose a latent bug in an older driver.
How to fix it
Work through these in order, testing for stability after each fix before moving on.
Fix 1: Note the driver name on the blue screen
The fastest diagnosis is free and takes seconds.
- The next time the blue screen appears, look for a line like What failed: netwtw10.sys near the bottom.
- Write down the exact filename.
- Search the filename to identify the device (for example, netwtw10.sys is Intel Wi-Fi, nvlddmkm.sys is NVIDIA graphics, iaStorAC.sys is Intel storage).
- That device’s driver is your prime suspect for Fix 2.
- If no filename appears, disable automatic restart so you can read future crashes: Control Panel then System then Advanced system settings then Startup and Recovery settings, and uncheck Automatically restart.
Fix 2: Update the named driver from Dell
Replace the suspect with Dell’s current certified version.
- Go to Dell Support and enter your Service Tag.
- Find the driver for the device identified in Fix 1 and download the latest version.
- Open Device Manager (Win + X), right-click the device, and choose Uninstall device (check Attempt to remove the driver if offered).
- Restart, then install the Dell driver package you downloaded.
- Restart again and test.
Fix 3: Update the big three if no driver was named
When the blue screen names nothing, refresh the usual suspects.
- From Dell Support , download the latest network (Wi-Fi and Ethernet), chipset/storage, and graphics drivers for your model.
- Install network first, then chipset, then graphics, restarting between each.
- For Intel-based network chips, the Intel Driver & Support Assistant can also find the newest network driver.
- Test for a full day of normal use before declaring victory.
Fix 4: Run SFC and DISM
Repair corrupted system and driver files.
- Open Terminal (Admin) with Win + X.
- Run
sfc /scannowand wait for completion. - Run
DISM /Online /Cleanup-Image /RestoreHealthif SFC could not fix everything. - Run
sfc /scannowonce more to confirm. - Restart and monitor.
Fix 5: Test your RAM
Bad memory produces IRQL errors that look exactly like driver bugs.
- Press Win + R, type
mdsched.exe, and press Enter. - Choose Restart now and check for problems and select the Extended test with F1.
- Run at least two passes.
- Errors mean a failing stick; test sticks individually if you have two, and replace the bad one.
Fix 6: Use Driver Verifier to trap the culprit
If the crashes continue with no named driver, force the issue.
- Create a restore point: search Create a restore point in Start and click Create.
- Open Terminal (Admin) and run
verifier. - Choose Create standard settings, then Automatically select unsigned drivers, and finish the wizard.
- Restart and use the laptop; Verifier will crash the guilty driver quickly and the dump will name it.
- After the crash, boot to Safe Mode if needed and run
verifier /resetto disable it. - Update or remove the driver the dump names.
Fix 7: Check for overheating and reset BIOS
Thermal instability can trigger IRQL violations under load.
- Monitor temperatures during heavy tasks; sustained CPU temperatures above 95°C are suspect.
- Clean vents with compressed air and ensure the fans spin freely.
- Enter BIOS setup and load optimized defaults to clear any unstable custom settings.
- Retest under the same workload that caused crashes.
Fix 8: Reset Windows if nothing else resolves it
A damaged installation can keep producing IRQL crashes regardless of drivers.
- Open Settings then System then Recovery and click Reset PC.
- Choose Keep my files first.
- If crashes persist, back up and choose Remove everything.
- Install drivers only from Dell afterward.
For the general Windows 11 version, see driver IRQL not less or equal on Windows 11 , and for the post-update variant, read driver IRQL after a Windows 11 update .
Closing
DRIVER_IRQL_NOT_LESS_OR_EQUAL is common precisely because it is honest: it usually names its own cause right on the blue screen. Read the filename, update that driver from Dell, and you have solved most cases before lunch. For the stubborn ones, Driver Verifier and a memory test close the remaining gaps. It is a very fixable error; it just demands that you update the right driver instead of all of them.
