Test RAM in layers: start with Windows Memory Diagnostic, confirm with MemTest86, then stress the system with OCCT. Bad memory can cause blue screens, random app crashes, corrupt downloads, failed game launches, and weird freezes that seem to appear from nowhere. Microsoft includes Windows Memory Diagnostic for checking memory after a restart [source: Microsoft], so you already have a first tool ready. Still, one quick test is not enough if the problem shows up only under heat, XMP, or long gaming sessions.

TLDR: Use Windows Memory Diagnostic first because it is built into Windows and takes little setup. If it finds errors, assume a RAM or memory setting problem right away. If it passes but crashes continue, run MemTest86 from a USB stick for several passes; for example, one bad stick may show 1 error after 40 minutes, while Windows reported nothing. Use OCCT last to test RAM under real Windows load, especially if failures happen during games, rendering, or heavy browser use.

Why Use Three RAM Tests?

RAM faults are annoying because they do not always fail on command. A stick may pass a 10-minute check, then crash after the case warms up. Another system may be fine at default speed, then fall apart with XMP or EXPO enabled.

Each tool catches a different kind of problem:

• Windows Memory Diagnostic: Fast, simple, already installed.
• MemTest86: Boots outside Windows, which removes drivers and apps from the equation.
• OCCT: Tests memory while Windows is running, with heat, CPU load, and voltage behavior in play.

The catch is that none of these tools is magic. A clean pass does not always mean “perfect RAM.” It means the tool did not catch errors during that run.

Step 1: Run Windows Memory Diagnostic

Windows Memory Diagnostic is the easiest place to start. It is useful when you need a quick yes-or-no check before tearing open the case.

1. Press Windows + R.
2. Type mdsched.exe and press Enter.
3. Choose Restart now and check for problems.
4. Let the test run after reboot.
5. After Windows loads, check the result in Event Viewer.

To see the result, open Event Viewer, go to Windows Logs, then System. Use Find and search for MemoryDiagnostics-Results.

You can press F1 while the test is running to change options. Standard is fine for a quick scan. Extended takes longer and may catch more faults. If you are already seeing blue screens, use Extended and increase the pass count.

If Windows Memory Diagnostic reports hardware problems, stop guessing. Turn off XMP or EXPO first. Test again. If errors remain, test one RAM stick at a time.

Step 2: Use MemTest86 for a Cleaner Test

MemTest86 is stronger because it runs from a bootable USB drive instead of inside Windows. That means fewer distractions. No antivirus scan. No game launcher. No broken driver muddying the result.

Download MemTest86 from PassMark, write it to a USB stick, and boot from it. The free edition is enough for most home users and supports UEFI systems [source: PassMark].

Basic process:

1. Back up anything useful on the USB stick.
2. Create the bootable MemTest86 USB.
3. Restart the PC and open the boot menu.
4. Select the USB drive.
5. Start the default test.

Let it run for at least 4 passes if you have time. Overnight is better for random crashes. Honestly, it feels a bit painful to stare at a test screen for hours, but one red error line is worth more than three days of guessing.

What counts as bad? Any error is bad. RAM should not produce even one error. If MemTest86 shows errors, do this:

• Disable XMP or EXPO and test again.
• Test one stick at a time.
• Test each stick in the same motherboard slot.
• If both sticks pass alone, test slots one by one.
• Update BIOS if memory training seems unstable.

This helps separate a bad RAM stick from a bad slot, weak memory controller, or unstable overclock.

Step 3: Use OCCT for Real-World Stress

OCCT is different. It runs inside Windows and can stress memory while tracking temperatures, voltages, and CPU behavior. That makes it great for finding problems that only happen when the whole PC is working hard.

Install OCCT, open the Memory test, and set a test length. Start with 30 minutes. If the PC usually crashes after long gaming sessions, run it for 1 to 2 hours. Watch for errors, freezes, sudden reboots, or temperature spikes.

OCCT can also mix CPU and memory stress, which is useful because the memory controller is inside the CPU on modern systems. A system may pass MemTest86, then fail OCCT because heat or voltage droop pushes it over the edge.

Good signs:

• No errors reported.
• No blue screens.
• No sudden restart.
• Temperatures stay under control.

Bad signs:

• OCCT reports memory errors.
• The system locks up.
• Windows restarts with no warning.
• Errors appear only when XMP or EXPO is enabled.

How to Read the Results

If all three tools pass, your RAM is less likely to be the cause. Look at storage, drivers, GPU, PSU, or Windows corruption next.

If Windows Memory Diagnostic fails, treat it seriously. It is not as detailed as MemTest86, but errors there usually mean trouble.

If MemTest86 fails, suspect the stick, slot, BIOS settings, or memory overclock. Test parts one by one.

If only OCCT fails, suspect heat, power, XMP or EXPO instability, or the CPU memory controller. Lower RAM speed one step, raise nothing yet, and test again.

The best workflow is simple: quick scan, boot test, Windows stress test. It saves time, cuts the guesswork, and keeps you from blaming Windows when the real problem is a tiny memory error hiding under load.