I have the Asus version of Intel XTU that comes with the Maximus XI Hero.
Yes, this is how all the dynamic clocks work. At any given instant in time, all the cores must run at the same multiplier. It can sometimes look otherwise in HWinfo, but that's because it's not actually measuring all the core multipliers at the same instant of time.
Well, I guess just use Intel's own version then.
Ahh ok, thanks, forgot about that.
What exact settings are you running on the Hero to achieve the balance of AVX/non-AVX?
Ok, short follow-up, I've tested power limiting AVX/FMA3 load a bit. I see 2 problems with it:
1. The transition from the high multiplier towards the lower, power-throttled one is still occuring (well, of course, what was I thinking?;)). It might still be triggering the transient crash and nothing's really gained.
2. The limited frequency probably is whithin "normal" operating range (36x - 49x for my 9700k), applying adaptive voltage VIDs as it's supposed to. But this might not be enough for the torturing AVX load, leading again to a crash. Way out is applying a positive offset voltage, but then, this means higher voltages overall.
So... I don't really know. Might be that in the end we actually end out roughly in the same voltage regions as when using AVX offset in the first place. Nevertheless, just for "safety" reasons it might be a good idea to limit power consumption anyway.
Oh, and why actually use PL1/PL2? Limiting IccMax achieves the same goal and is much simpler to test/stabilize, or am I missing something?
Well, congrats on this chip, seems to oc very well, but also very high vcore, no?
I wouldn't recommend running that 24/7, far too high. Remember, Maximus boards are about correct on voltage, in contrast to the lower tier boards where you can substract at least ~100mV from the HWInfo reading under full load. Real 1.47V is far too high and I doubt you can keep temps in check with an AIO. Show screenshot under full, prolonged Prime95 small-FFT non-AVX load, that's when we're talking! 😉