Using Prime95 as a Memory Test: What Large FFTs and Blend Can and Cannot Show
Short answer: Prime95 can stress memory hard, but it is not a dedicated memory tester, and treating it as one leads to missed diagnoses. Large FFTs use data sets too large for the CPU caches, so they stress the memory controller and RAM. Blend, the default preset, mixes everything, and the Torture Test menu carries an official hint: if Blend fails but Small FFTs passes, the problem is often in memory or the memory controller. What Prime95 cannot do is test every memory address methodically from outside the operating system, which is the job a dedicated bootable tool such as MemTest86 exists for. Use Prime95 to find memory instability under realistic combined load, and the dedicated tool to isolate faulty memory itself. The full preset comparison is in Small vs Large vs Blend FFTs.
What each preset tells you about memory
| Preset | Memory relevance (per the program’s own definitions) | How to read the result |
|---|---|---|
| Smallest FFTs and Small FFTs | Data fits in the L1, L2 and (for Small) L3 caches; these presets target the CPU and caches with high to maximum power and heat. | Failures here point first at the CPU path, not RAM, because memory is barely involved. |
| Large FFTs | Data exceeds the caches, forcing constant memory access; the menu defines this preset as stressing the memory controller and RAM. | Failures here, especially when Small FFTs passes, put memory and its controller at the top of the list. |
| Blend (default) | Tests all of the above across a range of sizes. | The menu’s own note applies: Blend failing while Small passes points to memory or the memory controller. Blend passing alone does not clear memory, because time is shared across sizes. |
| Custom | You choose the FFT size range and how much memory to use. | Useful for dwelling on large sizes once you already suspect memory, rather than as a first test. |
Since version 29.8, the Torture Test chooses its FFT ranges from your CPU’s cache size rather than from a fixed table, and on systems with more than 5 GB of memory Blend defaults to using all memory minus 3 GB. That means the same preset name adapts to your hardware; do not compare your run against old forum posts that quote fixed FFT ranges from much older versions as if they were specifications for the current release.
A sensible Prime95 memory workflow
- Start at base memory settings. Disable the memory overclock profile (XMP, EXPO or manual timings) and run Large FFTs. A clean run at base speed followed by failures at profile speed is a clear, actionable result: the profile settings are not stable on your system as configured.
- Run Small FFTs as the control. If Small FFTs also fails, the problem is not memory alone, and you should work through the general decision tree in the troubleshooting hub before drawing memory conclusions.
- Run Blend for combined load. Blend stresses CPU, caches and memory together, closer to a worst-case real workload. Instability that only appears under combined load is still real instability, even if each subsystem passes alone.
- Record the pattern. Note the preset, the elapsed time and whether one worker or several workers reported errors. Memory faults often produce errors across different workers, since all of them share the same RAM, unlike a single weak core.
Where Prime95 stops and MemTest86 starts
Prime95 runs inside your operating system, which means part of your memory is occupied by the system itself and cannot be tested, and a memory fault can crash or corrupt the very environment doing the testing. A dedicated bootable tester runs instead of Windows or Linux, can address the memory far more completely, and tests it with patterns designed purely for finding faulty cells and marginal sticks. The division of labour is therefore straightforward: Prime95 answers the question of whether your whole system, memory included, stays correct under heavy combined load; MemTest86 answers whether the memory itself is sound, stick by stick if needed. Our head-to-head, Prime95 vs MemTest86, explains when each tool should lead. If Prime95 points at memory, confirm with the dedicated test before buying replacement RAM; if the dedicated test passes every stick but Blend still fails at profile settings, the memory controller settings or the profile itself remain the likely problem, and base settings are your stable fallback.
Testing individual sticks and slots
When the dedicated test or the Prime95 pattern points at memory, the oldest isolation method is still the most decisive: test one stick at a time, in the slot your motherboard manual designates for single-stick use. A fault that follows one stick wherever it is installed identifies that stick. A fault that stays with one slot regardless of which stick occupies it points instead at the slot, the board or the memory controller. Change only the stick or only the slot between runs, and write down which combination produced which result, because with two sticks and several slots the combinations multiply quickly and memory of what you tested is unreliable after a long evening of runs. This physical isolation is something no in-Windows test, Prime95 included, can do for you, and it is the step that turns a suspicion into a part you can confidently replace or return.
Limits to state honestly
No pass, in Prime95 or anywhere else, proves memory perfect for all time; marginal faults can depend on temperature, load pattern and time. The official stress.txt guidance for the Torture Test overall is 6 to 24 hours for a thorough check, and that patience applies to memory suspicion too, since memory errors can be rare events per hour of testing. Equally, do not use Prime95 alone to condemn a memory kit for a warranty claim when a dedicated test from outside the operating system is the evidence the situation calls for. Used in the right order, the two tools complement each other: Prime95 finds the instability in context, and the dedicated tester isolates it.