WhyCrashed

STOP 0x0000000A

IRQL_NOT_LESS_OR_EQUAL

Windows (or a driver running inside it) touched memory at the wrong moment — while the system was in a state where that memory was off-limits. Nine times out of ten a device driver is responsible; less often it's faulty RAM.

Likely causes, most common first

How to fix it

1. Update or roll back the identified driver easy

  1. The report above names the driver most likely responsible — get its newest version from the vendor's own site (link in the driver card).
  2. If the driver was updated recently and the crashes started after that, roll it back instead: Device Manager → the device → Properties → Driver → Roll Back Driver.
  3. Reboot and use the PC normally to confirm the crashes stop.

2. Update the usual suspects easy

  1. Update your network driver (Wi-Fi and Ethernet) from your PC or motherboard maker's support page.
  2. Update your GPU driver from NVIDIA, AMD or Intel directly.
  3. Run Windows Update, including optional driver updates.
  4. If you installed antivirus or VPN software recently, uninstall it temporarily and see if the crashes stop.

3. Test your RAM moderate

  1. Press Start, type "Windows Memory Diagnostic", run it and let the PC reboot and test.
  2. If you use an XMP/EXPO memory profile in the BIOS, turn it off temporarily — an unstable profile causes exactly this crash.
  3. If errors appear, test one RAM stick at a time to find the bad one.

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 1Memory address that was referenced
Parameter 2IRQL (system state level) at the time
Parameter 30 = read, 1 = write
Parameter 4Address 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 →