Problems and testing

How to run MemTest86, TestMem5 and OCCT (and read the results)

Use MemTest86 when you think a stick might be faulty, and TestMem5 or OCCT when you want to know whether your XMP, EXPO or tuned settings are stable. MemTest86 boots from a USB stick and tests outside Windows; the other two run inside Windows and usually find speed-related instability faster. With all three, a single error counts as a failure: something needs to change.

Which test should you use?

Tool Runs from Best for Cost
MemTest86 A bootable USB stick Finding a faulty stick, checking a kit at default settings Free edition; Pro adds automation and extra reporting
TestMem5 Windows Checking XMP, EXPO or a manual overclock Free download
OCCT Windows The same, with temperature and voltage monitoring built in Free edition caps each test at one hour

They work best together. For a new build or a new kit, run MemTest86 at default settings first to rule out a bad stick. Then turn on XMP or EXPO and check that with TestMem5 or OCCT. Evetech's suggested routine ends with a MemTest86 run, real workloads, sleep and resume, and several days of normal use.

Before you start

  • Back up anything important. Unstable memory can damage files as they're saved, even when the PC seems fine.
  • Write down your setup: BIOS version, kit part number, which slots you're using, and whether XMP or EXPO is on. You'll want to compare runs later.
  • Install HWiNFO so you can watch the memory temperature during Windows tests. See how hot is too hot for DDR5?
  • Close everything else before a Windows test, and leave the PC alone while it runs.

How to run MemTest86

MemTest86 is made by PassMark. MemTest86+ is a separate program with a similar name; this guide covers PassMark's version.

  1. Download the Windows USB image from memtest86.com and extract it. The folder contains the image and a tool called ImageUSB.
  2. Run ImageUSB and pick your USB stick. This erases everything on the stick, so double-check you've picked the right drive.
  3. Boot from the stick. Use your board's boot menu key (your manual lists it) or put the USB stick first in the BIOS boot order. PassMark lists Secure Boot support for both editions, so you usually don't need to turn it off.
  4. Let it start. A splash screen counts down 10 seconds, then the tests begin with default settings: all tests, all CPU cores in parallel, four passes. The defaults are right for most people.

How long it takes depends on your CPU, memory speed and capacity. PassMark's own example is about 15 minutes for one pass and 120 minutes for four, and a big kit on a slow CPU can run overnight. PassMark's advice: "Generally a single pass is sufficient to catch consistent errors." For random crashes that come and go, run longer, either the full four passes or overnight.

How to read MemTest86 results

When it finishes, MemTest86 gives an overall result:

  • PASS: every configured test finished with no errors.
  • FAIL: at least one error was found. There's no acceptable number of errors.
  • INCOMPLETE PASS or INCOMPLETE FAIL: you stopped it before all tests finished. Treat an incomplete pass as unfinished, not as a clean result.

The summary also lists the lowest and highest addresses with errors, which bits were wrong and which CPU cores saw them. Press y when asked and it saves an HTML report to the USB stick, which is handy for a warranty claim.

Three details are easy to misread:

  • The hammer test (Test 13). It hammers memory at full speed first. If that finds errors, it repeats at a slower rate that PassMark describes as the memory makers' worst case. Errors at both rates are reported as errors. Errors only at the fast rate show up as a warning instead.
  • Block move errors (Test 6) are real errors, even on name-brand memory and a good board. Don't dismiss them.
  • A failure doesn't always mean a bad stick. PassMark notes that memory failing in one system can work fine in another, and may only need more conservative settings. If you saw errors with EXPO or XMP on, retest at default before you blame the RAM.

The free edition doesn't tell you which stick failed; PassMark lists faulty-module identification as a Pro feature. To find the bad one, test each stick on its own, in the slot your manual recommends for a single stick.

How to run TestMem5

TestMem5 (TM5) runs inside Windows, and what it tests depends on a config file. Use the version maintained by CoolCmd on GitHub. It fixes bugs in the old 0.12 release and bundles the popular configs, so you don't have to hunt for them.

  1. Download TestMem5.7z from the releases page on CoolCmd's GitHub, delete any older TM5 folders, and extract it anywhere.
  2. Run TM5.exe as administrator.
  3. Pick a config in Settings. Config files live in the program's bin folder, and the default is Universal 2. Changing a setting restarts the program.
  4. Set the test length. In this version you set the duration in minutes; when time runs out, it finishes the current cycle and stops.

Windows Defender and some other antivirus tools may flag TM5. The README says this is a false positive from heuristic scanning. Only download it from the GitHub page.

The configs most people use come from a tuner known as anta777. A Hardwareluxx forum overview lists their settings:

Config Time setting Cycles Good for
Universal 2 (CoolCmd's default) 100% 3 A quick check after each change
Extreme1 500% 3 A longer final test
Absolut 1250% 3 The longest, most thorough run

Reading the result: by default, TM5 stops at the first error and shows one message in plain language with suggested fixes. Errors are also written to a log. You can raise the error limit, but for a stability check there's no point: one error means the settings aren't stable.

How to run OCCT

OCCT is a stress-testing suite with a memory test and live monitoring built in.

  1. Install it from ocbase.com. The free edition limits each test to one hour and adds a short cooldown between tests.
  2. Open the Memory test and use one of the presets, such as the classic OCCT memory test. The test is built from 16 blocks you can combine, but the presets are fine.
  3. Leave Windows some room. Test most of your memory, but don't give it everything. OCCT can't test memory Windows has reserved anyway.
  4. Run at least an hour. Evetech recommends 60 minutes as a minimum and two hours or more for intermittent errors. On the free edition, that means two back-to-back runs.

Reading the result: the test graph turns red at the moments OCCT detects an error, and errors are listed in the log. Any error means instability, either from a profile your kit or board can't hold, or from a faulty stick. Glance at the memory temperature in the monitoring panel too, since errors that appear only once things warm up point to heat.

What should you do after a failure?

Errors can come from the stick, the memory controller in your CPU, the motherboard, the CPU's own tuning or temperature. Work through it in this order:

  1. Turn XMP or EXPO off and test again. If the errors stop, the RAM is fine; the profile just isn't stable on your system.
  2. If errors happen at default speed, test one stick at a time. A stick that fails on its own while the other passes in the same slot is faulty. See how to RMA RAM.
  3. If errors appear only after a while, check temperatures and airflow over the sticks.
  4. Check Windows' Event Viewer for hardware errors. Evetech points out that a test showing zero errors while Windows logs hardware faults isn't a clean result.

A clean run only means that test found nothing that time. That's why the long final test and a week of normal use still matter. On Ryzen 7000 and 9000, fixing RAM instability on AM5 has the full checklist.

How long is long enough?

Situation What to run
New kit, or you suspect a bad stick MemTest86 at default settings, four passes
After each small settings change 20 to 30 minutes of TM5 or OCCT
Final check of a profile or tune A few hours of TM5 (Extreme1 or Absolut) or repeated OCCT runs, then MemTest86
After that A week of normal use, including sleep and wake

If you're tuning beyond the profile, how to manually overclock DDR5 shows where testing fits into each step.

The short version

  • MemTest86 from USB finds faulty sticks; TestMem5 and OCCT in Windows find unstable XMP, EXPO or tuned settings faster.
  • One error is a fail in every tool. There's no acceptable number.
  • Errors with the profile on but none at default mean the settings need changing, not the RAM.
  • Find a bad stick by testing each one alone in the same slot.
  • Short tests after each change, a few hours at the end, then a week of normal use.

Sources