How to Run a Memory Test: Step-by-Step Guide

If your computer keeps freezing, throwing blue screens, or corrupting files for no obvious reason, faulty RAM is one of the first suspects worth ruling out. The fastest way to run a memory test is with the built-in Windows Memory Diagnostic tool (search it in the Start menu, then restart), but the most thorough method is a bootable USB tester like MemTest86 run over multiple passes.

That difference matters more than most people realize. A quick built-in scan gives you a rough yes-or-no. A deep bootable test, running outside the operating system entirely, catches the subtle, heat-induced, intermittent errors that hide from casual checks. This guide walks you through both, and tells you what to do when a module actually fails.

What Is the Fastest Way to Check Your RAM?

Speed and accuracy pull in opposite directions here, so pick based on what you’re chasing.

Quick built-in scan

Windows Memory Diagnostic runs a native test with zero downloads. You launch it, the machine reboots, and within minutes to an hour you get a verdict. Great for a first pass when you just want to know whether something’s obviously broken.

Deep bootable test

MemTest86 loads before Windows even wakes up. Because it takes exclusive control of the hardware, it hammers the memory channels with more than a dozen test algorithms and surfaces problems the OS-level tools miss. The tradeoff is time. Figure roughly an hour per 8GB.

When each fits

Use the built-in tool for a fast sanity check or before a warranty return. Reach for the bootable USB stick when you’re overclocking with XMP or EXPO, chasing an intermittent BSOD, or verifying new RAM. Here’s the rough logic I follow:

• Random freezing or file corruption → start with the quick Windows scan, escalate if clean but symptoms persist.
• Overclocked memory or repeated blue screens → skip straight to a multi-pass bootable test.
• Brand-new build validation → run MemTest86 for at least four full passes before trusting it.

Run Windows Memory Diagnostic Step by Step

Launch the tool

Type “Windows Memory Diagnostic” into the Start menu, or run mdsched.exe from Command Prompt. Choose “Restart now and check for problems.” The computer reboots into a blue diagnostic screen and gets to work automatically.

Choose test mode

Press F1 during the test to switch between Basic, Standard, and Extended. Extended runs more algorithms and takes longer, but on Windows Server or any machine where data integrity is non-negotiable, that extra depth earns its keep.

Read the results

After the reboot, the test results don’t always pop up on their own. Open Event Viewer, expand Windows Logs, click System, and look for the MemoryDiagnostics-Results event. A clean pass says no errors. Anything else, and you’ve got a lead worth chasing.

Run Apple Diagnostics on a Mac

Intel Macs

Restart and hold the D key right as it boots. Apple Diagnostics loads and scans the hardware, memory included.

Apple Silicon Macs

Shut down, then press and hold the power button until startup options appear. Release, then press Command + D to launch the diagnostic.

Error reference codes

Memory faults typically show as codes beginning with NDR (like NDR001). Jot the code down. It’s what an Apple technician will ask for first.

Why Bootable USB Testers Are the Gold Standard

MemTest86 vs Memtest86+

Both run on the raw x86 hardware. MemTest86 (from PassMark) offers polished UEFI support and automatic reporting; Memtest86+ is the open-source sibling that stays current with DDR5 and the latest modules. Either one beats an OS-bound scan for finding deep defects.

Create the boot drive

Download the software, write the image to a USB flash drive using the developer’s utility like imageUSB, then restart and pick that USB stick from your motherboard’s boot menu.

Run multiple passes

One pass proves almost nothing. Enthusiasts on overclocking forums push four to eight full passes, because a single lap can miss the sweaty, heat-stressed error that only shows up after the DIMMs warm up.

How Do You Read and Trust the Test Results?

Passes and error counts

Zero errors across several completed passes is what you want. Even one flagged error means the module is suspect. Memory doesn’t get a pity vote.

False positives

A wildly overclocked system or a botched BIOS setting can throw phantom errors. Before condemning a stick, reset CMOS to stock timings and retest clean.

Heat and timing edge cases

I’ve watched kits that bench beautifully fail after two hours of sustained load. If the quick test passes but your machine still coughs under real work, you’re likely staring at a voltage or timing edge case, not a dead module.

What Should You Do When RAM Fails the Test?

Re-seat and swap slots

Half the “faulty RAM” problems I’ve fixed were just poor contact. Power down, pull the module, wipe the contacts, and firmly re-seat it in a known-good slot.

Isolate a bad module

Test one stick at a time. Run each module individually to pin down which one throws the error, and whether it’s the DIMM or the slot betraying you.

XMP, EXPO, and voltage checks

Only enable XMP or EXPO after confirming stability at stock speed. Then validate the overclocked profile across several long passes before calling it good.

Choose the Right Tool for Your Situation

For a lazy Sunday sanity check, the built-in Windows tool is plenty. For anything mission-critical, a new build, or an overclock you’re staking your work on, boot MemTest86 and let it run overnight.

FAQ

How long does a memory test take?

A quick built-in scan runs 15 minutes to an hour. A full MemTest86 pass is roughly an hour per 8GB.

Can I use my computer during the test?

No. Both the Windows and bootable tools need exclusive control, so the machine is out of commission until it finishes.

Is one error a real problem?

Yes. Confirm it isn’t a false positive from overclocking, but a genuine error means that module needs replacing.

Conclusion

Testing memory isn’t a one-and-done checkbox. Start quick, escalate deep, and never trust a green banner if your system keeps stumbling under load. Match the tool to the stakes, run enough passes to expose the hidden flaws, and you’ll swap guesswork for the quiet confidence that your RAM won’t be the thing that ruins your afternoon.