Prime95 on Ryzen 7000 and 9000: Stress Testing Zen 4 and Zen 5
Bottom line first: Ryzen 7000 and 9000 processors are well suited to a modern Prime95 run because the current build can use their AVX-512 support, and because the Torture Test checks its own results as it goes. Start at stock settings or with a clearly recorded PBO configuration, run Small FFTs to find the real temperature and power behaviour under maximum load, monitor the run with a sensor tool, and only judge a tuned setup after a long Blend run. Change one setting at a time, and treat any worker error as a failed test, not as a rounding quirk to ignore.
Prime95 is a freeware program by George Woltman, written for GIMPS, the Great Internet Mersenne Prime Search. Its Torture Test is a secondary use described in the included stress.txt guide: the program calculates continuously and compares each result against a known correct answer. That result checking is why it remains useful on a new platform: a Ryzen system can feel fast and still return a wrong answer under sustained load if voltage, memory or cooling margins are too thin. All platform guides on this site are collected on the platforms hub.
AVX-512 on Ryzen 7000 and 9000
Ryzen 7000 series processors, based on the Zen 4 architecture, and Ryzen 9000 series processors, based on Zen 5, support AVX-512 instructions. That matters for Prime95 because AVX-512 FFT support was added to the program in version 29.8, and the current 30.19 build 20 can therefore use a wide vector code path on these chips instead of falling back to narrower AVX2 work. In practical terms, a Torture Test run on these platforms is a genuinely heavy modern load, and heat and power behaviour during Small FFTs deserves respect from the first minute: a cooling setup that looks fine in short bursts may behave very differently once the whole package has soaked in heat for an hour. If you ever need to compare behaviour with the wide vector path removed, the program can disable instruction paths through prime.txt settings, covered in our AVX guidance linked below.
PBO, power limits and the temperature wall
Most Ryzen stress testing today happens under Precision Boost Overdrive, or PBO, rather than under a fixed manual clock. Under PBO the processor raises clocks while it stays inside its configured power, current and temperature limits, and it reduces clocks when it reaches one of those limits. That behaviour changes how you should read a Prime95 run. A falling clock speed during Small FFTs is not automatically a failure: it may simply be the processor managing itself against its temperature wall, the point at which it holds temperature by giving up frequency. What matters for stability is whether the calculations stay correct at whatever speed the processor settles into, and whether temperatures level off instead of climbing without settling. This is also why comparing two PBO configurations by clock speed alone misleads. A configuration that holds a slightly lower clock but completes hours of checked work is the better configuration, and a configuration that boosts higher for ten minutes and then produces a worker error has told you its margin is too thin. Record your PBO settings, your power limits if you changed them, and the ambient conditions alongside every serious run.
What Small FFTs means on Ryzen
The Torture Test presets are defined by where their data lives. Smallest FFTs test the L1 and L2 caches with high power, heat and CPU stress. Small FFTs test the L1, L2 and L3 caches and are described by the program as maximum power, heat and CPU stress. Large FFTs stress the memory controller and RAM. Blend, the default, tests all of the above. Since version 29.8 the FFT sizes for each preset are chosen automatically from your CPU cache size, so do not copy fixed size ranges from old forum tables. On a Ryzen build, use Small FFTs first to establish the honest worst case for core temperature and package power under PBO. Then use Large FFTs when memory speed or timings are part of what you changed, because Ryzen memory behaviour and core behaviour are tuned through related settings and a failure can live on either side. Finish with Blend for the long run, following the official stress.txt duration guidance of 6 to 24 hours for a thorough check, while remembering that unstable systems often fail within minutes and that short runs are only for exploring steps.
Monitoring the run properly
Prime95 itself is not a monitoring dashboard, so watch the run in a separate sensor tool. Many builders use HWiNFO, a free monitoring program from the HWiNFO website, to follow core temperatures, clock speeds, package power and throttling behaviour while the test runs. This site has no commercial relationship with HWiNFO; it is recommended because watching the sensors is the difference between a useful test and a guess. Watch for three patterns: temperature that settles, which is normal under a maximum load; temperature that keeps climbing, which points at cooling or airflow; and errors that appear only after heat soak, which point at a margin that disappears when the machine is hot. For a deeper reading, see our guide to Prime95 temperatures explained.
No AVX offset? The Ryzen way of thinking
Intel platforms offer an AVX offset, a BIOS setting that lowers the multiplier only when AVX work is detected. Ryzen platforms do not offer an equivalent Intel-style AVX offset, so the tuning levers are different. The same goal, keeping heavy vector loads inside a safe power and temperature envelope, is reached through the platform’s own controls instead: PBO power limits, temperature limits, curve and voltage behaviour, or, at the Prime95 level, disabling the AVX or AVX-512 code paths in prime.txt so a run can be compared with the full load. The principle is identical even though the menus differ: reduce the intensity of the heaviest load in a controlled way, then prove the result with a checked run, rather than accepting errors as the price of a headline clock speed. Our guide to the Prime95 AVX offset explains the Intel setting and the reasoning behind it, and that reasoning is the part that transfers to Ryzen even though the setting itself does not.
If you are shopping or studying alongside a build
Cooling is the component that decides most Ryzen stress test outcomes, and readers who are planning an upgrade around a high sustained load often look at large dual-tower air coolers such as the Noctua NH-D15, available via our Noctua NH-D15 link. If you are also deciding on a platform upgrade at the same time, start from the verified packages on the download page and the overview on the platforms hub before you change hardware and settings together, so you can still tell which change caused which result. For readers who want to study the underlying topics more formally, structured courses are available through our Coursera link. Disclosure: the two product and course links in this section are sponsored affiliate links. If you buy or enrol through them, this site may earn a commission at no extra cost to you. They are buying options, not requirements for running the test described above.
Bottom line
On Ryzen 7000 and 9000, let Prime95 do what it is built to do: run the current version so the AVX-512 path is in play, establish the temperature truth with Small FFTs, check memory with Large FFTs, prove the final PBO configuration with a long Blend run, and watch the sensors throughout. A clean, long, error-free run at settings you have written down is worth more than any short burst at settings you cannot reproduce.