This thread is a result of my discussion W/Raja in another thread regarding the updating of his two Overclocking (OCing) thread stickys on this forum. He asked me for specifics, and it has occurred to me I may not be the only one W/good opinions on how Raja should update/revise his OC guides. So I made this thread so all of you could chime in without derailing the other thread.
Raja,
First, there's no mention of Vreg downclocking. If you have a WB on your Vreg, this is not an issue. But for me, I watched my Vreg external temp W/a Raytek, and every time it got >81*C on the hotspot, the LinX Gflops dropped significantly. This was a limiting factor in my CPU OC. You should have a discussion of this in at least one of your guides. Since the RIVE does not pass the Vreg temp info, most ppl have no idea this is happening, and some believe they have made a sucessful higher OC when in fact their CPU is being throttled by the board, due to Vreg overtemp.
Second, VCCSA is crucial to not only your memory speed, but the CPU core speed as well. As you raise your multi, you need more VCCSA, despite the unchanged memory speed. According to your guides, one would think that once you have a working VCCSA for your memory speed you could leave it alone. If you raise VCCSA just a little it allows faster core speeds without raising Vcore and thus cooler CPU temps. It is better to raise VCCSA to get your OC, than raise Vcore - up to a point - and you do that when you get the same signals (such as BSOD 101) as to raise Vcore. The method would be to raise VCCSA when otherwise indicated to raise Vcore, then if that don't work reset VCCSA and then try raising Vcore. I personally would suggest a limit of 1.4V or so - conservatively.
Third, there is nothing about the use of CPU Vcore in the UEFI BIOS guide. Ppl come here from using X58 OC, and think it is similar, and it is not. They automatically select manual Vcore and begin OCing. Many do not know what the implications of that are. I am repeatedly having to explain it to them when I help them W/their OC. They do not know they can get to 4.8GHz W/3930K (and a Vreg WC) with variable voltage, nor do they know (sometimes)
offset = variable
and
manual = fixed.
You should explain it to them in the UEFI BIOS guide. I was able to OC to 4.6GHz W/my 3930K and auto variable Vcore, just by raising VCCSA (and the other settings to remove or increase the current limits). A lot of these ppl asking for help have already raised their Vcore to 1.4V at this point, because that's what they thought they had to do.
My other suggestion is more precipitated from personal experience, so it is more of a soft suggestion, as I am not totally sure of the accuracy:
Ai Overclock tuner: Neither "auto" nor XMP should be used when OCing. I know you did not recommend to use XMP, and you recommended using "manual." But ppl still try to use them when OCing, they are not getting the message. It may be acceptable to use XMP to find your memory settings at stock CPU speed, then hard-select them in "manual" mode - providing they have the newer (2012) XMP tables programmed in their memory modules for SB (quad-channel) use. When the OC is somewhat unstable, upon BIOS POST the settings can get messed up if not set on "manual," causing a worse instability, possibly causing a corrupt Windows build. I think you need to stress this a bit more as ppl are not getting the message.
Thank you Raja, and we do appreciate your help.
i7-3930K; Asus RIVE; G.SKILL Ripjaws Z 4x4GB DDR3 1866; MSI 7870 2GD5/OC; Crucial M4 SSD 256GB;
Corsair 1000HX; Corsair H100, 4x Excalibur 120mm PWM CPU Fan p-p, AS5; SB X-Fi Titanium Fata1ity Pro;
Dell U2412m IPS 1920x1200; Cooler Master HAF 932 case; Tripp-Lite OMNIVS1500 UPS fully Line-interactive.
(EVGA site: )
And I have a second (wife's) computer,
Eve.Overclocking is useless to me if it is not rock stable.