MEMORY_MANAGEMENT Blue Screen
Usually points to RAM, a driver conflict, or disk corruption.
Before you start: save any open work and note down what you were doing when the problem started — that context helps if you need to search further or ask for help.
- Run Windows Memory Diagnostic (search for it in the Start menu) and let it do the extended test overnight if possible.
- If you've recently added RAM, try removing it and running on the original sticks to isolate whether the new memory is faulty or incompatible.
- Update your storage/chipset drivers from your PC or motherboard manufacturer's site — outdated ones are a common trigger.
- Run "chkdsk /f" from an admin Command Prompt and restart to let it scan the drive for errors.
- If crashes continue after all of the above, it's worth testing each RAM stick individually in different slots to isolate a specific bad module.
Still not fixed? Send us the details and we'll help you dig further, or browse related guides in Blue Screen of Death (BSOD).
Frequently Asked Questions
Does this mean my RAM is physically failing?
Not necessarily — despite the name, this stop code is often caused by a driver issue rather than actual failing memory hardware. Running Windows Memory Diagnostic is the way to confirm whether the RAM itself is the problem.
How long does Windows Memory Diagnostic take?
The standard test usually takes 10-20 minutes, though it varies with how much RAM you have. The PC will restart automatically once it's done and show you the results.
Related guides
How to Read and Respond to Any Blue Screen
A general framework for any stop code you don't recognize.
IRQL_NOT_LESS_OR_EQUAL Blue Screen
Almost always a driver issue — most often network, audio, or graphics.
CRITICAL_PROCESS_DIED Blue Screen
A core Windows process crashed — often tied to a recent update or corrupted system file.