Run Windows Memory Diagnostic (mdsched.exe) and, if you overclock memory, disable XMP/EXPO. Reseat or test RAM sticks one at a time. Then update graphics and chipset drivers and run DISM and sfc /scannow.

What's going on

MEMORY_MANAGEMENT covers a range of internal memory-manager failures: corrupted page tables, inconsistent memory counts and similar. Because the memory manager relies on RAM returning correct data, defective or unstable RAM is the first thing to test.

When RAM tests clean, the cause is generally a driver writing over memory it doesn’t own, or Windows system files damaged by a failed update or disk error.

How it shows up

  • Blue screen: “Stop code: MEMORY_MANAGEMENT”.
  • Random crashes, often under memory-heavy work (games, browser with many tabs, editing).
  • Programs crash or files corrupt unexpectedly.

What causes it

  • Faulty, loose or mismatched RAM modules.
  • Unstable XMP/EXPO memory profiles or overclocks.
  • Buggy drivers (graphics drivers in particular).
  • Corrupted system files or disk errors.

How to fix it, step by step

  1. Test memoryRun mdsched.exe → Restart now. For a longer test, use MemTest86 from a USB stick for several passes.
  2. Disable memory overclocksTurn off XMP/EXPO in the BIOS as a test, or update the BIOS for better memory compatibility.
  3. Reseat and isolate RAMPower off, unplug, reseat the sticks, then test with one stick at a time to find a faulty module.
  4. Update driversInstall the latest graphics and chipset drivers from the manufacturer.
  5. Repair WindowsRun DISM and SFC (commands below), then chkdsk C: /scan.

Command

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Run in an elevated Command Prompt (Run as administrator). DISM can take 10–20 minutes; run sfc after it finishes, then restart.

Check it's fixed: Memory tests pass and the PC runs for several days without a MEMORY_MANAGEMENT crash.

Keeping it from coming back

Use matched RAM kits listed in the motherboard's compatibility list and keep the BIOS updated.