It is common knowledge that the AVX offset helps us achieve better overclocks with programs that don't have AVX workloads. Basically, the CPU downclocks by a few multipliers when it detects AVX instructions, e.g. when encoding video.
What is /not/ common knowledge is that most games nowadays, especially AAA games, use AVX to a limited degree, e.g. The Witcher 3. The important note here is that the limited AVX used in games will /not/ cause any instability...
The problem is that [most] games will downclock the CPU by this overkill AVX offset, e.g. a 5GHz 8700k will downclock to 4700MHz when a game is running because AVX use is detected, thereby severely hamstringing game performance when AVX offsets are enabled - when playing the AVX game with 0 AVX offset will work just fine.
Most of us are gamers here, and I believe you will agree with me that this is a problem worth solving.
Most people I know leave the AVX offset at 0 because of this, and prefer to suffer the occasional crash when some program needs to heavily use AVX, e.g. a download being decrypted.
What is required is a feature where AVX offset only takes effect when power usage above a certain threshold is detected. This would mean that light AVX workloads, i.e. most games, will not trip the offset, however heavy AVX workloads, such as video encoding/encryption etc, will, thereby allowing us to game with maximum CPU speed.
Towards that end, I have tried a couple of things with limited success with my ASUS Hero board:
-- There is a temperature vs CPU speed setting - you can limit the CPU multiplier when the CPU goes above a certain temperature. There is also an AVX offset setting in this submenu but it does not work as intended - this AVX setting will always kick in just as if you had adjusted the main AVX offset setting, so is ultimately just as useless.
-- There is a power limit setting where you can limit power to the CPU to a certain wattage thereby keeping AVX temperatures and therefore stability under control.
Unfortunately neither of these settings work reliably, probably because it takes the system a little while to detect over temperature/over power, by which time the CPU has already destabilised and crashed to a BSOD.
Discussion and possible solution to this problem would be quite insightful.
Thanks for reading...
What is /not/ common knowledge is that most games nowadays, especially AAA games, use AVX to a limited degree, e.g. The Witcher 3. The important note here is that the limited AVX used in games will /not/ cause any instability...
The problem is that [most] games will downclock the CPU by this overkill AVX offset, e.g. a 5GHz 8700k will downclock to 4700MHz when a game is running because AVX use is detected, thereby severely hamstringing game performance when AVX offsets are enabled - when playing the AVX game with 0 AVX offset will work just fine.
Most of us are gamers here, and I believe you will agree with me that this is a problem worth solving.
Most people I know leave the AVX offset at 0 because of this, and prefer to suffer the occasional crash when some program needs to heavily use AVX, e.g. a download being decrypted.
What is required is a feature where AVX offset only takes effect when power usage above a certain threshold is detected. This would mean that light AVX workloads, i.e. most games, will not trip the offset, however heavy AVX workloads, such as video encoding/encryption etc, will, thereby allowing us to game with maximum CPU speed.
Towards that end, I have tried a couple of things with limited success with my ASUS Hero board:
-- There is a temperature vs CPU speed setting - you can limit the CPU multiplier when the CPU goes above a certain temperature. There is also an AVX offset setting in this submenu but it does not work as intended - this AVX setting will always kick in just as if you had adjusted the main AVX offset setting, so is ultimately just as useless.
-- There is a power limit setting where you can limit power to the CPU to a certain wattage thereby keeping AVX temperatures and therefore stability under control.
Unfortunately neither of these settings work reliably, probably because it takes the system a little while to detect over temperature/over power, by which time the CPU has already destabilised and crashed to a BSOD.
Discussion and possible solution to this problem would be quite insightful.
Thanks for reading...
