How to Test RAM Health with MemTest86 and Windows Memory Diagnostic
Your PC crashes at random times, with a different blue screen code every day? Before you blame Windows, test the RAM. Two free tools give a clear verdict — here is the full method, in the right order.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ Test runs 1 to 4 hours
🎥 Full RAM test method in the video — MemTest86 and the Windows test, step by step
RAM faults are the great imitators. A dying memory stick can look like a corrupt Windows, a failing drive or a bad driver, because every program keeps its working data in RAM. Guessing wastes days. A memory test replaces guessing with a verdict. This guide runs both trusted tools — MemTest86, the deep test that boots from USB, and the Windows Memory Diagnostic built into Windows — and tells you exactly how to read the result. The honest rule that governs everything below: even one error means the memory setup has failed the test. There is no safe number of errors.
MemTest86 — Test screen (example)
MemTest86 v11 — Pass 2 of 4 Test 7 of 13 [Moving inversions]
RAM: 16.0 GB Tested: 16384M Errors: 0
Lowest error address: — Highest error address: —
Errors so far0 HEALTHY SO FAR
Elapsed time1 hr 12 min
A MemTest86 run in progress. Example values — a healthy run ends with zero errors after all passes.
1
Know the Symptoms That Point at RAM
Suspect memory first when the failures are random and change their shape:
Blue screens with a different stop code each time — MEMORY_MANAGEMENT one day, something unrelated the next
Programs crashing or files corrupting with no pattern
Crashes that began after adding or changing RAM, or after enabling XMP
The PC sometimes refusing to start, or starting only after several tries
One honest warning: these symptoms accuse RAM, they do not convict it. The power supply, heat and a failing drive can imitate them — which is exactly why we test instead of buying parts.
2
Prepare Before You Test
Five minutes of preparation saves a wasted overnight run:
Save your work. The PC is unusable while a memory test runs
Enter the BIOS and note your settings, especially XMP or EXPO — take phone photos
For the first verdict run, disable XMP or EXPO and test at stock JEDEC speed. An overclocked profile can make good RAM fail, and that is a different problem with a different fix
Warm room, normal cooling — test the machine as it really lives, not with the side panel off and a table fan
Keep a pen ready. If errors appear, write down the test number and the failing address range
3
Method 1 — MemTest86 From a Bootable USB
MemTest86 by PassMark is the technician standard because it runs outside Windows — no driver or program can hide a faulty cell from it.
Download MemTest86 only from the official site, memtest86.com — the free edition is enough
The download includes a USB writing tool (imageUSB). Run it and write the image to a spare pen drive — this erases the pen drive completely
Restart the PC, open the boot menu (commonly F12, F8 or Esc — it varies by board) and choose the UEFI entry for the pen drive
The test starts by itself. The default run is 4 passes of 13 tests. On 16 GB this commonly takes one to three hours; bigger memory takes longer
Let it finish all passes. The summary screen gives the final word
4
Method 2 — Windows Memory Diagnostic with mdsched
No pen drive handy? Windows carries its own tester. It is shallower than MemTest86, but it is built in and quick to start.
Press Windows + R, type mdsched.exe and press Enter
Choose Restart now and check for problems
The PC restarts into a blue test screen. Press F1 there if you want the Extended test mix — it is slower and deeper than Standard
When it finishes, Windows boots normally. The result is written to Event Viewer, under Windows Logs → System, with the source MemoryDiagnostics-Results
Do not skip that last step. The on-screen result flashes past or never appears for many users, and the Event Viewer entry is the permanent record.
5
Read the Verdict and Act on It
The result is one of three:
Zero errors after the full run — the RAM, at these settings, is very likely healthy. If crashes continue, test the other suspects: drive health, temperatures, power supply, drivers
Any error at all — the memory setup has failed. Do not argue with the number. One stick at a time now: test each stick alone, then each slot, until the error follows a stick or stays with a slot
Errors only with XMP enabled, clean at stock — the sticks are probably fine; the profile, the board or the CPU memory controller cannot hold that speed. Lower the frequency a step or run stock
That isolation step — stick versus slot versus settings — is where a failed test becomes a buying decision instead of a guess.
🔴 One error is a fail. Memory either stores every bit correctly or it does not. A stick that produces even a handful of errors in one pass will corrupt files and crash programs in daily use — the only question is how often.
🎥 Watch the Full Video Guide
MemTest86 USB banana, dono test chalana aur result padhna — poora process live video me dekho.
Run the full default — 4 passes. A single pass can miss faults that only appear under later test patterns or as the memory warms up. If you are chasing a rare, stubborn crash, an overnight run of many hours is the thorough version.
MemTest86 or Windows Memory Diagnostic — which is better?
MemTest86 is the deeper and more trusted test, and it runs outside Windows, so nothing can hide a fault from it. The Windows tool is a reasonable first check when you have no pen drive. If the Windows test passes but the symptoms scream RAM, still run MemTest86 before clearing the memory.
Can a memory test damage my PC or data?
No. Both tools only write patterns into RAM and read them back; RAM forgets everything at power off anyway. Your files on the disk are never touched. The only cost is time — the PC cannot be used while the test runs.
This guide is based on the Technical Anshu RAM testing video linked above • Stuck on a step, ask in the video comments 🙏