MrDudeMan
Lifer
- Jan 15, 2001
- 15,069
- 94
- 91
I am kind of hoping there is something useful and simple you can tell us. Ever since Intel stopped giving us safeish voltages we have been totally in the dark and unable to really say anything about safe voltages. Obviously its complicated and confidential but its not like we need the process testing details or the design schematics. We just want to set basic limits like 1.3V so that its unlikely that there will be a problem.
That is how we frame it, how do you as an expert in the process and these concerns distill down to the parameters that we have? We are looking for advice not the word of Intel. We don't need official, we just want some guidance.
I definitely understand your point and frustration. As another Intel engineer on these boards told me, citing numbers can be dangerous. The reason it's dangerous is because it gets propagated around as "some Intel guy said X volts is okay" and it becomes the golden standard. That can be bad for the career of the person who released a number (people have been fired over such things) and it's bad for the person who fried their CPU because they got a part that had less tolerance to overvolting. Yes, they could have fried it anyway, but they may have been less likely to try to squeeze the last 25mV if someone on the internet hadn't told them it was safe. See this link for an example. "...degradation starts..." is exactly the problem. I assure you it's happening way before 1.3V because it's already happening at the nominal voltage. I'm not trying to weasel out of providing an answer by saying it's complex because it truly is.
There was actually an internal article about what not to post on public forums this week. It's ironic, actually, because I don't usually post things like this at all.
If your goal is to squeeze every ounce of performance out of your CPU with power and reliability be damned, then it probably shouldn't bother you to go well above the nominal voltage.
If you want a modest overclock with some priority placed on power usage, voltage is important. The amount of energy required for every charge cycle is 1/2 * C * V^2 (C = capacitance, V = voltage). You are going to burn a lot more power for every incremental voltage increase due to how many transitions are happening across the entire die even with power gating. Energy turns into heat because of non-zero resistance and some, though very small, amount of complex impedance.
The best guidance I can give you is to figure out how much overclock you really want. I would then iteratively reduce the voltage as low as possible until instability is introduced. Then increase it until the instability goes away. I know, that's obvious, but it's an algorithm for people to follow who may be new to this.
For temperature, I would do my best to stay well under Tjmax in all operating conditions. Remember the ambient air temperature could fluctuate a lot and cooling solutions are only as good as the ambient temperature will allow. It's also worth noting that the thermal diodes don't always directly measure the die temperature. Some (many) transistors experience higher temperatures than the number that's reported to you.
For voltage, two things are important. If you exceed the dielectric strength of the gate oxide, it's game over probably immediately. If you get close to, but don't exceed, the breakdown voltage, it's probably still game over in a short period of time unfortunately. I actually don't know what the breakdown voltage is on the IVB or HSW processes, so I couldn't tell it to you anyway. Assuming the voltage is less than the breakdown voltage, then it becomes a complex relationship between increased heat and increased kinetic energy in the electrons flowing through the transistors, wires, and vias.
The final thing I'll say is with respect to the OP:
I'm not giving any kind of official opinion by saying this. Personally, 1.389V seems incredibly aggressive and I would never do that to my own CPU.4.8 with 1.389 vcore and gaming temps of 66c.

