Request VCORE to stop when not in use but maintain a maximum of 1.3v during operation
Request VCORE to stop when not in use but maintain a maximum of 1.3v during operation
I tested a 3770k at 1.32v @ 4.9GHz for years. It wasn't a core set OC but a turbo limit set OC with C1-E and C-states enabled, while other relevant OC values were adjusted. Adjusting voltage limits (which affect VID and vcore), setting LLC to 1 step over medium, increasing current limits, and modifying turbo duration all impact the results. The final turbo output remains consistent as long as cooling permits full core operation, and a standard idle mode is retained since nothing is fixed for vcore or core speeds.
I only rely on maximum performance in Windows. That means nothing else affects this. When I adjust my 4.7 over clocked voltage to auto or adaptive, the voltage changes accordingly. The BIOS is handling this as far as I understand, not Windows. I just need it to behave the same way, but never exceed 1.3v. I want to stick with that maximum while still lowering the voltage dynamically like in adaptive/auto mode. I personally don’t like having C7 active during gaming. That’s just not my preference. My main goal is to focus on this voltage behavior I’m trying to achieve... With Windows performance at its top, 4.7 locked, just as before.
The allowable voltage limit for the VRM sending power to the CPU is called VID. The CPU demands a certain voltage, while Vcore represents what the CPU actually needs. CPUs tend to consume whatever they can obtain, based on their requirements. Power consumption is calculated as amperage multiplied by voltage, and the CPU requires a specific wattage to operate effectively—within acceptable limits. That's why current restrictions are often increased for overclocking, allowing voltage adjustments while maintaining power needs.
LLC is an additional voltage boost applied beforehand. As the CPU adjusts to varying loads, it experiences fluctuations in voltage consumption, which contributes to the vdroop effect. LLC is incorporated into the power delivered to raise the minimum voltage threshold, ensuring the voltage remains sufficient during the drop. Since LLC is also applied at the upper end, the overall voltage appears higher than intended.
Adjusting VID essentially manages the CPU's power intake, but it should always be slightly above Vcore by 0.05 volts. It's important to remember that the readings you observe are snapshots in time; they don't reflect the full operational context. For example, a voltage reading of 1.32V might include the effects of LLC.
Think of VID as controlling the CPU's diet—setting it too low would be like telling the CPU it needs only 4oz of meat, whereas the actual requirement depends on what it will actually consume. The difference lies in specifying the exact nutritional content versus general guidelines.
I went through it several times to grasp what it meant. I realized VID was the value the CPU asked for, while vcore was what it actually received. Many of the terms you mentioned, like LLC and SVI2TFN, are unfamiliar to me. In hwinfo64, these aren’t listed unless I missed something.
Right now, with my vcore set to override in my MSI BIOS at 1.3, hwinfo shows vcore as 1.300v (with a few thousandths variation) and VID as around 1.325. When you said using VID instead of vcore, I’m not sure how to do that. In the MSI BIOS, there’s nothing that suggests changing VID unless it’s referred to differently. Maybe the offset mode is what you’re thinking about?
Still, there’s an offset that seems straightforward—specifying plus or minus and the amount—but there’s also adaptive + offset and override + offset, all with the ability to add or subtract. Override just sets a fixed voltage in the BIOS, while adaptive is similar to auto, which was adjusting up to 1.4.
I’m not sure which one I should use. I’ve mostly seen people using offset, except for a few times when I messed up and had to clear my CMOS because I think the offset was too low.
The offset plays a role in VID. A standard offset influences all voltage levels by the specified value. Adaptive offset has a greater impact on working voltages and minimal effect on idle voltages. Override offset seems manual, establishing a fixed voltage. It's likely better to choose adaptive.
Here’s an alternative version of your text:
Trying to reduce the idle voltage isn’t really effective. Enabling C states already brings the voltage down to zero. The monitoring software you use for idle status offers little real value since a CPU in idle mode is typically in C7 at 0 volts about 99% of the time. The remaining 1% doesn’t matter much.
Lowering both voltage and CPU speed to their minimums only cuts power usage by 2 Watts at the wall. Is it worth the effort? The idle CPU temperature remains nearly the same in both cases, reinforcing that there’s no meaningful change in actual voltage or power delivery.
Your focus on just reducing voltage while keeping the CPU running at full speed is misguided. Even if you manage this, the CPU won’t be stable. When a core is active, it requires voltage; when idle, it drops to C7 at 0 volts. Stick with a consistent voltage that ensures full stability instead of chasing arbitrary numbers.
I’ve seen many people searching for the ideal voltage, but most end up with frustrating BSOD problems without any real progress.
The specific reason for 1.3v is that it aligns with the standardized limit for the 8th generation CPU health. Beyond that point, degradation starts to become a concern.
It's true that a CPU operating without issues can last over four decades, but the effects of degradation remain uncertain. It's possible that reaching 1.31v halves the expected lifespan or reduces it from 40 years down to just 40 months, while 1.32v might bring it down to around 5 years or 5 months, or even result in zero reliability. There are no precise measurements available; instead, we must consider that risks like voltage fluctuations, key burnouts, and core instability increase with higher voltages.
From what I understand, the goal is to maximize CPU aging while keeping it stable and functional enough to function as a standard operating system. This suggests moving away from static OC settings and opting for more flexible options, such as limited turbo boosts rather than fixed core or voltage limits. OC voltages are typically set at C0, representing the CPU's resting state before full idle. This is likely the highest voltage you'll encounter. Stability is verified through both dynamic and static loads—Prime95, Cinebench, and other benchmark tools—which simulate real-world usage by combining memory, GPU, core activity, communication tasks, and CPU workloads.