This is all quite interesting, but as a (so far) AMD user could someone explain the terms like, VCCIO, CPU PLL, Offset Volts, IntelME, VTT, LLC, etc without my wading through a bunch of OC forum posts? Thanks! Looking forward to the Intel jump in the near future.
Vccio is equivalent to Vtt , the memory controller voltage. Sometime you have to raise this for lots of memory or higher voltage memory or overclocking memory. It used to have a more important role before Sandy Bridge, when overclocking was achieved by varying the multiplier and the BCLK. With Sandy Bridge it is all multiplier - unless you are nuts and want to overclock your memory.
Intel ME is Intel Management engine. Some power management I thin but mostly provides custom bios config of network etc for IT shop.
Load Line Calibration: compensates for the drop in Vcore under load in an attempt to keep that voltage constant. However, with it enabled, voltage transients when load suddenly changes can exceed the chip maximum voltage
CPU PLL - Phase Locked Loop: Keeps the multiplied frequency stable and locked in-phase with BCLK.
Offsetvoltage: Instead of an absolute voltage, you provide an offset that is applied against the VID voltage. You need this for the power management to function properly so that when frequency is lowered, the voltage will be lowered with it and vice versa - instead of remaining fixed absolute voltage.
Last edited by GeneO; 01 Mar 2012 at 18:07.
Yes gary, the first thing you have to do is forget everything you ever knew about AMD. This is a new ballgame even for Intel, which is what Prof was saying. I still don't understand most of it. The only thing I know, is leave the FSB alone, unless you particularly like the color Blue.
I would also like to add the Load Line Calibration may be refered to slightly diffrently depending on the Motherboard.
My eVga board for example just has the Options: With vDroop or Without Vdroop.
Where Without Vdroop would be equall to having Load Line Calibration enabled.
It should be pretty easy to figure out though even if its called something slightly diffrent.
In a nutshell - The point is that you can
There's no denying that at stock speeds, these machines are plenty fast as is for the vast majority of tasks.
I personally do it primarily because I enjoy the challenge. It's a hobby. The added bonus is that through my own trials and errors, I can speak from experience when helping others, which I like to do where I can.
I also play games and I like to be able to run them at optimal IQ and speed. Some games that are either poorly coded, or single core dominant (often both) do benefit from overclocking. FPS dip vs smooth no FPS dip.
Brute force OCing can also often make up for poor coding. Even with a decent single GPU overclock, it can be the difference between 90% GPU usage vs 99% GPU utilization which results in an overall higher minimum and average framerate with higher IQ settings.
One example is GTA IV. It's notorious for being a poorly coded port. Between a GPU overclock and a hefty CPU overclock, I can actually run this game completely maxed out at close to 60FPS + vsync at all times. There is a vast difference between 60FPS and dipping below 30FPS.
Basically, it's a personal choice. If you have no desire not to, don't. If you do - then you can :)
*
I've dropped back to 4.7 for 24/7 because 4.8ghz would sporadically BSOD during low load transitions. Investigations continue
But 5ghz/5.2ghz, even 4.8ghz is really not worth a 24/7 pursuit (unless running multi high end GPU's)
Good for shits and giggles but the cons outweigh the pros.
As Gene mentioned, no - you're perfectly fine.
It would be of benefit if you were trying to really tighten your timings etc, but your kit is performing great as is and you aren't going for a high 5.0-5.2ghz OC.
The option to up it is there should you try to OC/ really tighten the timings but as it stands - it's all good J :)
*
I've done further reading including posts from Asus and G.Skill techs and real world degradation reports from experienced OC'ers on OC forums. The average result is that it's still the vcore at 1.5+ that's the biggest cause for chip degradation. 1.6v is quick, 1.5v not as much.
Mid 1.4 is a mixed bag.
As previously mentioned, a VCCIO of 1.2 is the 'max safe' limit and DRAM volts of 1.7 is the max DRAM limit. My re-reading just reinforces that. Intel specs are primarily intended as a guide for 'zero' degradation issues.
Since only 'hardcore benchers' will be using DRAM volts of 1.7, a VCCIO/VTT of 1.2 is also unnecessary for the average user.
For 1.65v users, a VCCIO/VTT of 1.15 is fine.
For 1.6v users, a VCCIO/VTT of 1.10 is fine
For 1.5V users, a VCCIO/VTT of 1.0 is also fine.
As long as it's within the .5v variance, it's all good. So if you're using 1.5v DRAM and a VCCIO of 1.05, even 1.10 it's under the .5 variance
A lot of the P67, Z68 boards tend to default between 1.0 and 1.10, so it's not an issue for most. Only users of 1.65v kits should take extra care to note what their VCCIO/VTT is set at. These boards also tend to fluctuate, even with a manually applied voltage, so a double check is worthwhile.
Also as mentioned, when running more than 8GB ie 16GB, a higher VCCIO/VTT is recomended to ensure that the RAM runs as close to it's rated speed as possible.
It's the same principle on previous sockets where the more DIMM slots filled, the more NorthBridge voltage was required to maintain stability.
*
Actually, the more I think about it, the more I'm thinking it's not as badly performing as first thought.
HT on is an automatic 5c-10c temp increase, especially under IBT.
What is your current/average ambient temps?
As already mentioned, the bouncing vcore is the vdrop (voltage drop) and offset in action. IIRC, LLC 5 is similar to 'off' (following intel spec) so voltage fluctuations are quite normal, particularly when using the offset function.
Ostensibly, the offset function either + or - uses the chips stock VID (the voltage factory set to guarantee for supplying sufficient voltages for the chip to run at rated Stock speeds) as a base voltage which is then adjusted depending on the overclock/load used. A + offset 'adds' more vcore, the - offset reduces the vcore.
In conjunction with the offset setting, LLC adds another layer of fluctuation.
When set to low/off, the vcore fluctuates more. When using a higher LLC, it 'forces' the vcore to maintain a stabler voltage with less fluctuations. The downside to a higher forced LCC is that any 'spikes' can overspike the voltage which has a higher potential to cause damage.
Using a fixed vcore and high LLC helps maintain a more constant voltage. Some boards like the Asus Z68 range actually work beetter with a lower LLC and the offset function.
Depending on target OC, it's better to use a low/no LLC. The trick is managing how high the vcore spikes under high load and how low it drops during the power saving states. Often an idle x124 BSOD crash is caused by insufficient vcore as it cycles through the varying power states. (If enabled)
Would one of you masters have a look? CPU running at 100% on LG F1
He's an Intel user and I don't know what to tell him. His issue is that he can't get his SpeedStep to throttle and boost his CPU.
[QUOTE=smarteyeball;1820381]You should not even go near those voltages you mention IMO. If you go out of the range of 1.05 +/- 3% then you can shorten the lifetime of your processor. I wish people would get this (not referring to you but whoever said that was safe) - staying in Intel's absolute maximums doesn't mean it is safe, it means it won't immediately croak. What is safe is staying within the DC operating ranges. The Intel DC operating range for DRAM voltage is 1.425 to 1.575 for Sandy Bridge.
In fact, where do those safe 1.2V VCCIO and 1.7 v DRAM voltage numbers come from? Intel apparently doesn't even publish absolute maximum voltages in their spec anymore (I can speculate why), just DC operating, so somebody probably pulled those numbers out of their butt or are basing them on the previous gen maximums, which were for 45nm chips (vs 32nm Sandy Bridge) and could probably stand more voltage. Since the processor hasn't been out but a year - nobody can tell you for sure what are the long term affects of operating out of the DC window on voltages.
Except for the Vcore, which has a wide range, I think it is best to stay within Intel's DC specs for everything else and to avoid using LLC if you can, because that is also out of spec.
Last edited by GeneO; 02 Mar 2012 at 16:24.
The 1.2 VCCIO and 1.7 VRAM has come from internal testing by certain companies ie G.Skill, Asus and even intel. It also includes findings from the serious benchers.
As you say, the chip is less than a year old and nobody knows for certain what the true max safe limits are. I personally wouldn't run my RAM and VCCIO that high. It's also why I'm working on lowering my DRAM volts.
If the DRAM voltage absolute max is 1.575, then there's quite a few RAM manufacturers up for some serious class action lawsuits since there are a wide variety of 1.65V kits available :)
I agree mate. However for most overclockers, if the intention is to keep a chip for 10+ years, then they wouldn't be OCing to begin withstaying in Intel's absolute maximums doesn't mean it is safe, it means it won't immediately croak. What is safe is staying within the DC operating ranges. The Intel DC operating range for DRAM voltage is 1.425 to 1.575 for Sandy Bridge.
Also agree. Part of that is because because intel don't release the limits any moresomebody probably pulled those numbers out of their butt or are basing them on the previous gen maximums, which were for 45nm chips (vs 32nm Sandy Bridge) and could probably stand more voltage. Since the processor hasn't been out but a year - nobody can tell you for sure what are the long term affects of operating out of the DC window on voltages.
However part of my reading has encompassed threads with users who who intentionally pump X amount of dangerous volts on various settings 'just to see' what causes what and what causes degradation the quickest.
The majority are using 1.5V kits anyway, so staying within intel specs is a moot point as they already are. For others like myself who technically fall outside of the intel spec, I'm simply trying to offer advice that helps minimize any 'quick degradation'.
Apart from some playing around at 5.0ghz+, I personally don't use LLC either.and to avoid using LLC if you can, because that is also out of spec.
It really comes down to the "if you can't afford to overclock - don't". But if you're going to take the risk, minimize where you can.
I'm putting in a request for smarteyeball to write a Tutorial on this. I promise to rep you 'til the cows come home if you do.
