AVX Offset Explained: Why Prime95 Triggers It and How It Differs from Disabling AVX
Short answer: An AVX offset is a BIOS or firmware setting, found mainly on Intel platforms, that automatically lowers the CPU clock multiplier by a set amount whenever the processor detects AVX workloads. It exists because AVX instructions draw more power and generate more heat per clock cycle than ordinary code. Prime95 triggers the offset reliably because current versions use AVX, AVX2 and, where supported, AVX-512 code paths in their FFT calculations – exactly the kind of sustained AVX load the offset was designed for. An offset is not the same as disabling AVX inside Prime95: the offset keeps AVX running at a lower clock, while the in-program settings stop Prime95 from using AVX paths at all. Platform background is collected in our platforms hub.
Why AVX loads get their own clock speed
AVX instructions process wide blocks of data in a single operation, which is why Prime95’s FFT code became much faster when AVX support was added in the 27.x versions, followed by FMA support and later AVX-512 FFT support. The trade-off is electrical: moving and processing that much data per cycle draws more current and produces more heat than the same clock speed running non-AVX code. A processor overclock that is perfectly stable for gaming or rendering can therefore be unstable, or simply too hot, the moment a sustained AVX workload arrives. Motherboard makers added the AVX offset as the compromise: keep the high multiplier for ordinary work, and automatically step down by a few multiplier steps when AVX instructions are detected, trading a little AVX performance for stability and manageable temperatures.
Why Prime95 is the classic trigger
Many programs use AVX only in bursts, so the offset engages briefly and invisibly. Prime95’s Torture Test is different: on a supported processor it runs AVX-heavy FFT calculations on every worker, continuously, for as long as the test runs. That has two practical consequences. First, the clock speed you see during Prime95 is the offset clock, not your headline overclock, which surprises users who expected the higher number. Second, Prime95 is the standard way people discover whether their offset is large enough: if the system is stable at the non-AVX clock but produces errors at the AVX clock, the offset, the voltage, or both need attention. Observing the actual clock during a test, in a monitoring tool, is how you confirm the offset is engaging as intended.
Setting an offset: principles, not numbers
The setting is usually found in the BIOS or firmware overclocking section, near the CPU multiplier controls, under a name resembling AVX Offset or AVX Negative Offset; the exact name and menu location vary by board maker and model, so consult your motherboard manual rather than a guide written for a different board. In general terms, the value states how many multiplier steps to subtract when AVX is detected. The working method is iterative: start from stable settings, apply or increase the offset in small steps, and run Prime95 after each change, noting the AVX clock, temperatures and whether errors appear. A larger offset lowers AVX clocks and heat further but gives up more AVX performance; a smaller offset keeps performance but demands more from voltage and cooling. There is no universally correct value, because it depends on your processor sample, cooling and voltage settings, and this site will not publish per-model numbers it cannot verify for your hardware. Change one variable at a time, and treat stability at stock settings as the baseline every tuned result is compared against.
| Approach | Where it acts | What actually happens | What it means for testing |
|---|---|---|---|
| AVX offset | BIOS or firmware, for the whole system | AVX code still runs, at a reduced clock multiplier whenever AVX is detected, in every program. | Prime95 still tests the AVX code paths, but at the offset clock. Stability here validates that clock, not the higher non-AVX clock. |
| Disabling AVX in Prime95 | Inside Prime95 only, via prime.txt settings such as CpuSupportsAVX=0 | Prime95 avoids the AVX code paths entirely and uses lighter calculations; other programs are unaffected. | Heat and power fall, but the AVX workload is no longer being tested. See our guide to disabling AVX in Prime95 for the steps. |
How to tell whether your offset is doing enough
Run Prime95 with a monitoring tool open and record three observations: the clock speed the processor settles at under the Torture Test, the temperature it settles at, and whether any worker reports an error. If clocks settle at the expected offset level, temperatures settle below your model’s published limit, and a long run completes without errors, the offset is doing its job for that workload. If errors appear at the offset clock, the problem is no longer the headline overclock: the offset clock itself, its voltage, or the cooling behind it needs work, and the correct response is a larger offset, a conservative voltage adjustment within documented limits, or better cooling, changed one at a time. If temperatures settle but remain at the model’s limit with throttling, the offset has traded an error problem for a cooling problem, and the cooling path in our overheating guide is the next step.
Which approach should you use?
If your goal is a system that is stable for real AVX workloads – rendering, encoding, scientific software and modern games can all use AVX – the offset is the more honest tool, because the workload still runs, just at a clock the system can sustain. Use the in-program option, described in how to disable AVX in Prime95, when your goal is narrower: for example, reproducing the lighter heat profile associated with the old 26.6 version, or isolating whether AVX specifically is the source of heat or errors on a test system. Be clear with yourself about which question each run answers, and do not present a pass with AVX disabled as proof that an AVX overclock is stable. For generation-specific context on recent Intel processors, see our upcoming guide to Prime95 on Intel 13th and 14th gen, and return to the troubleshooting hub if the offset work uncovers errors you need to diagnose.