MEMORY_MANAGEMENT blue screen in Windows 11: how to fix it

Applies to: Windows 11 (and Windows 10) PCs that restart with the MEMORY_MANAGEMENT stop code, whether during games, while idle, or right after new RAM, a driver or a Windows update. If you only saw a sad face and a QR code, our guide on finding the stop code after a crash shows where Windows records it. This guide is about a full system crash. A program that closes with a message about memory that “could not be read”, or a process using too much RAM, is a different problem.

What MEMORY_MANAGEMENT means

Windows keeps detailed bookkeeping about memory: which physical pages of RAM are in use, which belong to which program, and which have been moved out to the page file on disk. The memory manager checks that bookkeeping as it works. When something doesn’t add up, such as a table that points to the wrong page or a page whose contents changed when they shouldn’t have, carrying on could corrupt files, so Windows halts.

Microsoft’s bug check 0x1A reference describes it in one line: “a severe memory management error occurred.” It doesn’t name a single cause. Instead, the first number recorded with the crash (parameter 1) says which check failed. A few examples from Microsoft’s table:

Parameter 1	What Microsoft says it means	Points toward
0x41790	A page table page has been corrupted	RAM, or a driver writing where it shouldn’t
0x403	Page table and page frame numbers are out of sync; “probably a hardware error, especially if parameters 3 and 4 differ by only one bit”	RAM
0x5003	The working set free list is corrupted; “probably a hardware error”	RAM
0x31	Relocation data or code has been corrupted; “probably is a hardware error”	RAM or storage
0x3F	Reading a page back from the page file failed a CRC (integrity) check	Drive, cable or page file
0x1233, 0x4477	A driver mapped memory it hadn’t locked, or wrote to an unallocated address	A driver

The pattern is clear even without a debugger: most entries point at the hardware that holds memory, either the RAM itself or the drive behind the page file, and a smaller group points at a driver. That’s why this guide tests RAM earlier than a typical blue screen guide does. More broadly, Microsoft’s advanced stop code troubleshooting article estimates that about 70% of all stop errors come from third-party drivers and about 10% from hardware, so a driver stays on the list even when the hardware checks out.

Match your situation

What you see	Likely cause	Start with
Crashes began after adding or swapping RAM	Incompatible, faulty or badly seated module	Fix 2, Fix 3
Crashes under load or in games, with XMP/EXPO or an overclock on	Memory running beyond stable settings	Fix 2, Fix 3
Parameter 1 is 0x41790, 0x403 or 0x5003	RAM, by Microsoft’s description	Fix 3
Parameter 1 is 0x3F, or the drive is old or making noise	Drive, cable or page file	Fix 5, Fix 6
The dump names a .sys file, or crashes began after a driver update	That driver	Fix 1, Fix 4
Crashes began after a Windows update	A driver, security tool or the update itself	Fix 2, Fix 4, Known issues
Windows crashes before or right after sign-in	Hardware or a driver that loads at startup	The section below

If Windows crashes before you can sign in

If the PC can’t stay up long enough to work through the fixes, start in Safe Mode, which loads only basic drivers.

1. Get to the blue Choose an option screen. Windows normally shows it by itself after two failed starts; if you can reach the sign-in screen, holding Shift as you pick Power, then Restart, opens it too.
2. Go to Troubleshoot > Advanced options > Startup Settings and select Restart.
3. On the numbered list, 4 starts Safe Mode and 5 adds networking, which you need for driver downloads.

If the recovery screen never appears, our WinRE guide explains how to open recovery when Windows won’t start. Safe Mode doesn’t rule out faulty RAM, though. If it crashes there too, go straight to Fix 2 and Fix 3, which run outside Windows or in the firmware.

Fix 1: Read the crash details

A minute here tells you whether to suspect hardware or a driver first.

Event Viewer

Right-click Start, open Event Viewer and go to Windows Logs > System. After a blue screen, Windows usually logs an entry from source BugCheck when it starts again. Its text gives the stop code 0x0000001a followed by four values in brackets; the first is parameter 1. Compare it with the table above. If the value changes from crash to crash, or you also see other stop codes, unstable RAM is more likely than one bad driver.

The crash dump

Microsoft’s advanced troubleshooting article says small dumps are saved in %SystemRoot%\Minidump and larger ones in %SystemRoot%\MEMORY.DMP. The bug check page recommends the !analyze command in Microsoft’s WinDbg debugger to help identify the root cause. Our IRQL_NOT_LESS_OR_EQUAL guide explains how to find the driver behind a crash from the blue screen, Event Viewer and a minidump. If the output names a third-party .sys file, Fix 4 is your main fix. If it names only Windows files such as ntoskrnl.exe, treat RAM as the lead suspect.

Fix 2: Undo recent changes and memory overclocks

These steps are quick and easy to reverse.

1. If you recently added, swapped or moved RAM, shut down, unplug the PC and put the original configuration back. If that isn’t possible, check that each module is fully seated with both clips closed, and that the modules sit in the slots your motherboard manual recommends for that number of sticks.
2. Disconnect other hardware added shortly before the crashes began, such as a new graphics card, dock or USB adapter.
3. Remove tools installed around then that load their own driver or background service (lighting and fan utilities, hardware monitors, VPN clients, security suites) through Settings > Apps > Installed apps.

Turn off XMP, EXPO and overclocks

Memory profiles such as Intel XMP and AMD EXPO run RAM faster than its default speed. Many systems handle them fine, but a profile that’s slightly unstable on your board can corrupt the odd bit under load, which is exactly the kind of damage this stop code reports. The same goes for CPU or memory overclocks and undervolts.

Warning: if BitLocker or device encryption is on, a firmware change can make Windows ask for the recovery key at the next start. Find the key first (it’s normally stored in your Microsoft account) and note every setting you touch so you can put it back.

Open the BIOS/UEFI setup, turn off XMP or EXPO and any overclock, save and restart. Our WHEA guide shows how to open the firmware and switch these settings off. Use the PC normally for a few days. If the crashes stop, leave the profile off or try a lower memory speed. Mixing kits of different models or speeds also makes instability more likely, even if each kit works on its own.

Fix 3: Test the RAM

Microsoft’s bug check page suggests the Windows Memory Diagnostic tool “to check for problems that affect physical memory modules.” It’s built in and runs before Windows loads, so drivers can’t interfere. Save your work first, because it restarts the PC.

1. Press Windows + R, type mdsched and press Enter.
2. Choose Restart now and check for problems (recommended).
3. For a more thorough run, press F1 while the test is running, set Test Mix to Extended and press F10 to apply. It takes much longer, so leave it running.
4. The result appears as a notification once you’re back in Windows. Missed it? In Event Viewer, under Windows Logs > System, find the event from MemoryDiagnostics-Results.

If the test reports errors, find the bad module: shut down, leave one stick in, test, and repeat with each stick in turn. A module that fails in every slot needs replacing; one that fails only in a certain slot points to the slot or board. Before you buy a replacement, our guide on checking your RAM manufacturer shows how to read the module details in Windows.

A clean result doesn’t fully clear the RAM. Some faults only show up when the PC is warm or with XMP turned on. If crashes continue, Microsoft’s advanced article also suggests running relevant hardware tests; many PC makers include their own memory diagnostics in the firmware, and several free bootable testers run longer and deeper tests than the built-in tool.

Fix 4: Update or roll back drivers

If Fix 1 named a driver, start with that one. Otherwise, graphics, chipset and storage drivers are the most likely to touch memory directly. Which way you go depends on timing: crashes that began after a driver update call for a rollback, while old drivers on a freshly upgraded Windows call for an update.

1. Open Settings > Windows Update > Advanced options > Optional updates and install any driver updates offered, then restart.
2. If Windows Update has nothing new, get current graphics and chipset drivers from your PC maker’s support page, or from the graphics card and motherboard makers for a self-built PC.
3. To go back a version, open Device Manager from the Start right-click menu, open the device’s Properties and use Roll Back Driver on the Driver tab. A grayed-out button means Windows kept no older copy, so download an earlier release from the maker.

If the crashes started right after a monthly Windows update rather than a driver, you can remove it from Settings > Windows Update > Update history > Uninstall updates while you wait for a fix.

Fix 5: Repair Windows files and check the drive

Damaged system files or a failing drive can produce memory errors too, especially the page file read failures in the table above. Open Terminal (Admin) and run these one at a time:

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

Run DISM before SFC: it fixes the component store that SFC copies replacement files from. Our SFC and DISM guide explains what each result means. Then check the system drive for file system errors:

chkdsk C: /scan

The /scan option checks the drive online without a restart. If it reports problems it can’t fix while Windows is running, it tells you what to run next. On many PCs with an NVMe SSD, Windows 11 also shows drive health under Settings > System > Storage > Advanced storage settings > Disks and volumes; the drive maker’s own tool gives more detail. Back up your files first if the drive shows any sign of trouble.

Fix 6: Check the page file and free space

The page file is the disk space Windows uses to extend RAM and to save crash dumps. Microsoft’s introduction to page files explains that a system-managed page file grows automatically when memory demand rises, as long as there’s enough free disk space, and warns that running out of committed memory “can cause freezing, crashing, and other malfunctions.” A page file that was turned off or set very small by a tweaking tool is worth putting back to the default.

1. Press Windows + R, type sysdm.cpl and press Enter.
2. On the Advanced tab, under Performance, select Settings, then open the Advanced tab and select Change under Virtual memory.
3. Tick Automatically manage paging file size for all drives, select OK and restart.

Free space matters as well. Microsoft’s advanced article recommends keeping about 10 to 15 percent of the system drive free. If the drive is nearly full, clear space before testing again.

Fix 7: Update the BIOS and chipset drivers

Microsoft’s advanced troubleshooting article lists up-to-date BIOS and firmware among its first checks. Firmware updates often improve memory compatibility, especially for new RAM kits and newer processors. Check your PC or motherboard maker’s support page for a newer BIOS and chipset driver and read the release notes for memory fixes.

Warning: a failed BIOS update can leave a PC unable to start. Follow the maker’s instructions exactly, keep a laptop plugged in, don’t turn the PC off during the update, and suspend BitLocker first if the maker’s tool doesn’t do it for you.

A BIOS update often resets firmware settings to their defaults, which also turns XMP or EXPO off. Test for a few days before turning a memory profile back on.

Fix 8: System Restore or reset

System Restore

A restore point taken before the first crash lets Windows undo the drivers, updates and settings installed since then, while your documents stay put. Search Start for Create a restore point, select System Restore and pick a date before the trouble began. From recovery, the same tool sits under Troubleshoot > Advanced options > System Restore.

Reset this PC

Warning: both reset options remove your installed apps and third-party drivers, and Remove everything also erases personal files. Keep my files is the gentler choice, but back up before either one.

Go to Settings > System > Recovery > Reset PC. A reset clears out any third-party driver or software at fault. Because this stop code is so often hardware, though, try it only after the RAM tests in Fix 3.

When it’s the hardware

If MEMORY_MANAGEMENT keeps returning on a fresh reset, before you install any extra software, the cause is almost certainly hardware. The likely order is RAM first, then the drive, then the motherboard or power supply. Replace a module that fails testing, try known-good RAM if you can borrow some, and contact the PC maker if the PC is under warranty. Many makers ask you to run their own diagnostics first, so have the results ready.

Known issues

As of November 2026, Microsoft’s Windows 11, version 25H2 release health page lists no known issue that causes MEMORY_MANAGEMENT or other stop errors. If many PCs start crashing with it right after the same update, check that page, since Microsoft posts confirmed problems and workarounds there.

Related guides

• Your PC ran into a problem and needs to restart: how to fix it
• IRQL_NOT_LESS_OR_EQUAL blue screen in Windows 11: how to fix it
• WHEA_UNCORRECTABLE_ERROR (0x124): how to fix it on Windows 11/10
• KERNEL_SECURITY_CHECK_FAILURE: what it means and how to fix it
• BAD_POOL_CALLER on Windows 11/10: what it means and how to fix it
• How to run sfc /scannow in Windows 11 and 10 (and read the results)
• WinRE: what the Windows Recovery Environment is and how to open it
• How to check your RAM manufacturer in Windows 11 and 10 (without opening the PC)
• Fix the PAGE_FAULT_IN_NONPAGED_AREA (0x50) stop code

Official sources

• Microsoft: Bug check 0x1A MEMORY_MANAGEMENT
• Microsoft: Advanced troubleshooting for stop code errors
• Microsoft: Introduction to page files