STOP 0x0000001A
MEMORY_MANAGEMENT
Windows' memory manager found its own bookkeeping corrupted. That usually means the RAM itself is faulty or unstable — though a badly behaved driver can corrupt memory too.
Worth knowing: Recurring 0x1A crashes are a hardware signal more often than a software one — do not skip the RAM test.
Likely causes, most common first
- Faulty or failing RAM — the single most common cause of this code
- An unstable memory overclock or XMP/EXPO profile
- A driver corrupting memory (GPU and storage drivers most often)
- A failing SSD corrupting the page file
How to fix it
1. Test your RAM first moderate
- Press Start, type "Windows Memory Diagnostic", run it and let the PC reboot and test.
- For a more thorough test, create a MemTest86 USB stick and run at least 4 passes.
- If you use XMP/EXPO in the BIOS, disable it and re-test — this alone fixes a large share of 0x1A crashes.
- If errors appear, test one stick at a time to find the faulty one and replace it.
2. Update the identified driver easy
- A driver is named in the report above — update it from the vendor link in the driver card, then keep watching for crashes.
- Bear in mind: with memory corruption, the named driver can be a victim rather than the culprit, so still run the RAM test.
3. Repair Windows system files easy
- Right-click Start → Terminal (Admin).
- Run: sfc /scannow
- Then run: DISM /Online /Cleanup-Image /RestoreHealth
- Reboot.
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 | Subtype code identifying the exact violation |
| Parameter 2 | Varies by subtype |
| Parameter 3 | Varies by subtype |
| Parameter 4 | Varies by subtype |
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 →