Random blue screens, games crashing to desktop, files that corrupt for no reason, unstable memory is a prime suspect and one of the hardest faults to pin down while Windows is running. MemTest86 solves that by testing your RAM outside the operating system, hammering every address until errors surface. A clean pass buys real peace of mind; a single error explains a lot of misery.
Why Test Outside Windows?
While Windows runs, it is constantly using RAM, so it can never test the regions it occupies. MemTest86 boots from a USB stick before any OS loads, giving it full access to every memory cell. That is why it catches faults Windows Memory Diagnostic and in-OS tools miss.
Creating the Test USB
1. Download and Image a USB Stick
Grab the free MemTest86 from its official site and use the included imaging tool (or Rufus) to write it to any 1GB+ USB drive. This erases the stick, so use a spare.
2. Boot From USB
Restart, tap the boot-menu key (often F12, F11, or Esc), and select the USB drive. On newer systems you may need to disable Secure Boot temporarily. MemTest86 launches straight into its own environment.
Running the Test Properly
Let it run the full default suite, which is four passes through thirteen algorithms. This is not quick: figure roughly 20-30 minutes per 8GB, so a 32GB kit can take two hours or more. The most reliable approach is to start it and leave it overnight, because intermittent errors sometimes only appear after several passes.
| RAM Amount | Approx. Time (1 pass) | Recommended Passes |
|---|---|---|
| 16GB | ~40-60 min | 4+ (overnight) |
| 32GB | ~90-120 min | 4+ (overnight) |
| 64GB | ~3-4 hours | 4+ (overnight) |
Reading the Results
The screen tracks errors in red as they occur. Zero errors after four full passes is a strong sign the memory is stable. Any error, even one, means something is wrong: a bad module, an unstable XMP/EXPO overclock, or a marginal memory controller.
Isolating Which Stick Failed
If errors appear, retest one stick at a time in the same slot to find the faulty module. Then test the good stick in each slot to rule out a bad slot. This tells you whether to RMA a stick or reconsider your overclock.
Errors Only With XMP Enabled?
If MemTest passes at default JEDEC speed but fails with XMP/EXPO on, the memory itself is likely fine, the profile is just too aggressive for your CPU’s memory controller. Drop to a lower speed, loosen timings, or bump the profile down a tier. That is tuning, not a hardware defect.
Frequently Asked Questions
Is Windows Memory Diagnostic good enough?
It is a quick first check but far less thorough than MemTest86. It runs fewer test patterns and cannot test memory Windows reserves. Use it for a fast screen, but trust MemTest86 for a real verdict.
How many errors are acceptable?
Zero. Memory is meant to be perfectly reliable; even a single confirmed error means data can silently corrupt. Treat any error as a fault to fix, whether by RMA or by backing off an overclock.
What to Do When Errors Appear
Finding errors is progress, not disaster, it tells you exactly where to look. First, note whether you were running an XMP/EXPO profile. If so, disable it, set memory to the JEDEC default, and retest; passing at default confirms the overclock, not the hardware, was unstable. If errors persist at stock speed, isolate the faulty stick by testing each individually, then contact the vendor for a warranty replacement, as quality memory typically carries a limited lifetime warranty.
When to Suspect the Memory Controller
If every stick fails individually in the primary slot but the same sticks pass in another machine, the fault may lie with your CPU’s integrated memory controller or the motherboard slot rather than the RAM. This is rarer but real, especially after an aggressive overclock. Resetting the BIOS to defaults and updating to the latest firmware resolves many controller-related instabilities before you conclude the CPU is at fault.
Bottom Line
When crashes defy explanation, test the RAM. Image a USB stick with MemTest86, boot from it, and run at least four full passes, ideally overnight. Zero errors clears memory as the cause; any error sends you to isolate the stick or back off an unstable XMP profile. It is the definitive way to trust your memory.
