So, in the real world the voltage will under or overshoot as the CPU is asked to change it's load. These over or under shoots are what causes instability and the overshoots, in particular, can be damaging.
This limits the voltage increase possible and therefore limits the possible overshoot. Blue line. However, if your CPU needs the orange line for a certain OC you can see, that the protection mechanism of Vdroop limiting the voltage would cause the OC to fail.
So, you are given control over Vdroop. By setting LLC levels you are adjusting the level of the safety mechanism. Essentially, moving the blue line up in steps Hope that helps. Last edited by Arne Saknussemm; at AM. Originally Posted by Arne Saknussemm. Assuming that BIOS follows the general settings LLC 1 would put you close to the Blue Line LLC of 7 should limit the voltage droop to near zero Of course, at LLC 7 the overshoots you cant see will be high.
You have to understand that you can't see the overshoots in software Last edited by evo4ever86; at PM. But we're talking about ringing on the supply lines, LLC cannot respond fast enough at that scale.
It takes an oscilloscope to see it. I know what issues LLC creates. The little spike is not going to kill the processor in any time that you care about it. Vdroop isn't actually designed to prevent "overshoots". Otherwise, those pentium 3's would have been frying to death at 1.
It's designed to keep the processor within a power envelope. The processor drops the voltage on load to keep itself within TDP. It's about power management. While true, that vdroop is supposed to tighten transient voltage tolerances, this is for processors running at STOCK speeds. What everyone in the world seems to completely forget, is something very basic: If there is a 0. With vdroop, for a target vcore of 1. But in order to do that, you have to set 1. So now you're feeding it an unhealthy constant 1.
It's much better to have LLC give the processor a 1. Vdrooping is perfectly fine if you're running stock or running a low overclock without wanting to change the voltage. No harm in doing so. Unless you want to put extremely high idle volts into your CPU Last edited by Falkentyne; at AM. Originally Posted by ProtoTraveler. Well, you can't just "turn off" vdroop, that's for sure.
You can turn off the BIOS features that help reduce it, that's not a very good idea though. SirMaster 2[H]4U. Joined Nov 8, Messages 2, I run my i7 at 4. I set 1. Joined Nov 13, Messages 7, CrayMan n00b. Joined Mar 23, Messages I leave LLC on for my i, i and i builds.
I like the idea of getting more life out of cpus. Zero82z Fully [H]. Joined Jan 20, Messages 27, CrayMan said:. Yeah I decided against it on my current board.
Enabling LLC caused the voltage under load to go up which means I needed more voltage than necessary under load to keep the cpu at idle speeds stable. That caused power consumption to go up quite a bit and temps to skyrocket. I don't remember it being so bad on my UD3. Zero82z said:. LLC will technically reduce the life of your CPUs while overclocking in exchange for keeping the average voltage closer to the level you set it to.
BababooeyHTJ said:. It's the wattage that kills not necessarily just the voltage. Your cpu doesn't draw much while idle. Actually, it is the voltage that kills. CPUs are semiconductor devices, and applying too much voltage will damage them. Not necessarily, more voltage seems to equal more wattage. Thats why I have a feeling that a higher voltage under load is worse than a higher voltage while idle.
More voltage does mean more power, but that is not a danger to the CPU. It doesn't really matter if the high voltage is while the CPU is idle or at load. What matters is whether or not the voltage is within safe limits for the CPU. If it is higher than that, then it will cause damage. I think that the higher voltage under load that I seem to need to use with LLC on my current board is the riskyer part.
What is this theoretical safe point and how does it relate to LLC? Voltage is what kills CPUs.
0コメント