How Long to Run Prime95: The Official 6 to 24 Hour Guidance
Quick facts: The only official duration guidance for Prime95 30.19 build 20 is in stress.txt, the guide written by the program’s author and included with the download. It recommends running the Torture Test for 6 to 24 hours. It also says unstable machines often fail within minutes, and that people who are overclocking can use short 10 to 15 minute runs to explore each frequency step before a long final test. There is no official statement that any fixed run length makes a system completely stable or safe.
What stress.txt actually says, and why it matters
Many forum posts turn duration into a contest or a badge: pass a certain number of hours and the machine is declared finished. The official guide is more careful. It explains that the program has exposed errors after several hours, and in some cases after much longer, which is why the recommended window stretches to 24 hours. At the same time, it recognises that most clearly unstable configurations do not survive long at all. A machine that cannot pass the first few minutes does not need an overnight run to prove the point; it needs a settings change. A machine that passes an hour has cleared only the easiest hurdle. Duration buys probability, not certainty, and each additional hour is most valuable when temperatures and settings stay exactly the same throughout.
Short tests have a job, but it is not certification
When you are tuning an overclock, rebooting for a 24-hour test after every small change would waste days. That is the situation the 10 to 15 minute short run is for. Use a short Small FFTs run to check that a new frequency boots under load, watch whether temperatures level off, and catch immediate errors. Then move to the next step or back off. Once you reach settings you actually intend to keep, switch modes completely: run the long test, in Blend or in the preset that matches your concern, and do not change settings mid-run. Mixing the two modes, for example calling a system stable because it survived the same short test five times, is the most common mistake in stress testing. Five short runs still leave the long-run failure modes untested, including heat soak in the case and memory errors that appear only after sustained access patterns.
How to plan a long run you can trust
Start a long run only when you can monitor the beginning in person. Watch the first 15 to 30 minutes for temperature behaviour, fan response, and early worker errors. Confirm the extracted Prime95 folder is writable so results.txt is saved, and disable sleep so the operating system does not suspend the machine overnight. Note the preset, the worker count, your voltage and frequency settings, and the ambient conditions in a simple text note. If a worker stops, the value of the run is in those details: which preset, after how long, and with what message. Stop the test from the Test menu, preserve results.txt, and change one variable before retesting. Repeating an identical failing run without a change tells you nothing new.
Temperature is a reason to stop, not a duration to endure
No duration guidance overrides thermal common sense. Prime95’s documentation does not publish a universal safe temperature that fits every processor, and this site will not invent one. Check your exact CPU model on the manufacturer’s specification page, watch temperatures with a monitoring tool during the run, and stop if temperatures keep climbing instead of levelling off, if fans fail, or if the system throttles heavily or shuts down. A test you stop for cooling reasons has still done its job: it found the limit. Fix mounting, paste, airflow, or voltage, then start the clock again from zero.
Choosing a preset for the long run
The duration guidance applies to whichever preset matches your question, but the choice changes what a long run proves. A long Blend run is the broadest single choice because it cycles through sizes that live in cache and sizes that press memory. A long Small FFTs run is the stronger statement about core stability and cooling, because that preset produces maximum power and heat. A long Large FFTs run is the stronger statement about memory and the memory controller. If time allows only one overnight run, match it to the change you just made: core voltage or frequency changes call for Small, memory profile changes call for Large, and a brand-new build with no specific suspicion is best served by Blend. Record the preset beside the duration in your note, because a duration without a preset is only half a result.
Frequently asked questions
How long should I run Prime95 according to the official guide?
The stress.txt guide included with Prime95 recommends running the Torture Test for 6 to 24 hours for a thorough stability check.
Can a short Prime95 run prove my system is stable?
No. The same guide notes that unstable machines often fail within minutes, and that short runs of 10 to 15 minutes are useful while exploring overclock steps, but a short pass cannot prove a system is stable. Running longer gives the test more chance to expose a problem.
My system failed after only a few minutes. What does that mean?
According to stress.txt, unstable machines often fail quickly, sometimes within minutes. Treat an early failure as a clear sign that the current settings are not stable, save the error from results.txt, and adjust one setting at a time before retesting.
Does Prime95 promise that a system is safe after a long run?
No. Prime95 provides no such promise. Its license provides the program as-is without warranty, and stress.txt gives duration guidance only. A long error-free run is evidence of stability under that test, not a certification for every workload.
Next steps
For the full workflow, see How to Use Prime95. For the broader question of risk and monitoring, read Is Prime95 Safe? More short answers are collected on the FAQ page, and all guides are indexed in the tutorials hub.