Pages

Showing posts with label Input Voltage. Show all posts
Showing posts with label Input Voltage. Show all posts

Saturday, September 21, 2013

[Article] Haswell, VDroop and Load Line Calibration

When Intel CPUs are stressed with heavy load, the Core voltage (Vcore) drooped slightly to relieve the voltage controller on the motherboard. We call this VDroop. It is not a sudden drop, but it is maintained throughout the period the CPU is stressed, hence is was not called a VDrop.

The amount of VDroop depended on how much Voltage the CPU was using up. Thus, when the CPU was overclocked - meaning, the Vcore was higher than nominal figure, you could see a bigger VDroop. While this was according to Intel's design specification, it was not a good thing for overclockers.

The CPU becomes unstable when the Vcore drops, especially when it is under load. Besides, all these overclocking boards had way better voltage regulating circuitry and the sudden increase in power draw from the CPU was nothing they couldn't handle. Thus, motherboard manufacturers did something to counter the VDroop. The common term they use is Load Line Calibration. I'm not sure how it works exactly, but it seems to add up more volts when the Vcore droops. Usually we can decide how much voltage the motherboard should counter apply by selecting the level of LLC, so it is not really "intelligent". Further, I'm sure the other voltages drooped a bit as well, but not in significant amounts. It was the Vcore that everyone was concerned about.



1st of June, 2013 arrived and came Haswell. Haswell brought a lot of new things to the table. Voltage regulation was one of that. Instead of depending on the motherboard's voltage regulator to split the +12V into individual component voltages such as Vcore, Vmem, VCCIO, VCCSA, Uncore voltage etc and input them separately, Haswell asked for only one specific voltage from the motherboard. It's called the VRIN or VCCIN or Input Voltage. (It's about time they all agreed on a common term!). In Haswell, there is a voltage regulator inside the CPU (called FIVR) and that's what takes care of splitting this input voltage to different individual component voltages. They have done this to improve the idle power consumption. Dropping 12V down to 0.xxxV is difficult for any voltage regulator. But it is much easier when you drop it from about 1.8V. The default VCCIN is 1.8V. 

VDroop is still there with Haswell. But it doesn't apply to Vcore like previous generations. It applies to the Input Voltage - the only voltage inputted to the CPU from by the motherboard. The default Input Voltage is high enough so that for a casual overclock, you don't have to worry about VDroop. But at high overclocks (which means, many component voltages will be running above stock voltages) you will run into issues. I think, you will see two phenomena caused by lack of Input Voltage.
  • First one is, that the FIVR will not have enough juice to do its magic. This will cause a dip in any of the volts that would result in instability of the CPU. You will almost always get a BSOD with 0x124 stop code. This is probably why most people say that increasing the Input Voltage allowed them to use a less Vcore to stabilize the CPU.
  • Second phenomenon is that the FIVR will completely shutdown. This will cause the PC to reboot out of nowhere. You won't see a BSOD or any warning. It will be as if the power went off and came back on.
I've seen some reviewers say that you don't see VDroop on certain motherboards even though there is no LLC setting. They say by looking at the Vcore droop. But Vcore doesn't droop with Haswell. They are looking at the wrong voltage. You have to monitor the Input Voltage. Then you will see that LLC still is required. But since it doesn't affect the Vcore directly, if the Input Voltage is high enough, you will be able to get away without fiddling with the LLC.

Sunday, August 25, 2013

[Article] I give up. Have to settle at 4.3GHz with my 4770K.

In a previous post I mentioned that I was able to clock my new Haswell Core i7 4770K chip to 4.3GHz and I was planning to clock it to 4.4GHz. After trying for a week or so, I couldn't get it Prime stable at 4.4GHz below 1.3V Vcore. My CPU is a dog. It doesn't overclock well at all. In fact, it is a well below average chip. That's sad. I lost the silicon lottery.

But it is not the end. There is a few more tweaks I can do. For example, right now the RAM is at 1600MHz with XMP timings (9/9/9/24/2T/1.5V etc.) and cache ratio is at 39x with 1.075V. I think I can tweak the timings a bit and increase the cache ratio to 41x or so. 43x is ideal but will be a long shot  I guess. I would definitely have to increase the Un-core voltage to somewhere around 1.2V to get near 4.1GHz. But that doesn't add a lot of power so I should be alright. Maybe I could tweak the voltages a bit. Perhaps lower the CPU input voltage to cut the temps by a degree or two. I could even play with the BCLK as well. Perhaps put it to 105MHz with the multiplier dropped to 41x? That might improve the performance slightly. Something is better than nothing, right? 

Anyways, I am really disappointed with my CPU. There are people who have chips than can clock to 4.9GHz with just 1.25V. I have a great motherboard - a motherboard made for overclocking. But me not being able to get higher than 4.3GHz overclock is not the board's fault. It's the CPU alone. I probably can get by with 4.4GHz at something like 1.29V and be stable in real-world work loads. (Heck, I played Crysis 3 campaign from beginning to end with just 1.28V and didn't encounter a single crash). But in my head I know that it is not 100% stable and it might crash when I least expect it to. That is not something I can live with. Hey, it's just 100MHz which is even less than 2.5%.

One thing I should tell is that it was almost always the in-place Large FFT test that crashed when I tested for stability at 4.4GHz. Playing with the voltages other than the Vcore didn't made it more stable. It just needed more Vcore. When I kept on increasing the Vcore, the duration until Prime95 crashed lengthened, which means it was Vcore starved. 1.3V is a lot of volts for Haswell, no thanks to Intel cheaping out under the hood. Bastards!

Funny thing was that I could run 10 passes of Intel Burn Test at very high memory usage at 4.5GHz with just 1.280V Vcore. Intel Burn Test might be an indication of stability, but it is way inferior to Prime95, even though the temps while running Intel Burn Test is much higher than when running Prime95.

Here's are my current settings for 4.3GHz.
  • Vcore: 1.235V manually set in BIOS (1.248V max recorded in AISuite III)
  • Un-core multiplier: x39 (AUTO)
  • Un-core voltage: 1.075V manually set
  • RAM speed: 1600MHz
  • RAM timings: 9/9/9/24/2T
  • RAM voltage: 1.50V
  • Extreme Tweaking: Disabled
  • EPU Power Saving Mode: Disabled
  • Everything else: AUTO
Now, I haven't run adequate stress tests. I will do that after tweaking the un-core and the memory timings a bit.



Related Posts Plugin for WordPress, Blogger...