MEMORY_MANAGEMENT (0x1A): Causes and Fixes

MEMORY_MANAGEMENT (0x0000001A)

Stop code 0x0000001A, also written 0x1A. Here is what it means, what usually causes it, and the safest order to work through fixes on Windows 11 and Windows 10.

In short

Windows hit a severe memory-management error, most often from faulty RAM or unstable memory settings.

What MEMORY_MANAGEMENT means

This is a broad stop code for serious memory-management failures. Faulty RAM, memory settings the hardware cannot run reliably and driver bugs are the usual causes. Storage problems that affect the paging file can contribute as well.

Common causes

Faulty RAM, or sticks that are not seated correctly
An XMP or EXPO profile, or manual memory overclock, that is not stable
A driver corrupting memory
A failing drive holding the paging file

How to fix MEMORY_MANAGEMENT

Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.

Test the memory. Run Windows Memory Diagnostic (search for it in Start) for a quick check, then MemTest86 for several passes if the crashes continue. Any error points to a faulty stick or slot, or to memory settings the hardware cannot run reliably.
Turn off XMP or EXPO temporarily. Enter the BIOS and load default memory settings. If the crashes stop, the profile is not stable on your CPU and motherboard. Try a lower speed, or slightly more voltage only within the memory maker's rated range.
Reseat and test sticks one at a time. Power off, unplug the PC and reseat the RAM. Test one stick at a time in the slot your motherboard manual recommends to find a bad stick or slot.
Undo the most recent change. If the blue screens began after a Windows update, a new driver or new software, remove that change first. Uninstall the update from Settings, Windows Update, Update history, or roll a driver back in Device Manager (right-click the device, Properties, Driver, Roll Back Driver).
Check the health of the drive. Read the SMART data with the drive maker's tool or CrystalDiskInfo and look for reallocated or pending sectors, media errors and a low remaining-life figure. Back up important files first if the drive reports any warning.

When to stop and protect your data

Any error in a full MemTest86 run means the module or slot is at fault. Replace the module rather than relying on it.

Not sure this is your code?

The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.

Related guides

Other memory errors

PAGE_FAULT_IN_NONPAGED_AREA (0x50)
BAD_POOL_HEADER (0x19)

Frequently asked questions

What does MEMORY_MANAGEMENT mean?

Windows hit a severe memory-management error, most often from faulty RAM or unstable memory settings. This is a broad stop code for serious memory-management failures. Faulty RAM, memory settings the hardware cannot run reliably and driver bugs are the usual causes. Storage problems that affect the paging file can contribute as well.

What usually causes MEMORY_MANAGEMENT?

Typical causes: Faulty RAM, or sticks that are not seated correctly; An XMP or EXPO profile, or manual memory overclock, that is not stable; A driver corrupting memory; A failing drive holding the paging file.

How do I fix MEMORY_MANAGEMENT (0x0000001A)?

A sensible order is: 1) Test the memory; 2) Turn off XMP or EXPO temporarily; 3) Reseat and test sticks one at a time; 4) Undo the most recent change. Any error in a full MemTest86 run means the module or slot is at fault. Replace the module rather than relying on it.

Use this guidance carefully

A stop code can have several causes, and these steps are general guidance rather than a diagnosis of your PC. If your data matters, back it up before repairs. If the problem continues, a hardware technician can test the parts.

See our testing methodology·Read our editorial policy