You got a blue screen, it said MEMORY_MANAGEMENT, and every result you clicked told you to buy new memory. Before you spend anything, hold on.
Microsoft documents thirty six separate causes for that stop code. Exactly two of them mention hardware.
I read the whole table, then read the crash history on this machine. The two crashes here were not this code at all, and finding that out took one command.
What the stop code is actually telling you
The name is doing a lot of damage.
⛔ MEMORY_MANAGEMENT does not mean your memory chips failed. It means the part of Windows that manages memory hit something it could not accept.
⚡ Documented by Microsoft on its bug check 0x1A page: "The bug check indicates that a severe memory management error occurred."
⭐ A corrupt driver can cause that. So can a bad page in a file. So can genuinely faulty RAM. The name does not choose between them.
The number nobody reads
This is the part that changes what you do next.
Microsoft states, in one short line: "Parameter 1 identifies the exact violation."
⚡ Your blue screen has more than a name. Under it, or in the crash log, there is a first parameter, and that number is the actual diagnosis.
⭐ Two machines can both say MEMORY_MANAGEMENT and have nothing in common. One is a driver bug. The other is a failing stick.
⚠️ Microsoft says so itself on that page: it is written for programmers, and readers like you are pointed at the general blue screen guide instead.
Only two of thirty six point at hardware
I counted them, because the ratio is the whole story.
⛔ Ours, counted off Microsoft's own table. Thirty six parameter values are documented for current Windows. Two of them say the fault is probably hardware.
⚡ Documented by Microsoft, parameter 0x31: "The image relocation fix-up table or code stream has been corrupted. The error probably is a hardware error."
⚡ And parameter 0x403: "The page table and page frame numbers (PFNs) are out of sync. The error probably is a hardware error, especially if parameters 3 and 4 differ by only one bit."
⭐ Everything else on your list is software. Corrupted page tables, drivers mapping memory they never locked, pool addresses freed twice, working set lists in a mess.
⚠️ So buying RAM first is a one in eighteen bet. That is what the table says.
Ours: what the crash history here looks like
A measurement, and the command behind it is the one to run first.
Ours, straight off the System log here. Two bug checks are recorded: 0x19C on 9 June 2026 and 0x133 on 28 April 2026.
⛔ Neither of them was 0x1A. So this page cannot show you a MEMORY_MANAGEMENT crash reproduced here, and it does not pretend to.
⚡ Yours is one command away. Paste this into Terminal:
wevtutil qe System /q:"*[System[(EventID=1001)]]" /f:text /c:5 /rd:true⭐ Every bug check the log still holds comes back with its code and its parameters. That is the number you actually needed.
The dump files outlive the log
Worth knowing, because the log throws things away.
Ours, and the gap is real. There are three minidump files in the Windows folder here, dated 9 June 2026, 28 April 2026 and 15 October 2025.
⚠️ The event log only remembers two of those three. The October one has aged out of the log while its dump is still sitting on disk.
⭐ Look in `C:\Windows\Minidump` yourself. If there are files in there, your PC has blue screened, whatever the log says.
⚡ Ours: the dump setting on this machine is small memory dump, which is the one that writes those small files rather than a copy of all your memory.
A sudden restart is not a blue screen
The two get mixed up constantly, and the difference matters.
Ours, from the same log. This machine records fifteen unexpected shutdowns and only two blue screens.
⛔ Thirteen of those fifteen left no crash at all. Power, heat, or a hard power-off by hand. Nothing for a stop code to explain.
⚡ So if your PC restarts with no blue screen and no minidump, this page is not your page. You are chasing a crash that never happened.
⭐ A blue screen leaves evidence. A power event does not.
What to do, in order
Shortest first, and none of these costs money.
⭐ Get the parameter. Everything below depends on which of Microsoft's thirty six causes you actually have.
⚡ Then run the memory test, because it is free. Microsoft's own resolution note says you "might find it helpful to run the Windows Memory Diagnostic tool to check for problems that affect physical memory modules".
⚠️ Ours: it has never been run on this machine, and there is no result event in the log to show for it. Almost nobody has run it.
⛔ Then look at what changed. A driver installed or updated in the days before the first crash is the commonest software cause, and rolling one back is free.
⭐ Only then buy memory. And check first whether your laptop can even take any, because plenty cannot.
When it really is the RAM
Three signs, and a high memory percentage is not one of them.
⚡ The same parameter every time, and it is 0x31 or 0x403. That is Microsoft's own hardware wording.
⚠️ The memory diagnostic reports errors. That is as close to proof as you get without swapping sticks.
⭐ Crashes that follow the heat rather than the app. Fine cold, blue screens after an hour, every time.
⛔ And what is not a sign: memory sitting at 80 percent in Task Manager. That number is Windows caching and it worries people for nothing.
Status: read against Microsoft's bug check 0x1A documentation, 26 August 2026, on Windows 11. The thirty six to two count is ours, off Microsoft's own table. ⛔ No 0x1A crash occurred here.
What causes the MEMORY_MANAGEMENT stop code?
Thirty six different things, according to Microsoft's own table, and only two of them are described as probably hardware. The rest are software: corrupted page tables, drivers handling memory wrongly, pool addresses freed twice. The first parameter on your blue screen says which one you have.
Do I need new RAM if I get MEMORY_MANAGEMENT?
Probably not, and you should not buy any until you have the parameter and a memory test result. Run the Windows Memory Diagnostic first, and it is free. If it comes back clean and your parameter is not 0x31 or 0x403, your memory is very likely fine.
Where do I find the parameter after the PC restarts?
In the System event log, under event ID 1001, or inside the minidump file. The one-line command above prints the last five bug checks with their codes and parameters. Your minidump folder is also worth opening, because it keeps crashes the log has already forgotten.
My PC restarts with no blue screen. Is that the same thing?
No, and this is worth separating before you spend an evening on it. A blue screen writes a bug check event and usually a dump file. A plain restart writes neither. On the machine tested here there were fifteen unexpected shutdowns and only two actual blue screens.
The Short Version
- MEMORY_MANAGEMENT names a part of Windows, not your memory chips.
- Microsoft documents thirty six causes and only two mention hardware.
- The first parameter on your blue screen is the real diagnosis. Read it.
- Get it from event 1001 in the System log, or from your minidump file.
- Your minidump folder keeps crashes the event log has already dropped.
- Run the Windows Memory Diagnostic before buying anything. It is free.
- An unexpected restart with no dump file is not a blue screen at all.
- High memory usage in Task Manager has nothing to do with this code.
Where to Next
Run the one line above and read the parameter off your own crash. Thirty seconds, and it tells you whether this is a driver or a stick of RAM.
Then open your minidump folder. If there are files there you did not know about, your PC has been crashing longer than you thought.
Run the memory test next, because it is free and it either clears your RAM or condemns it. Mine has never been run, and I suspect yours has not either.
If you got a different stop code entirely, start with the general list instead. Reading the code on the screen is the first move for any of them.
If your parameter turned out to be one I have not seen, put it in the comments. That table is long and the interesting ones are rare.
Isaac Smith is the founder and editor of PC Glance, a website that covers computers, laptops, and technology. He is a tech enthusiast and a computer geek who loves to share his insights and help his readers make smart choices when buying tech gadgets or laptops. He is always curious and updated about the latest tech trends.