Photo by Alexey Demidov on Unsplash

It's midnight. You're in the middle of something. Your screen goes blue. MEMORY_MANAGEMENT. Your PC reboots itself like nothing happened and you're just sitting there wondering what the hell just occurred. I've been there more times than I want to admit, both on my own machines and on other people's machines that I get roped into fixing.

The frustrating thing about this particular BSOD is that it sounds catastrophic. Memory management. Like something fundamental is broken. And sometimes it is. But honestly, most of the time it's a driver that's misbehaving, a RAM stick that's starting to flake out, or Windows itself having a bad day. The error is vague by design, which makes diagnosing it feel like guesswork. It doesn't have to be.

Here's what the full stop error actually looks like when it hits you.

Your PC ran into a problem and needs to restart.
We're just collecting some error info, and then we'll restart for you.

Stop code: MEMORY_MANAGEMENT

Sometimes you also see it paired with a specific stop code like 0x0000001A in the event logs. Either way, same problem, same fixes.

Why This Error Happens

Windows throws the MEMORY_MANAGEMENT stop code when it detects something has gone wrong with how RAM is being read or written. That's the textbook answer. The real answer is that it's a catch-all for several different root causes, and figuring out which one is affecting you is half the battle.

The most common culprits I've seen are bad or failing RAM, corrupted Windows system files, outdated or broken drivers (especially GPU drivers — these are guilty more often than people think), and sometimes even a recently installed Windows Update that shipped with a bug. I've also seen it triggered by antivirus software doing aggressive memory scanning at the wrong time.

If your crashes started after you added new RAM, swapped out your GPU, or installed a specific update, that's your lead. Start there.

Photo by Stefano Intintoli on Unsplash

Fix 1: Run Windows Memory Diagnostic

This is always my first move. Windows has a built-in memory tester and it's actually decent for catching obvious hardware failures. It won't catch every bad stick — for that you'd want MemTest86 running overnight — but it catches enough to be worth doing first.

Press Win + R, type this, hit Enter:

mdsched.exe

Choose "Restart now and check for problems." Your machine will reboot into the diagnostic tool and run two passes by default. When it finishes and Windows loads back up, search for Event Viewer, go to Windows Logs > System, and look for an event from "MemoryDiagnostics-Results." It'll tell you if it found anything.

If it does find errors, you've got bad RAM. Pull your sticks and test them one at a time to figure out which one. If you've got two sticks, try running with just one and see if the crashes stop. Swap them out. This is tedious but there's no shortcut here.

Photo by BoliviaInteligente on Unsplash

Fix 2: Repair Corrupted System Files with SFC and DISM

Corrupted system files are a surprisingly common cause of this BSOD, especially after a Windows Update goes sideways or your machine shut down hard mid-operation. Windows has tools to fix this and you should run both, in order.

Open Command Prompt as administrator and run this first:

DISM /Online /Cleanup-Image /RestoreHealth

Let that finish. It connects to Windows Update to pull down fresh copies of corrupted files, so it needs internet access and it takes a while. Don't cancel it. After that completes, run:

sfc /scannow

This one scans protected system files and replaces anything broken. If SFC finds and fixes something, reboot and see if the crashes stop. If it says it found errors but couldn't fix them, run DISM again, then SFC again. That one-two combo usually clears it.

Photo by Kajetan Sumila on Unsplash

Fix 3: Roll Back or Update Your GPU Driver

I can't tell you how many times a GPU driver has been the cause of a memory management BSOD. This is especially true on Windows 11 right now — driver compatibility has been rough and certain Nvidia and AMD driver versions have known issues that cause exactly this stop code.

If you updated your GPU driver recently and the crashes started around the same time, roll it back. Go to Device Manager, expand Display Adapters, right-click your GPU, Properties, Driver tab, Roll Back Driver. If that option is greyed out, you'll need to do a clean uninstall.

Download DDU — Display Driver Uninstaller — boot into Safe Mode, and run it. It strips every trace of the current driver out. Then install a known stable version directly from Nvidia or AMD's website. Not the most recent one necessarily. Look at the release notes and avoid anything that has reports of BSODs attached to it.

# Boot into Safe Mode via Settings:
Settings > System > Recovery > Advanced Startup > Restart Now
Then: Troubleshoot > Advanced Options > Startup Settings > Restart > F4

Fallback: Check Your Event Viewer Before Giving Up

Before you consider reinstalling Windows — and look, sometimes that's the answer, but it should be the last one — spend 10 minutes in Event Viewer. Go to Windows Logs > System, filter for Critical and Error events, and look at the timestamps around when your crashes happened. You'll often see a specific driver or service named right before the crash event. That name is your target.

Also check C:\Windows\Minidump — if there are .dmp files in there, you can open them with WinDbg or upload them to an online crash dump analyzer. They'll usually point you at a specific driver file. Something like nvlddmkm.sys means Nvidia GPU driver. ntoskrnl.exe by itself often means RAM. These aren't guarantees, but they narrow it down fast.

The MEMORY_MANAGEMENT BSOD is annoying precisely because it sounds worse than it usually is. Nine times out of ten, you're not replacing your whole machine. You're rolling back a driver, running a scan, or reseating a RAM stick. Work through these fixes methodically and you'll get there. And if you genuinely find a bad RAM stick — honestly, just replace it. Don't try to nurse it along. That's a crash that'll keep coming back.