How to Fix BSOD MEMORY_MANAGEMENT (0x0000001A)

By ErrorFix · Updated October 14, 2026 · 9 min read

What error 0x0000001A means

Every running program gets its memory from a component of Windows called the memory manager. When the memory manager detects that memory structures it controls have been corrupted — wrong pointers, damaged page tables, impossible states — it stops everything with the MEMORY_MANAGEMENT blue screen (stop code 0x0000001A) before the corruption can damage your files. The name is unusually direct for a blue screen: this one is about memory itself.

The most common cause is exactly what the name says: a RAM stick that is going bad. A defective memory cell stores or returns the wrong bits, and the memory manager eventually catches the damage. But this blue screen has other, less obvious triggers. Drivers that write into memory they don't own can corrupt the same structures. Unstable XMP, EXPO, or DOCP memory profiles — the factory overclock many gaming PCs ship with — are a huge trigger on custom-built machines. Corrupted Windows system files and bad sectors on the drive that holds the paging file can also produce it. So while RAM deserves the first test, a memory test alone isn't the whole diagnosis: the fixes below work through hardware and software causes in a sensible order.

Common causes

• Defective RAM stick: a failing memory cell corrupts data as it is written and read — the single most common cause of this blue screen.
• Unstable XMP / memory overclocking: factory memory profiles push RAM past stock speeds, and marginal kits crash under the tighter timings.
• Buggy drivers: graphics, chipset, and storage drivers that write into the wrong memory areas corrupt the same structures the memory manager checks.
• Corrupted Windows system files: damaged core files can corrupt memory operations, especially after a failed update or sudden shutdown.
• Bad disk sectors: when the paging file or memory-mapped files live on damaged sectors, the kernel sees it as memory corruption.

How to fix error 0x0000001A — step by step

Work through these fixes in order. The memory test in step 2 is the key diagnostic: its result tells you whether you are dealing with hardware or software.

1. Boot into Safe Mode to check stability. Interrupt the boot process three times in a row (hold the power button during the Windows logo) to reach the Recovery screen. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 for Safe Mode. Safe Mode loads only Microsoft's own drivers, so if the PC is stable here, a third-party driver or program is likely involved rather than the RAM itself. Make a note of when the crashes happen — during gaming, at boot, or randomly — because the pattern narrows the cause.
2. Run the Windows Memory Diagnostic. Press Win + R, type mdsched.exe, and choose "Restart now and check for problems." Let the scan complete fully — don't skip it, a partial test can miss bad cells. If it reports any error at all, a memory stick is defective and needs replacing, which directly fixes the memory corruption this blue screen reports. If it passes with zero errors, the RAM is probably fine and the cause is one of the software or settings issues in the steps below.
3. Update or roll back recent drivers. Press Win + X and open Device Manager. If the crashes started right after an update, find the updated device, right-click it, open Properties, go to the Driver tab, and click Roll Back Driver. If nothing recent changed, update the chipset driver, the graphics driver, and the storage controller driver from your motherboard or PC maker's support page — the manufacturer's versions matter more than Windows Update's generic ones here. Drivers that mismanage memory are a classic 0x0000001A trigger.
4. Repair system files with SFC and DISM. Open an admin Terminal (right-click Start > Terminal (Admin)). First run sfc /scannow and let it finish — it repairs protected Windows files. Then run DISM /Online /Cleanup-Image /RestoreHealth, which repairs the component store that SFC relies on. If SFC reported corruption it couldn't fix, run it once more after DISM completes. Restart the PC and use it normally to see whether the crashes stop.
5. Check the drive with CHKDSK. Bad sectors on your drive can corrupt the paging file and memory-mapped data, which the kernel reports as a memory management failure. Open an admin Terminal and run chkdsk C: /f /r, then type Y and restart when prompted so the check can run before Windows loads. The scan takes a while on large drives — let it finish. If CHKDSK marks sectors as bad and crashes continue, the drive itself may be failing and backing up your data becomes urgent.
6. Turn off XMP or memory overclocking in BIOS. On gaming and custom-built PCs, this step alone fixes a huge share of 0x0000001A crashes. Restart and enter BIOS/UEFI setup (usually Del or F2 at boot). Find the XMP, EXPO, or DOCP profile setting — often under an "AI Tweaker," "Overclocking," or "Extreme Tweaker" menu — and set it to Disabled or Auto so the RAM runs at its stock speed. Save and exit, then use the PC normally, especially under the load that used to crash it. If crashes stop, the memory kit can't hold its advertised timings; you can run it at stock speeds or replace it.
7. Test one RAM stick at a time. If the memory diagnostic pointed at the RAM but you have several sticks, find the bad one instead of replacing all of them. Power the PC off, unplug it, ground yourself, and remove all but one memory stick (check your motherboard manual for the correct single-stick slot). Boot and use the PC with each stick alone. The stick that triggers 0x0000001A by itself is the defective one — replace it. For a deeper check, MemTest86 booted from a USB drive runs multiple passes across all installed sticks at once and is the gold standard for catching intermittent faults.

Did this fix it? Quick checklist

• Windows Memory Diagnostic completed with zero errors
• SFC and DISM both completed without unrepairable corruption
• CHKDSK found no new bad sectors
• XMP/overclocking disabled and crashes have stopped under normal use

If crashes continue after all seven steps, reseat the RAM sticks — power off, unplug, pop each stick out, blow out the slots, and firmly click them back in. Poor contact causes intermittent memory errors that look exactly like failing RAM. If reseating and single-stick testing still implicate the RAM, replace the defective stick: RAM is cheap compared to the data loss a corrupt system can cause, and a matched kit is ideal if you want to keep dual-channel speeds.