Owen Bradley Random crashes, blue screens with different error codes each time, files that corrupt for no obvious reason, applications closing without warning: these symptoms look like a software mess, but they are the classic signature of failing memory. Memory faults are uniquely frustrating because they are intermittent. The machine works perfectly for hours, then falls over during something trivial. The only reliable way to settle the question is a proper test that writes and reads every address with patterns designed to provoke errors. This guide covers how to test RAM for errors using MemTest86 and the built-in Windows tool, how long to run it, and how to identify which single stick is at fault.
When Memory Testing Is Worth Your Time
Run a memory test if you recognise several of these:
- Blue screens with inconsistent error codes, particularly memory management or page fault errors.
- Applications closing silently or reporting corrupted data files.
- Crashes that occur under load but at unpredictable moments rather than in one specific program.
- File copies that produce a different checksum than the original.
- Instability that appeared immediately after enabling a memory speed profile, adding a new stick, or moving the PC.
- A newly built system that fails to boot reliably or posts intermittently.
By contrast, if one specific game crashes and nothing else ever does, memory is unlikely to be the cause. Faulty memory is indiscriminate; it takes down whatever happens to be using the bad address.
What You Need Before Testing
- A USB flash drive of at least 1GB that you can erase completely.
- The MemTest86 bootable image, downloaded from its official site. The free version is sufficient for diagnostics.
- Several hours of uninterrupted time. A meaningful test is not a five-minute job.
- A screwdriver, for the isolation stage where sticks are removed one at a time.
- A note of your current memory configuration: capacity, speed, number of sticks, and which slots are occupied.
Test from a bootable USB rather than inside the operating system wherever possible. Windows occupies memory addresses that a running test cannot examine, so an in-Windows test can only ever check part of the total.
Step-by-Step: Testing RAM With MemTest86
- Prepare the bootable drive. Download the MemTest86 package and run the included USB imaging tool, selecting your flash drive as the target. This erases the drive entirely, so move anything important off it first.
- Return memory to default settings. Enter the motherboard firmware and disable any memory overclocking profile, returning the sticks to their base speed. This separates a genuine hardware defect from an unstable overclock, which is a different problem with a different fix.
- Boot from the USB drive. Restart and use the boot menu key, usually F8, F11, or F12 depending on the board, to select the USB device. If it does not appear, disable Secure Boot temporarily in the firmware.
- Start the default test suite. MemTest86 begins automatically after a short countdown. It shows the detected memory size, speed, and the currently running test pattern along with a pass counter and an error count.
- Let it complete at least four full passes. A single pass catches only the most obvious faults. Four passes is the widely accepted minimum for confidence, and an overnight run of eight or more is better for intermittent problems. Expect roughly one to two hours per pass for a 32GB configuration.
- Watch for errors as they appear. Any error at all is a failure. The display lists the failing address, the expected value, and the value actually read. One error is as significant as ten thousand; healthy memory produces exactly zero.
- Record the results. Note the pass count, the error count, and the failing addresses if any. MemTest86 can also save a report to the USB drive, which is useful for a warranty claim.
- If errors appear, isolate the faulty stick. Power down, unplug, and remove all sticks but one. Test that single stick for at least two passes, then repeat with each stick in turn using the same slot every time. The stick that produces errors is the defective one.
- Rule out the slot itself. Once you have a suspect stick, test a known-good stick in the slot the failing one occupied. If the good stick also fails there, the problem is the motherboard slot or a bent CPU socket pin rather than the memory.
- Re-test the surviving configuration. After removing the faulty stick, run a further four passes on the remaining memory to confirm the system is now clean before drawing conclusions.
- Re-enable your speed profile and test again. If the memory passes at default speed, turn the profile back on and repeat the test. Errors that only appear with the profile enabled point to an unstable overclock rather than defective hardware.
- Claim the warranty if a stick failed. Memory is almost always sold with a long or lifetime warranty. Contact the manufacturer with the saved report and the serial number printed on the stick’s label.
Using the Windows Memory Diagnostic
Windows includes a basic memory tester that is worth running when you want a quick first look without preparing a USB drive. Search for Windows Memory Diagnostic in the start menu, choose to restart and check for problems, and the machine reboots into a simplified test.
Press F1 during the test to reach the options and select the extended test suite, which is far more thorough than the default basic pass. Results appear in a notification after the system restarts, and can also be found in Event Viewer under the system log.
Treat this tool as a screening test rather than a verdict. It runs fewer pattern types and typically for less time, so it detects obvious faults but misses marginal ones. A pass here does not clear your memory; a failure here is strong evidence of a real problem.
Understanding What the Results Mean
Zero errors after multiple passes. Your memory is very likely healthy at the tested settings. Look instead at storage health, power supply stability, graphics drivers, or thermal issues.
Errors clustered at similar addresses. This usually indicates a specific defective chip on one module and points cleanly to a warranty replacement.
Errors scattered randomly across the whole range. This is more often a controller, slot, or settings problem. Check the memory voltage, the profile, and whether the sticks are in the slots the manual recommends.
Errors only when all sticks are installed. Individual sticks may be fine while the combination overloads the memory controller. Try a lower speed or looser timings, or use a kit that was sold and validated together.
Safety and Handling Notes
- Always unplug the power cable and hold the power button for five seconds before removing memory. The board holds standby power.
- Touch the bare metal chassis first, and handle sticks by their edges only. The gold contacts should never be touched.
- Open both slot latches before pulling a stick out. Levering a module out against a closed latch cracks the board or the module.
- When refitting, align the notch, then press both ends down firmly until the latches snap closed on their own.
- Follow the manual’s recommended slots. On a four-slot board with two sticks, the correct pair is usually the second and fourth from the processor, and using the wrong pair causes instability that mimics a fault.
Common Mistakes When Testing Memory
- Stopping after one pass. Intermittent faults regularly appear only on the third or fourth pass or during specific test patterns.
- Testing with an overclock enabled. You cannot tell a defective stick from an unstable profile until you test at default speed.
- Testing all sticks together and calling it done. A pass tells you nothing about which stick to replace if it fails.
- Ignoring the slot. Slot and CPU socket pin problems produce identical symptoms to a bad stick.
- Mixing kits. Two separately purchased pairs frequently misbehave together even when each pair is individually perfect. Buy capacity as one matched kit.
- Assuming new means good. Fresh memory can be defective out of the box, and testing a new build before you rely on it is time well spent.
Frequently Asked Questions
How many passes of MemTest86 are enough?
Four full passes is the practical minimum for reasonable confidence. If crashes are rare and hard to reproduce, run it overnight for eight or more passes. Any single error at any point means the test has already given you its answer.
Can bad RAM damage other components?
No, but it can corrupt data written to your drives, including system files and saved documents. That is why you should back up before extended testing and avoid heavy work on a system you suspect has faulty memory.
My memory passes but the PC still crashes. What now?
Look at storage drive health, power supply stability under load, temperature, and graphics drivers. Also confirm the memory is running at settings the board and processor genuinely support, since an aggressive profile can be unstable in daily use even when it survives a synthetic test.
Should I replace one stick or the whole kit?
Replace the whole kit wherever possible. Sticks in a kit are validated to run together, and pairing a single new module with older ones frequently forces lower speeds or reintroduces instability. Warranty claims usually replace the full kit for this reason.
Does memory speed or type affect how likely errors are?
Faster memory running near the limits of the controller is more likely to show errors, especially with four sticks installed. Newer DDR5 RAM kits run at higher frequencies and include on-die correction, while mature DDR4 RAM platforms are generally more forgiving at high capacities.
Final Thoughts
Memory testing is one of the few diagnostics that gives a genuinely clear answer, provided you run it properly. Boot from a USB image rather than testing inside Windows, return the sticks to default speed first, run at least four passes, and isolate stick by stick if anything fails. Confirm the slot as well as the module before you order a replacement, and re-test after any change so you know the fix worked. If you do end up buying, choose a single matched kit rather than mixing modules; our guides to the best RAM for gaming, high-capacity best 32GB RAM options, and tightly tuned best low latency RAM cover the configurations worth considering. A few hours of testing now saves weeks of chasing crashes that were never a software problem in the first place.
