Is Bad RAM Crashing My PC How Do I Test the Memory Properly
Blue screens with a different stop code every day. Restarts in the middle of nothing. Files and downloads that corrupt for no reason. Defective RAM imitates almost every other fault in a PC — which is why technicians do not guess at it. They boot MemTest86+ from a USB and let it give a straight yes-or-no answer.
✍️ Technical Anshu🖥️ Desktops + laptops⏱️ 1 pass ≈ 20–40 min for 16 GB
🎥 The toolkit USB carrying MemTest86+ and the WinPE environments is built step by step in the video
Suspect RAM when the crashes are random and inconsistent: stop codes like MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NONPAGED_AREA taking turns, programs closing without errors, or a PC that crashes under load but idles fine. One honest caution: drivers, a failing disk and overheating can produce similar chaos — the test exists to replace suspicion with evidence. Software memory tests running inside Windows cannot test the memory Windows itself is standing on, so the proper test boots from USB and owns the whole machine.
BLUE SCREEN — THE SYMPTOM THAT BRINGS PEOPLE HERE
:(
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
...and tomorrow the stop code is a different one. That inconsistency itself is a clue.
📷 What the problem looks like — changing stop codes on repeat crashes point investigators at the RAM first
1
Boot MemTest86+ From the Toolkit USB
Boot your Ventoy USB and open the boot menu as usual
Select the MemTest86+ entry — MediCat carries it in its collection, and the standalone MemTest86+ ISO can also simply be copied onto any Ventoy drive
On a modern UEFI PC, if a legacy entry fails to start, pick the entry again and let Ventoy use its normal mode; MemTest86+ current versions support UEFI booting
The test starts by itself — blue screen, columns of numbers, a progress line. No setup is needed for a standard run
2
Let It Run Full Passes — Zero Errors Is the Only Pass ⭐
A pass means the tool has written and verified patterns across every byte of RAM once — let at least one full pass complete
For a PC that crashes only sometimes, run 4 passes or overnight: marginal RAM often survives a short test and fails in hour three
Read the verdict the only way it can be read: Errors: 0 is healthy. Any error at all — even one — means the memory subsystem is faulty. Stable RAM does not produce "a few" errors
If errors appear, note roughly when (which pass) — then move to isolation in Fix 3
MEMTEST86+ — A FAILING TEST, AS IT APPEARS
MemTest86+ v7.x | RAM: 16 GB DDR4
Pass 23% Test 45% Test #7 [Moving inversions, 32-bit pattern]
Wall time: 0:18:42
Errors: 14 — failing addresses listed below
📷 What failure looks like — the moment the Errors counter leaves zero, the hunt is over and the isolation begins
MemTest86+ lives on the same toolkit USB as the WinPE repair environments — the full drive, with MediCat, Strelec and Gandalf alongside, is assembled on screen in the video above.
3
Find the Bad Stick — or the Bad Slot
Errors prove a memory problem, not which part. Isolate it methodically (power off, unplug, and touch a metal part of the case first — static is a real risk to RAM):
First, simply reseat the sticks: remove each one, blow dust from the slot, refit until both clips click. A surprising share of "bad RAM" is dirty contacts — retest before buying anything
Still errors? Test with one stick at a time, in the same slot. The stick that errors alone is the faulty one
If a known-good stick errors in one particular slot but not another, the fault is the slot/motherboard, not the RAM
On a laptop with soldered memory there is nothing to swap — errors mean a board-level repair or warranty claim
4
Act on the Result
Faulty stick identified: replace that stick, matching type and speed (DDR4/DDR5, MHz) to the remaining good one
After any replacement or reseat: run MemTest86+ again for at least one full pass to prove the fix before declaring victory
Zero errors over a long run: believe it — your RAM is very likely fine, and the crashes live elsewhere. Check disk health with CrystalDiskInfo and review drivers next, using the same toolkit USB
⚠️ Do not keep "living with" a PC that fails this test. Bad RAM does not only crash programs — it silently corrupts files as they are written through memory. Documents and photos can be damaged without any error message, which is a worse outcome than the blue screens.
🎥 Build the Diagnostic Toolkit in Video
One Ventoy USB with MemTest86+, MediCat, Strelec and Gandalf — built completely in the video, step by step.
At least one full pass — roughly 20 to 40 minutes for 16 GB. For a PC that crashes only occasionally, four passes or an overnight run is the honest test, because marginal RAM can pass a short run and fail hours later under the harder patterns.
The test found just one error in hours. Is that really a problem?
Yes. Healthy RAM runs indefinitely with an error count of exactly zero — there is no "acceptable" number above that. A single error means data was written or read incorrectly once, and it will happen again inside Windows, where it appears as a crash or a corrupted file.
Windows has its own Memory Diagnostic tool. Why use MemTest86+?
Windows Memory Diagnostic is a reasonable quick check, but it runs within limits and is less thorough. MemTest86+ boots on its own, tests the memory far more completely and with harsher patterns, and is the tool technicians standardize on — it is also already on your toolkit USB.
This guide is based on Technical Anshu's "One USB = All Tools" video • Stuck on a step? Ask in the video comments — you'll get help there 🙏