How to Fix the MEMORY_MANAGEMENT Blue Screen on Windows
The MEMORY_MANAGEMENT stop code (0x0000001A) means Windows hit a fatal memory error — but the source is usually one of two things: a failing RAM stick or a misbehaving driver/corrupted file. This guide tests memory definitively first, then walks the driver and system-file fixes so you repair the real cause.
- ✓Tests RAM with Windows Memory Diagnostic (and points you to MemTest86 for a thorough pass)
- ✓Repairs corrupted system files and updates the GPU/chipset drivers that trigger 0x1A
- ✓Clears unstable XMP/overclock memory profiles that cause intermittent crashes
Best for 0x0000001A crashes under load, after a RAM upgrade, or after enabling an XMP/EXPO memory profile.
Main Troubleshooting Guide
How to Fix Blue Screen of Death (BSOD) →Complete symptoms, causes, and step-by-step solutions
Symptoms
You might be experiencing this problem if you notice:
- •Blue screen with the "MEMORY_MANAGEMENT" stop code
- •Stop code 0x0000001A shown on the BSOD
- •Crashes during memory-intensive tasks (games, video editing, VMs, large builds)
- •Random BSODs with no consistent trigger
- •The system restarts unexpectedly under load
- •Crashes began after adding RAM or enabling XMP/EXPO
- •Occasional file corruption or apps crashing alongside the BSODs
- •BSOD on wake from sleep or during heavy multitasking
Pattern matters: crashes right after a RAM upgrade or XMP enable point to memory/config; crashes tied to a specific app or after a driver update point to drivers; widespread instability points to corrupted system files.
What RescuePC checks for MEMORY_MANAGEMENT crashes
RescuePC runs the memory and integrity checks and updates the drivers most associated with 0x1A, so you can quickly tell a hardware fault from a software one.
- →Launches the memory test and reads the MemoryDiagnostics-Results from the Event Log
- →Runs SFC and DISM to repair the corrupted system files that cause 0x1A
- →Checks GPU and chipset drivers — outdated graphics drivers are a frequent trigger
- →Flags an active XMP/overclock profile that may be running RAM beyond stable limits
- →Checks the pagefile (virtual memory) configuration for a known misconfiguration cause
This is most useful when you cannot tell whether the BSOD is failing RAM or a driver, and you want the memory test plus integrity repairs run together.
When These Fixes Resolve It
- ✓The memory test is clean and the cause is a driver or system file
- ✓Crashes began after a driver update (rollback fixes it)
- ✓Crashes began after enabling XMP/EXPO (disabling it fixes it)
- ✓Reseating RAM or running a single stick stops the crashes
These cover the software and configuration causes of 0x1A — driver updates, system-file repair, XMP/overclock cleanup, and RAM reseating.
When the RAM Is Genuinely Failing
If the hardware is bad, only replacement fixes it:
- ⚠Memory Diagnostic or MemTest86 reports errors on a stick
- ⚠Crashes continue with default memory speeds and updated drivers
- ⚠One specific stick or slot reliably reproduces the BSOD
Common Causes
- ⚠A failing or faulty RAM module
- ⚠Mismatched or incompatible RAM sticks running together
- ⚠An unstable XMP/EXPO profile or manual memory overclock
- ⚠Outdated or corrupt drivers — especially GPU and chipset
- ⚠Corrupted Windows system files
- ⚠A misconfigured or disabled pagefile (virtual memory)
- ⚠A failing storage drive corrupting paged memory
- ⚠Dust/poor seating causing intermittent RAM contact
Solutions
Solution 1: Test Your RAM Definitively
- 1Press Windows + R, type mdsched.exe, choose "Restart now and check for problems"
- 2Let it run (use the Extended test via F1 for a thorough pass — 20+ minutes)
- 3After reboot, open Event Viewer > Windows Logs > System and find the "MemoryDiagnostics-Results" entry
- 4For a much more rigorous test, run MemTest86 from a USB stick for several passes
- 5Any reported errors = a RAM fault; proceed to reseat/isolate sticks below
Solution 2: Reseat and Isolate RAM
- 1Power off, unplug, and open the case (or laptop RAM hatch)
- 2Remove each RAM stick and reseat it firmly until the clips snap (a common intermittent cause)
- 3If you have multiple sticks, run with just one stick and see if crashes stop, then test each stick/slot in turn
- 4Confirm the sticks are a matched/ supported kit for your motherboard
- 5If one stick reliably crashes the system, replace it
Solution 3: Clear Unstable XMP / Overclock
- 1Restart into BIOS/UEFI
- 2Disable XMP/EXPO (set memory to default JEDEC speed) and remove any manual RAM/CPU overclock
- 3Save and boot into Windows; if crashes stop, your XMP profile was unstable on this kit
- 4Re-enable XMP only if stable, or run the RAM one step below its rated speed
- 5Re-test under load
Solution 4: Repair System Files and the Pagefile
- 1Open Command Prompt as Administrator
- 2Run: DISM /Online /Cleanup-Image /RestoreHealth
- 3Run: sfc /scannow, then restart
- 4Open sysdm.cpl > Advanced > Performance Settings > Advanced > Virtual memory > Change; ensure "Automatically manage paging file size" is checked
- 5Restart and monitor for further crashes
Solution 5: Update GPU/Chipset Drivers and Check the Drive
- 1Open Device Manager > Display adapters > update the GPU driver (or do a clean install from NVIDIA/AMD/Intel)
- 2Install the latest chipset driver from your PC or motherboard maker
- 3Open Command Prompt as Administrator and run: chkdsk C: /scan to check the system drive
- 4If you suspect the driver but cannot find it, run Driver Verifier (verifier /standard /all) to force the faulty driver to name itself in the next crash dump (reset with verifier /reset)
- 5Restart and test under load
Fix MEMORY_MANAGEMENT blue screens — the exact commands
MEMORY_MANAGEMENT (0x1A) points at RAM, the pagefile, or memory-corrupting drivers. Test in that order — RAM first, because no software fix survives bad RAM.
mdsched.exeWindows Memory Diagnostic — reboots and tests RAM. Any reported error means a physical RAM problem; stop and reseat/replace modules.
sfc /scannowRepairs corrupted system files, a secondary cause of 0x1A crashes.
DISM /Online /Cleanup-Image /RestoreHealthRepairs the component store backing SFC.
chkdsk C: /f /rRepairs disk errors that corrupt the pagefile — pagefile corruption raises MEMORY_MANAGEMENT even with good RAM.
wevtutil qe System /c:3 /rd:true /f:text /q:"*[System[(EventID=1001)]]"Prints the last BugCheck (crash) records with parameters — confirms the stop code and any named driver.
Memory Diagnostic results are logged in Event Viewer (MemoryDiagnostics-Results). One pass clean is not proof — run overnight MemTest for intermittent faults. RescuePC reads the crash records and maps 0x1A parameters to the likely cause.
What Triggers Your 0x1A Crash?
Started right after a RAM upgrade or enabling XMP/EXPO
Likely cause: Incompatible/mismatched RAM or an unstable memory overclock
Crashes tied to one app or after a driver update
Likely cause: A faulty GPU/chipset driver
Memory test reports errors
Likely cause: A failing RAM stick — reseat, test one stick at a time, or replace
Fix MEMORY_MANAGEMENT Blue Screen Automatically
RescuePC Toolkit includes 109+ automated repairs that fix this problem with one click. No command line knowledge required.
Download Now - Free TrialNo credit card required • Works on Windows 10 & 11
Test Memory Before You Buy Memory
MEMORY_MANAGEMENT is half hardware, half software — the memory test tells you which half to fix.
- →Clean memory test = driver or system file
- →Errors reported = reseat / isolate / replace RAM
- →Started after XMP = unstable overclock
- →Started after a driver = roll it back