Cpu core/cache current limit max: 400
Long duration package power limit: 253
Short " " " " : 253
IA CEP: Enabled
SA CEP: Enabled
Global core svid voltage: adaptive mode
Offset mode sign: -
Additional turbo mode cpu core voltage : auto
Offer voltage : 0.0500
Undervolt protection: disabled
This what i need to do to give this ago?
If I set the voltage limits this will lock any spiking ?
Please do not assume that what I write is correct, it is just what I have picked up from various videos, some posted by BZ.
These types of voltage spikes, seemed similar to me of what Nvidia had as issues with the 3000 series GPU's, noted when my 3080Ti at the time would cause the OCP on the PSU to switch off the whole system, is not related to any limits that you set. But, IIRC, it was related to when the CPU would need to ramp up core and MHz limits as the demands for it increased due to workload. As the voltages were being raised it would initially cause a momentary spike in voltages beyond that which was set and only noted, as mentioned, when being scoped. I think there seems also to be a flip side when the work demand reduces then there is a low dip, somewhat mitigated with LLC control, where a PC could crash due to the drop of voltages being too low.
There also seemed to be a situation where these CPU's were calling for more voltages than they needed during light work loads.
This seems to have been covered here with my motherboards final BIOS update...
- Checksum : 5689
- Introduce the "Intel Default Settings" and enabled as default
- Introduce microcode 0x12B as the final mitigation of 13/14th Gen desktop processor Vmin Shift Instability issue according to Intel official
i. 0x12B encompasses 0x125 and 0x129 microcode updates, and addresses elevated voltage requests by the processor during idle and/or light activity periods.
ii. microcode 0x129 (August 2024) addresses high voltages requested by the processor.
iii. microcode 0x125 (June 2024) addresses eTVB algorithm issue.
You could copy parts of that and start to search for a greater explanation if you needed.
What I was not able to find, conclusively, is if making any, or what, changes at all to the Intel default BIOS settings could affect those Intel fixes as, BZ suggested they could do just that.
I got the impression, like what has been happening with the damage limitations being done by Intel with Arrow Lake, is that things get mentioned and then, largely, the tech press move on to something else.
Perhaps, with Arrow Lake, moving on to something else is not a bad thing.
Last edited: