Windows Memory Diagnostic is a convenient first check for obvious RAM faults. A bootable tool such as MemTest86 runs outside the normal Windows environment and offers broader patterns and longer passes, which can expose marginal XMP or EXPO instability that a quick built-in test misses.
Quick Answer
Run Windows Memory Diagnostic when you need a fast check with no USB setup. For a new kit, tuned profile or intermittent corruption, boot a current MemTest86 image and complete several passes. Follow it with a memory-heavy test inside Windows because no single utility covers every controller, CPU and software path.
Browse DDR5 memory kits by capacity and rated profile, then compare the RAM best-seller list. Confirm motherboard support, module count and CPU memory limits before treating advertised speed as guaranteed.
What Windows Memory Diagnostic Does Well
Search for the tool from Windows, choose a restart and let the test run before the operating system loads. It is built in, quick to reach and useful when a PC shows crashes or file errors.
After restart, check the result in Windows or Event Viewer if the notification does not appear. A pass means the patterns it ran found no error. It does not certify every address, temperature and timing combination.
Why Use a Bootable Test
MemTest86 controls the test environment and can run repeated patterns across a large part of memory. Create the USB from the official current package, boot it through UEFI and record each error with the active BIOS settings.
Any reproducible error at stock needs attention. With XMP or EXPO active, return to default JEDEC settings and repeat. This separates a defective module from a profile, controller or motherboard issue.
Test one matched kit at a time in the board's recommended slots. If errors remain, test individual modules and slots to isolate the pattern. Keep electrostatic handling and the board manual in mind.
Finish Inside Windows
Run a maintained memory stress tool and your real workload after the bootable passes. The operating-system stage adds drivers, CPU scheduling and application behaviour. Watch for WHEA events, calculation mismatches and silent application exits.
Save the Evidence
Photograph the test summary and write down the DIMM slots, BIOS version, memory profile and CPU settings. When an error appears, note its address and test number. Repeated errors on one module or slot make the next isolation step clearer, while random failures across configurations can point towards the controller or tune.
FAQ
Does one clean Windows Memory Diagnostic pass prove RAM is stable?
No. It is a useful screen, while longer bootable and in-Windows testing cover more conditions.
Does a MemTest86 error always mean the DIMM is faulty?
No. The memory profile, controller, motherboard slot or CPU settings can cause errors. Retest at defaults.
Should XMP or EXPO be enabled during testing?
Test the intended profile, then repeat at JEDEC defaults if an error appears so you can isolate the cause.
Use the Windows check for a fast screen, complete several bootable passes for the intended memory profile and finish with a real Windows workload.