Windows Stop Code Memory Management BSOD Fix

Quick answer for advanced users

Run sfc /scannow, then chkdsk /f, then Windows Memory Diagnostic. If that fails, roll back or update drivers, then run Driver Verifier. Still dead? Swap RAM sticks and test one at a time.

Context: Why this happens

The Memory Management bug check (0x0000001A) fires when Windows detects an attempt to access memory that doesn't belong to the process, or when the memory page tables are corrupted. In plain English: something wrote where it shouldn't have, or the memory itself is flaky.

I've seen this error three main ways:

• Bad RAM – most common. A single bad stick can crash you once a week or every 10 minutes.
• Driver corruption – especially older network or graphics drivers that leak memory or write to wrong addresses.
• Failing hard drive – if the page file or system files are on a bad sector, you'll see this.

Don't bother reinstalling Windows first. That's throwing a grenade at a gnat. Start with the hardware checks.

Fix steps

1. Run Windows Memory Diagnostic. Press Win+R, type mdsched.exe, hit Enter. Choose "Restart now and check for problems". Let it run a standard pass (takes 30-60 minutes). If it finds errors, your RAM is bad. Swap sticks or replace.
2. Check system files. Open Command Prompt as admin, run sfc /scannow. Let it finish. If it finds corrupted files, run dism /online /cleanup-image /restorehealth next. Then reboot.
3. Check your hard drive. In admin CMD, run chkdsk c: /f /r. Say yes to schedule on next reboot, then restart. This can take hours on a big drive. If it reports bad sectors, replace the drive.
4. Update or roll back drivers. Open Device Manager. Look for drivers with a yellow exclamation. For graphics, network, and chipset drivers, visit the manufacturer's site. If the BSOD started after a driver update, roll back via Device Manager (Properties > Driver > Roll Back Driver).
5. Run Driver Verifier. This is the nuclear option. Type verifier in Run, select "Create standard settings", then "Select driver names from a list". Only check drivers from third parties (not Microsoft). Reboot. If it triggers another BSOD, verifier will tell you which driver caused it. To disable verifier in safe mode, run verifier /reset.
6. Clear page file. Sometimes a corrupted page file causes this. Go to System Properties > Advanced > Performance > Advanced > Virtual memory > Change. Uncheck "Automatically manage", set initial and max size to 0 for all drives, apply, reboot. Then set it back to system managed.

Alternative fixes if the main ones fail

• Disable fast startup. Power Options > Choose what the power buttons do > Change settings that are currently unavailable > Uncheck "Turn on fast startup". Reboot. This fixes some memory timing issues on boot.
• Update BIOS/UEFI. Go to your motherboard or laptop manufacturer's site. A newer BIOS can fix memory compatibility bugs, especially with Ryzen systems.
• Test with one RAM stick. If you have two sticks, pull one. Run the system. If it crashes, swap to the other. If it only crashes with one stick, that stick is bad. If it crashes with both, the motherboard slot might be bad.
• Check CPU cooler mounting. I've seen loose cooler mounts cause random memory errors because of thermal expansion on the memory controller. Yes, it's rare, but I've fixed two machines this way.

Prevention tip

Keep your drivers and BIOS updated, but don't install beta drivers unless you're testing. Run a memory test every six months if your system is mission-critical. And never overclock RAM without running MemTest86 for 24 hours first — I've seen "XMP profiles" cause this error more times than I can count.