MEMORY_MANAGEMENT blue screen (0x0000001A): causes and fixes

Published Sources checked By helps.wiki editorial team

The MEMORY_MANAGEMENT stop code (bug check 0x0000001A) means the Windows memory manager found a serious inconsistency in its own data. Microsoft's documentation ties it either to hardware errors (RAM is the prime suspect) or to a driver that corrupts memory. Start with Windows Memory Diagnostic, then read the crash dump to see which side you are on.

Applies to:Windows 10Windows 11
On this page

What it means

A blue screen is never pleasant, but this one has a fairly narrow set of suspects. MEMORY_MANAGEMENT (bug check 0x0000001A) is raised when the memory manager in the Windows kernel finds that its own bookkeeping no longer adds up. The damaged items can be page tables, page frame records, working set lists, pool addresses or memory descriptor lists.

The stop code alone does not say what went wrong. Microsoft's reference documents a first parameter that identifies which check failed. Some values are described as probable hardware errors, while others are plain driver bugs. So the right fix depends on which side you are on: bad or unstable RAM, or software writing to memory it should not touch.

Microsoft's detailed page is written for programmers and gives only one consumer-level step, running Windows Memory Diagnostic. The order below goes from quick and safe checks to the more involved ones. The BIOS reset, testing RAM sticks one at a time and the disk check are general techniques that are not listed on Microsoft's page for this code, so treat them as reasonable things to try rather than guaranteed fixes. Microsoft also has a general page for consumers, Troubleshoot blue screen errors, but it could not be opened while preparing this article, so nothing here is taken from it.

Symptoms and causes

You are likely dealing with this problem if:

  • A blue screen showing "MEMORY_MANAGEMENT" or "Your PC ran into a problem", followed by an automatic restart.
  • Crashes that seem random, appear under heavy load, or happen during or after a Windows update or upgrade.

The usual causes, most common first:

Faulty or unstable RAM
A failing module, a badly seated stick, or an unstable XMP or overclock setting. Microsoft lists several subcodes as probable hardware errors, for example a page table and page frame mismatch where two values differ by a single bit.
A buggy kernel-mode driver
Microsoft lists subcodes where a driver mapped memory that was not locked, freed an invalid pool address, or wrote to an unallocated address. These are driver bugs, not hardware faults.
A failed disk read
One documented subcode (0x3f) is an inpage operation that failed with a CRC error, which points at reading data back from disk.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Undo recent changes and reset BIOS defaults

Easy

An overclock or XMP profile that is slightly too aggressive can corrupt memory at random. Removing the most recent change also tells you whether it was the trigger. This is a general measure, not a step from Microsoft's page.

  1. Think back to what changed before the first crash: a new driver, a Windows update, new RAM, or an overclock.
  2. Enter your BIOS/UEFI setup, turn off any overclock or XMP/memory profile, or load the default settings, then save and restart.
  3. Use the PC normally for a while and see whether the blue screen returns.

2.Run Windows Memory Diagnostic

Easy

This is the one step Microsoft's own documentation gives for this stop code. It checks RAM for errors.

  1. Save your work, then press WinR, type the command below and press Enter.
    Command Prompt
    mdsched.exe
  2. Choose Restart now and check for problems. The PC restarts and runs the test before Windows loads.
  3. After Windows starts again, open Event Viewer and look under Windows Logs > System for the memory diagnostic result.
  4. If any error was reported, the RAM is the likely cause. Go to the next solution to find out which stick, then replace it.

3.Test RAM sticks one at a time

ModerateChanges settings

If you have more than one stick, this separates a bad module or slot from a healthy one. It is a general technique rather than a step from Microsoft's page.

Before you start: Shut the PC down and unplug it before touching the memory. Touch bare metal on the case first to discharge static. On a laptop, only do this if the RAM is user-accessible.

  1. Power off, unplug, and remove all RAM sticks except one.
  2. Boot and use the PC, or run Windows Memory Diagnostic again. Then repeat with each stick in turn, and try a different slot.
  3. If the crash or error follows one stick, replace that stick. If it follows one slot, avoid that slot.

4.Check the system drive for errors with CHKDSK

ModerateChanges settings

One documented subcode (0x3f) is a disk inpage operation that failed with a CRC error. CHKDSK checks a volume for logical and physical errors, and with /f it fixes them.

Before you start: Back up important files before running a disk repair. Microsoft says interrupting CHKDSK is not recommended, so let it finish, and on a large drive it can take a long time. If the drive itself is failing, back up first and expect to replace it.

  1. Open Command Prompt as administrator and run the command below. Windows cannot lock the system drive while it is in use, so it asks whether to check it the next time the system restarts. Answer Y and restart.
    Command Promptrun as administrator
    chkdsk C: /f
  2. Leave the PC alone while the check runs. Per Microsoft's documentation, on a boot partition CHKDSK restarts the computer by itself when it finishes.
  3. To read the result afterwards, open Event Viewer, expand Windows Logs, right-click Application, choose Filter Current Log and select the Chkdsk and Wininit event sources.

5.Read the minidump to see which subcode failed

Advanced

Parameter 1 tells you whether the crash looks like hardware or a driver bug, which saves guessing. Microsoft's table maps each value to a meaning.

  1. Install WinDbg from Microsoft and open the latest dump file from C:\Windows\Minidump.
  2. Run the analysis command.
    Text
    !analyze -v
  3. Compare Parameter 1 with the table on Microsoft's Bug Check 0x1A page. Values such as 0x403 or 0x31 are described as probably hardware. Values such as 0x1233, 0x1236, 0x1240, 0x5305, 0x41286 and 0x4477 point to a driver, so look at the driver named in the analysis and get a newer version from the PC or component maker.

6.Last resort for advanced users: Driver Verifier

AdvancedBack up first

When crashes repeat and the cause stays unclear, Driver Verifier stresses drivers so a faulty one fails with a clear blue screen. Microsoft recommends running it only on test or debugging computers, so skip this on a PC you depend on unless everything above has failed.

Before you start: Microsoft warns that Driver Verifier could cause the computer to crash and recommends using it only on test or debugging computers. On a daily-use PC it can leave you in a crash loop. Back up your data and create a restore point first, and know your way out before you start: boot to Safe Mode and run verifier /reset. If Windows will not start at all, System Restore or a recovery drive is your fallback. Driver Verifier is not included in Windows 10 S.

  1. Open an elevated prompt and start the tool.
    Command Promptrun as administrator
    verifier
  2. Choose Create standard settings, then pick drivers from a list (or another selection option) and restart.
  3. If a violation occurs, it usually shows as bug check 0xC4 or a related code (0xC1, 0xC6, 0xC9, 0xD6, 0xE6). Note the driver named on screen.
  4. When finished, turn Verifier off and restart. If the PC is stuck in a crash loop, boot to Safe Mode first and run this there.
    Command Promptrun as administrator
    verifier /reset

7.Replace faulty RAM or reinstall Windows

AdvancedBack up first

If a RAM test fails, the module needs replacing. Reinstalling Windows is a general last resort for software damage, not a step from Microsoft's page for this code.

Before you start: Resetting or reinstalling Windows can remove apps and, depending on the option, files. Back up everything important first.

  1. Replace any RAM stick that failed a test.
  2. If crashes continue with passing RAM and you have exhausted the steps above, back up your data and use the Reset this PC option in Windows recovery settings.

Check that it worked

  • The PC runs under your normal workload for several days without a MEMORY_MANAGEMENT blue screen.
  • Windows Memory Diagnostic finishes with no errors reported in Event Viewer.
  • If you used Driver Verifier, verifier /reset has been run and the PC restarted.

If it still fails

  • Note Parameter 1 from the crash dump and compare it with Microsoft's table to decide between a hardware and a driver cause.
  • Test sticks individually and in different slots, as described above.
  • Contact the PC or motherboard manufacturer's support, especially if the machine is under warranty.
  • Related but different stop codes include PAGE_FAULT_IN_NONPAGED_AREA (0x50) and BAD_POOL_CALLER (0xC2). If your screen shows one of those, it is a different problem.

Questions

Does this stop code always mean bad RAM?

No. Microsoft lists some subcodes as probable hardware errors and others as driver bugs, so RAM is a prime suspect but not the only one.

Sources

  1. Bug Check 0x1A MEMORY_MANAGEMENTOfficial · Microsoft Learn
  2. How to Use Driver Verifier for Driver TestingOfficial · Microsoft Learn
  3. chkdskOfficial · Microsoft Learn

Browse