STOP 0x000000D1
DRIVER_IRQL_NOT_LESS_OR_EQUAL
A driver tried to touch memory it wasn't allowed to at that moment. Almost always a buggy or outdated driver — and the crash data usually names it directly.
Likely causes, most common first
- A buggy or outdated device driver — network (Wi-Fi/Ethernet) drivers are the classic cause
- Antivirus, VPN or anti-cheat drivers
- A driver installed or updated just before the crashes began
- Rarely, faulty RAM making a good driver look bad
How to fix it
1. Update or roll back the identified driver easy
- The report above names the driver at the faulting address — install its newest version from the vendor's own site (link in the driver card).
- If it was updated recently and crashes started after, roll it back: Device Manager → device → Properties → Driver → Roll Back Driver.
- Reboot and confirm the crashes stop.
2. Update network and security drivers easy
- Update your Wi-Fi and Ethernet drivers from your PC or motherboard maker's support page.
- Update or temporarily remove third-party antivirus/VPN software.
- Run Windows Update including optional driver updates.
3. Rule out RAM moderate
- Run Windows Memory Diagnostic (Start → type "memory") and let it test.
- If you overclock RAM (XMP/EXPO), disable the profile temporarily.
The four parameters on the blue screen
Windows shows four hex numbers with this stop code. Here's what each means — our analyzer decodes them automatically from your dump file.
| Parameter 1 | Memory address that was referenced |
| Parameter 2 | IRQL (system state level) at the time |
| Parameter 3 | 0 = read, 1 = write, 8 = execute |
| Parameter 4 | Address of the instruction that did it |
Got a crash dump? Get your verdict in seconds
Drop the .dmp file into our analyzer — it runs entirely in your browser. No upload, no size limit, no account.
Analyze my dump file →