The Problem
Your PC crashes to a blue screen with the stop code MEMORY_MANAGEMENT (technical code 0x0000001A). It may happen randomly, under heavy load like gaming, or increasingly often over time.
This stop code means Windows detected a serious error in how memory is being handled. The most common physical cause is failing RAM, but faulty drivers, corrupted system files, an unstable RAM overclock (XMP/EXPO), and even a failing SSD can trigger the same crash. The steps below go from most likely to least likely.
Quick Checks Before You Start
- Did you recently add or reseat RAM? Power off, unplug, and make sure the sticks are fully clicked into their slots.
- Did you enable XMP/EXPO or overclock recently? Enter BIOS and disable it temporarily — unstable memory profiles are a classic trigger.
- Crashing constantly? Boot into safe mode first so you can work: see how to enter Safe Mode in Windows 11.
Step 1: Run Windows Memory Diagnostic
Test whether your RAM itself is failing.
- Press
Win + R, typemdsched.exe, and press Enter. - Choose Restart now and check for problems.
- Your PC reboots into a memory test that takes several minutes. Let it complete both passes.
- After Windows restarts, the result appears as a notification. You can also find it in Event Viewer > Windows Logs > System (look for MemoryDiagnostics-Results).
If errors are found, you almost certainly have a failing RAM stick. With two or more sticks, test them one at a time in the same slot to identify the bad one, then replace it. For a more thorough test, the free tool MemTest86 (run from a USB drive) catches errors Windows Memory Diagnostic misses.
Step 2: Update or Roll Back Drivers
A buggy driver corrupting memory produces the same stop code as bad hardware.
- Right-click Start > Device Manager.
- Update your display adapter driver first — GPU drivers are the most frequent software cause. Download directly from NVIDIA, AMD, or Intel.
- If the crashes started right after a driver update, roll it back instead: right-click the device > Properties > Driver tab > Roll Back Driver.
- Also update chipset drivers from your motherboard or laptop manufacturer's support page. Our guide to updating outdated drivers covers this safely.
Step 3: Repair Corrupted System Files
- Right-click Start > Terminal (Admin).
- Run:
sfc /scannow - Then run:
DISM /Online /Cleanup-Image /RestoreHealth - Restart your PC. The full procedure is in repair Windows 11 system files with SFC and DISM.
Step 4: Check Your Disk and Page File
The page file extends RAM onto your drive — if the drive is failing, memory errors follow.
- In Terminal (Admin), run:
Schedule it for the next restart when prompted, then reboot.chkdsk C: /f /r - Check drive health with the steps in check SSD and hard drive health.
- Reset the page file: Settings > System > About > Advanced system settings > Performance Settings > Advanced > Virtual memory Change — check Automatically manage paging file size for all drives.
Step 5: Undo Overclocks and Update BIOS
- In BIOS/UEFI, load Optimized Defaults to clear any memory overclock or XMP/EXPO profile.
- If your system is stable afterward, the profile was unstable — try a lower speed or update your BIOS, since memory compatibility fixes ship in BIOS updates regularly.
If the blue screens continue after RAM tests pass and drivers are current, save your files and consider reinstalling Windows without losing data to rule out deep OS corruption.
Getting different stop codes each time? Random, changing stop codes strongly suggest hardware (RAM or PSU). Start with the general blue screen troubleshooting guide. Related codes: CRITICAL_PROCESS_DIED, KERNEL_SECURITY_CHECK_FAILURE, PAGE_FAULT_IN_NONPAGED_AREA, and IRQL_NOT_LESS_OR_EQUAL.
Related guides
How to Fix PFN_LIST_CORRUPT in Windows 11
PFN_LIST_CORRUPT means Windows' index of physical memory pages was damaged. Test the RAM first, then the storage driver — here is the order that works.
How to Fix BAD_POOL_HEADER in Windows 11
BAD_POOL_HEADER means a driver corrupted Windows' kernel memory pool. Track down the driver, antivirus, or RAM stick behind it with these ordered checks.
How to Fix KMODE_EXCEPTION_NOT_HANDLED in Windows 11
KMODE_EXCEPTION_NOT_HANDLED means a kernel-mode program hit an error nothing caught. Find the driver behind it and stop the crashes with these ordered checks.
How to Fix KERNEL_DATA_INPAGE_ERROR in Windows 11
KERNEL_DATA_INPAGE_ERROR means Windows could not read data back from the drive. Read the sub-code, test the disk and cable, and fix the real cause.
Fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED in Windows 11
This blue screen usually names the driver that crashed, right on the screen. Read that .sys file, roll the driver back, and stop the reboot loop for good.