CPU Not Reaching OC during load??

[xkm1948]

So my CPU is overclocked to 4.2GHz which I am 100% sure. Somehow during some of my work load it is only reaching up to 3.9GHz, confirmed by both CPU-Z and Task manager.

So I thought about AVX2 offset. Problem is my AVX offset is 2. So my AVX speed should be spot on 4GHz. Could this happen due to chip instability? I am really confused here.

 

[Dia01]

Is window power options set to high performance and the min/max processor state settings correct. Grasping at straws here really.....

 

[Vayra86]

Euhm... this is mysterious

How is your OC set up, as an all-core boost, or a multi without that, or specific boost clocks for each core count?

 

[xkm1948]

It is ASUS all core sync overclocking. I do have a negative vcore offset. Would that be the cause?

 

[Vayra86]

It is ASUS all core sync overclocking. I do have a negative vcore offset. Would that be the cause?

I have little experience overclocking HEDT on Asus, sorry. But I would attribute this behavior to an odd OC / BIOS setting somewhere yes. Chip instability, unlikely - degradation will cause additional voltage required for a certain clock, not a clockspeed / multiplier drop off. If the voltage is insufficient the OC just falls apart and you'll notice in the usual ways.

You said you had a negative AVX offset, which I know can act funny though I've never seen it drop multi below what its' set at.

What you can do is switch the Asus All core sync OC to a per-core OC, that you just set for 2 ~ 10 core boost at the desired clocks (4.2 Ghz like it is now). This way you can remove any Asus trickery from the equation there while effectively not changing your OC. So you can at least rule it out.

Negative vcore offset, if this is just an adaptive voltage type of vcore setting and not an additional offset value for specific loads, then no, it should not make you drop a multiplier under AVX, rather the CPU will just start giving errors due to lack of voltage or the OC collapses altogether.

Beyond all this, look for any out of the ordinary BIOS settings, I would also look at the safety measures built into it/the CPU such as the maximum allowed Watts during prolonged/sustained loads. You do push that sucker hard and you may exceed a value there to cause it to clock differently over time.

 

[Chane]

Hello, I have experienced this on i5-6600k and i7 7700k in the past and in those cases the chips were being power throttled by the motherboard. Check your BIOS for settings similar to these;

▶Long Duration Power Limit (W) [Auto] Sets the long duration TDP power limit for CPU in Turbo Boost mode.
▶Long Duration Maintained (s) [Auto] Sets the maintaining time for Long duration power Limit(W).
▶Short Duration Power Limit (W) [Auto] Sets the short duration TDP power limit for CPU in Turbo Boost mode.
▶CPU Current Limit (A) [Auto] Sets maximum current limit of CPU package in Turbo Boost mode. When the current is over the specified value, the CPU will automatically reduce the core frequency for reducing the current.

In my case Auto was not a sufficient setting and the one that corrected it was increasing the CPU Current Limit setting.

 

[phanbuey]

^ this is the most likely answer.

see if disabling C states & putting windows in high performance mode solves the issue, if so, then you know it is a power management related

 

[xkm1948]

Turns out this program was indeed using AVX2 and that 3.9GHz matches up to my AVX offset of 3. Stupid me forgot my AVX offset has been 3 instead of 2.

 

[eidairaman1]

Write it down lol

 

[hat]

Glad you got it sorted out. I was genuinely starting to get frustrated just thinking of how... frustrating something like that would be to me.