Memory Management Blue Screen (0x1A): How to Fix It in Windows 10 and 11
The MEMORY_MANAGEMENT stop code means Windows hit a serious memory error. Test your RAM, update drivers, repair system files and check the disk, in that order.
By PC MomentUpdated 7 min read

A memory management blue screen shows the stop code MEMORY_MANAGEMENT, which is bug check 0x1A. Microsoft describes it as a severe memory management error. On Windows 11 version 24H2 and later the crash screen is black instead of blue, but it is the same error. The quickest useful check is to run Windows Memory Diagnostic. If the RAM passes, update drivers, repair system files and check the disk.
What causes the memory management stop code
Microsoft’s reference for bug check 0x1A lists dozens of sub-causes. Several are flagged as “probably a hardware error,” and others come from a driver handling memory incorrectly. In practice, the usual suspects are:
- Faulty or loose RAM. A bad memory module is the classic cause.
- Drivers. Microsoft’s own crash analysis attributes about 70% of all stop errors to third-party driver code and about 10% to hardware.
- Storage problems. One documented sub-cause (parameter 0x3F) is a failed read from the page file, which lives on your drive.
- Corrupted system files. These can come from failed updates or disk errors.
- Memory overclocking. XMP or EXPO profiles run RAM beyond standard settings, and Intel notes that changing clock frequency or voltage may reduce stability.
Important: Before you start, back up your important files to an external drive or cloud storage. Repeated crashes can corrupt data.
How to fix the memory management blue screen
Work through these in order. Restart and use the PC normally after each fix to see if the crashes stop.
| Fix | When it helps | Note |
|---|---|---|
| 1. Undo recent changes | Crashes started after new hardware or software | Use safe mode if you can’t reach the desktop |
| 2. Windows and driver updates | A driver handles memory incorrectly | Free, built into Settings and Device Manager |
| 3. Windows Memory Diagnostic | You suspect faulty RAM | Runs during a restart; Extended test is more thorough |
| 4. DISM and SFC | System files are corrupted | Needs an administrator Command Prompt |
| 5. chkdsk | Disk or page file read errors | Back up first; runs at the next restart |
| 6. Default memory speeds | XMP, EXPO or an overclock is on | Changed in BIOS or UEFI setup |
| 7. MemTest86 and reseat or replace RAM | The memory tests report errors | Unplug the PC before you touch the RAM |
Fix 1: Undo recent hardware and software changes
If the crashes started after you added hardware or installed something new, that change is the first suspect.
- Shut down the PC and remove any hardware you added just before the errors started, such as a new RAM module or USB device.
- Start the PC and see if the error returns.
- If you can’t get to the desktop, start Windows in safe mode and continue from there.
Fix 2: Install Windows updates and driver updates
Microsoft recommends installing the latest updates and making sure drivers, BIOS and firmware are current.
- Windows 11: Select Start > Settings > Windows Update > Check for updates. Then go to Advanced options > Optional updates and install any driver updates.
- Windows 10: Select Start > Settings > Update & Security > Windows Update > Check for updates. If you see View optional updates, install those too.
Next, check Device Manager:
- Right-click Start and select Device Manager.
- Look for devices with a yellow exclamation mark.
- Right-click the device and select Update driver.
If Windows doesn’t find a newer driver, download one from your PC or motherboard manufacturer’s support page.
Fix 3: Run Windows Memory Diagnostic
This built-in tool tests your RAM during a restart (Windows 10 and 11).
- Save your work and close all apps.
- Press Windows key + R, type
mdschedand select OK. - Select Restart now and check for problems (recommended).
- The test starts automatically after the restart. For a more thorough test, press F1, change Test Mix from Standard to Extended, then press F10 to apply.
- When Windows starts again and you sign in, a notification shows the result. It can take a few minutes to appear.
To read the result later, open Event Viewer and go to Applications and Services Logs > Microsoft > Windows > MemoryDiagnostics-Results > Debug. Event ID 2001 means no memory errors were detected.
If the tool reports errors, skip to Fix 7.
Fix 4: Repair system files with DISM and SFC
Important: These commands need an administrator Command Prompt. Don’t close the window until the scan reaches 100%.
- Search for Command Prompt, right-click it and select Run as administrator. (See our guide to the elevated command prompt for other ways to open it.)
- Run DISM first:
DISM.exe /Online /Cleanup-image /Restorehealth
Microsoft says to run this before SFC. It can take several minutes.
- Then run System File Checker:
sfc /scannow
This scans protected system files and replaces corrupted ones. If it says it “found corrupt files and successfully repaired them,” restart the PC.
Fix 5: Check the disk for errors
Because the page file lives on your drive, disk errors can show up as memory errors.
Important: Back up your files first. A disk check that repairs bad sectors can take a long time, and a failing drive can lose data.
In the same administrator Command Prompt, run:
chkdsk /f /r
This detects and repairs disk errors. On the Windows drive the scan can’t run while Windows is using it, so it runs at the next restart. Type Y if you’re asked to schedule it, then restart.
Fix 6: Reset memory to default speeds
If you turned on XMP or EXPO, or overclocked your RAM or CPU, go back to stock settings.
- Enter your PC’s BIOS or UEFI setup. Our guide on how to get into BIOS on Windows 11 covers the common methods.
- Turn off the XMP or EXPO memory profile, or load the default settings.
- Save and exit.
If the blue screens stop, your RAM isn’t stable at the higher speed.
Tip: Microsoft also recommends updating the BIOS and firmware when you troubleshoot stop errors. Use the update tool from your PC or motherboard manufacturer.
Fix 7: Test with MemTest86, then reseat or replace the RAM
MemTest86 is a free memory tester that boots from a USB flash drive, so it doesn’t need Windows. It supports UEFI systems and memory from DDR2 to DDR5.
- Download the free edition from memtest86.com and create the bootable USB drive using its instructions.
- Boot from the USB drive and let the test run.
- If it reports errors, shut down the PC and unplug it.
If you’re comfortable opening the PC, you can find the bad module:
- Remove all memory modules except one.
- Test that one module in each memory slot, one slot at a time.
- Repeat for every module.
Dell recommends this one-module-per-slot method in its memory troubleshooting guide. If the errors follow one module no matter which slot it’s in, replace that module. If the errors follow a slot instead, the slot or motherboard may be at fault.
Important: Unplug the power cable (and on a laptop, disconnect the battery if your manual says to) before you touch the RAM. Follow your PC manufacturer’s service manual for your model.
When you buy replacement memory, match the type, speed and form factor your PC supports (desktop DIMM or laptop SO-DIMM, DDR4 or DDR5). Your manual or the manufacturer’s support page lists them. Then check replacement RAM prices on Amazon.
If it still doesn’t work
- Try a clean boot. Disabling third-party startup apps and services helps you find a driver or app that triggers the crash. If a crash names a specific driver file, update or remove that driver.
- Keep 10-15% of the drive free. Microsoft recommends this amount of free space when troubleshooting stop errors.
- Collect a memory dump. IT staff can analyze the dump file in WinDbg with the
!analyze -vcommand to find the faulting driver. - Use System Restore. If the crashes started after an update or driver change, restore to an earlier point.
- Get it checked. If MemTest86 and Windows Memory Diagnostic pass but crashes continue, a repair shop can test the motherboard and power supply. For other crash and hardware problems, see our computer repair tips, and if your PC is also sluggish, read why is my computer so slow. More crash and error guides are in our PC repairs section.
Frequently asked questions
What does the MEMORY_MANAGEMENT stop code mean?
It is bug check 0x1A. Microsoft describes it as a severe memory management error. Many of its sub-codes point to hardware, but faulty drivers can also cause it.
Is a memory management blue screen always bad RAM?
No. Faulty RAM is a common cause, but drivers, corrupted system files, disk errors and memory overclocking (XMP or EXPO profiles) can trigger the same stop code.
How do I see the Windows Memory Diagnostic results?
A notification shows the result after you sign in. You can also open Event Viewer, go to Applications and Services Logs > Microsoft > Windows > MemoryDiagnostics-Results > Debug, and look for Event ID 2001, which means no errors were found.
Can I keep using my PC if it shows this error?
Back up your important files as soon as possible. Repeated memory errors can corrupt data, so test the RAM and disk before you rely on the PC for important work.
Related guides

PC Repairs
Computer Repair Tips for Beginners: Fix Common PC Problems Safely
Back up first, diagnose before you fix, and work safely. These beginner computer repair tips cover slow PCs, crashes, overheating, no sound, Wi-Fi and PCs that won't start.
7 min read

PC Repairs
Windows Host Process (Rundll32) Has Stopped Working: How to Fix It
Rundll32 crashes when a DLL it loads fails. Find the faulting DLL in Event Viewer, then repair system files, update drivers or remove the program that owns it.
7 min read

PC Repairs
Why Is My Computer So Slow? How to Find the Cause and Fix It
A slow PC almost always comes down to startup apps, a busy disk, low memory, a full drive, malware or an old hard drive. Here's how to find which one and fix it.
8 min read

PC Repairs
Windows Update Error 0x80070005 (Access Denied): How to Fix It
Error 0x80070005 means Windows Update was denied access to files or settings it needs. Check admin rights first, then reset the update components.
5 min read