Suggesttions on 3820 OC to 4.75 w/ 1.395V. Bios template attached.

[dwillingm]

Thanks to everyone who has helped me so far with my new hardware (HalloweenWeed, Whitepaw,mrmojorisin, maximiza).

I am running stable at 4.75 Ghz right now (IBT on 10 passess at Maximum). It is requiring 1.395Vcore, and hits 73C. I am getting about 109 Gflops.

I am not going to push for 4.875 Ghz, but would like to fine tune my Bios and potentially reduce vcore / heat if possible. Here is my Bios template. Any suggestions? I don't think the 180% CPU capability is needed, but the LLC = high is required.

Extreme Tweaker Menu
Ai Overclock Tuner: Manual
CPU Level Up: Disabled
Bclk freq: 125.000
CPU Strap: 125MHz
ClockGen Full Reset: Enabled
Turbo Ratio: By All Cores
By all cores : 38
CPU Clock Gen Filter: Auto
Memory Freq: DDR3-2000MHz
Extreme Tweaking: Enabled
EPU Power Saving Mode: Disabled
Extreme OV: Enabled
Bclk Skew: Auto
CPU Vcore : Manual Mode
CPU Vcore Voltage: 1.395
VTT CPU Voltage: 1.15000
2nd VTTCPU Voltage: 1.15014
CPU VCCSA Manual Voltage: 1.15
DRAM V (A, B): 1.625
DRAM V (C, D): 1.625
CPU PLL Voltage: Auto
PCH Voltage: Auto
VTTDR Voltage (A, B): Auto
VTTDR Voltage (C, D): Auto
CPU Spread Spectrum: Disabled
PCIe Spread Spectrum: Disabled

DRAM Timing Control
Rampage Tweak : Auto
CAS: 9
RAS to CAS Delay: 11
RAS Pre Time: 10
RAS ACT Time:28
Command Mode: 1

Digi+ Power Control Submenu
CPU Load-Line Calibration(LLC): High
CPU current capability: 180%
CPU Voltage Freq: Auto
VRM Over Temperature Protection: Auto
CPU Power Duty Control: T.Probe
VCore MOS voltage Control: Auto
CPU Power Phase Control: Extreme
CPU Vcore Boot Up Voltage: Auto
VCCSA Load-Line Calibration(LLC): High
VCCSA Current Capability: 140%
VCCSA Fixed Freq: 300
CPU VCCSA Boot Up Voltage: Auto
CPU VTT Switching Freq: Auto
CPU VTT Over-Current Protection: Auto
DRAM-AB Current Capability: 100%
DRAM-AB Voltage Frequency: Auto
DRAM-AB Power Phase Control: Auto
DRAM-CD Current Capability: 100%
DRAM-CD Voltage Frequency: Auto
DRAM-CD Power Phase Control: Auto
PCH Switching Freq: Auto

CPU Performance Settings Submenu:
CPU Ratio: 38
Enhanced Intel Speedstep Technology: Disabled
Turbo mode: Enabled
Power Limit Control: Auto

Advanced Menu
CPU Configuration Submenu:
Intel Adaptive Thermal Monitor: Enabled
Hyper-threading: Enabled
Active Processor Cores: All
Limit CPUID Maximum:
Execute Disable Bit: Enabled
Hardware Prefetcher: Enabled
Adjacent Cache Line Prefetch: Enabled
DCU Streamer Prefetcher: Enabled
DCCU IP Prefetcher: Enabled
Intel Virtualization Tech: Enabled

CPU Power Management submenu
CPU Ratio: 38
Enhanced Intel Speedstep Technology: Disabled
Turbo mode: Enabled
CPU C1E: Disabled
CPU C3 Report: Disabled
CPU C6 Report: Disabled
CPU C7 Report: Disabled

Monitor Settings
Anti Surge Support: Disabled

[HiVizMan]

Nice OC daveo sadly for over 5GHz I needed way to much VCCSA and was obliged to dial it back down. Guess it is just the luck of the silicone draw.

[HalloweenWeed]

dwillingm, do you have Turbo, Speedstep, and C-states working? HiVizMan seems to think:
"No reason to go to the 125 strap. You loose all the Intel built in functions if you do. I for one am a fan of speedstep."
But he was talking about the 3970X too. Just curious.

[dwillingm]

HalloweenWeed wrote:
dwillingm, do you have Turbo, Speedstep, and C-states working? HiVizMan seems to think:
"No reason to go to the 125 strap. You loose all the Intel built in functions if you do. I for one am a fan of speedstep."
But he was talking about the 3970X too. Just curious.

Update: 1.37vcore, 1.175 vtt/vccsa, 1.625 vdimm passed 30 runs of IBT, then failed about 1 hour into prime blend with 0x000000d1.

I have turbo on, but speedstep and c-states off. I have to go with the 125 strap on the 3820, otherwise the best I can OC is 43 x 100 = 4.3 ghz.

I guess I will try a run with increased vccsa at these settings:

vcore 1.38, vtt 1.175, vccsa 1.225, vdimm 1.65

Daveo: my timings are not set to auto, but they are not that aggressive i dont think: 9-11-10-28-1T

[Daveo]

One thing i noticed in the bios under gaming profile 1/2 was the 131.25 (i think) bclk with -3 skew. That, and the ridiculously high voltages. According to Asus, 131 is the sweet spot... i tried it and it did boot fine as for stability i didn't go ahead with the bench tests as 1.55v with extreme llc for 5ghz almost made me fall off my chair. Thank the lord for fast reboots. Though i did make some of my own adjustments to the profile, i changed vcore/vccsa and a few others and it turned out to be stable.

Perhaps its an idea to apply one of the Asus profiles, make some adjustments and work your way back by lowering the values to find min/optimal. You shouldn't get any voltage-related crashes by it being slightly overvolted as opposed to being undervolted.

If i were using gskill, i'd set CR back to 2 and leave ram timings on auto until it was stable at the desired clock.
Might also be an idea to drop your memory ratio down a notch or two, keep that memory controller nice and relaxed whilst finding a stable vcore.

HiVizMan- cheers this board has been great and i know what you mean, after 4.87 i cant believe how much extra vcore is required!

Daveo

[HalloweenWeed]

Daveo: What CPU and mobo are you using? "extreme llc" does that indicate the R2E? That platform is way different. On the RIVE you select memory speeds, not ratios (however in the background it actually is a ratio, it just doesn't say that). The prob with reducing the memory stuff while OCing is then when you get to your OC you may not be able to find the proper setting for your mem at orig freq - it can be very tricky. Sure it might allow you to get to higher OC if temp isn't your limit, but with the caveat of slower mem. The diff between 4.8GHz and 4.6GHz is only 4.3%, slowing your mem to get there is just not worth it IMHO. And what is your Bclck strap?

[Daveo]

I am using a 3820 with a Formula. Extreme load-line calibration, meaning that with 1.55v cpu vcore (asus profile) that level of calibration would spike the voltage up even further than desired- keeping in mind with my own configuration, i get 5ghz stable with 1.47v so it was a little high for my liking. I quickly rebooted to change profiles.

Dropping the memory ratio down a notch is sometimes needed to eliminate memory-side stressors, though the primary reason for doing this is to gain stability at that cpu clock, not for the sole purpose of gaining extra cpu mhz but i didnt mean it in the sense that it must be done to get 4.8 stable. It applies moreso to those running 2133/2400mhz kits with 3820's that rely on bclk to reach higher cpu frequencies.

Past 4.7ghz, 2400mhz just wasn't going to work without a load of voltage and, for little gains.

I am using 125 bclk manually set. It has served me best for higher clocks. 100-105 and 125-129 bclks worked without needing skew, at least to the extent of my testing which has been mainly based on 125 bclks.

Well that's just the thing, with bclking its likely you won't be able to achieve exact original mem freq. This is why i run my 2133 kit @ 2000mhz with tighter timings. I feel it's not really a disadvantage, i only sacrificed 133mhz in exchange for stability at the cpu clock i was hoping to get stable at the time. As a gamer it was a better choice.

Daveo

[HalloweenWeed]

Daveo: Does your rig sleep properly? Does the fans turn off when it sleeps? Does it wake properly, including sound in true 3D games?
I don't think your settings will allow this especially when you turn on SpeedStep and C1E-C6. And I would never recommend any settings to another person that raised the Vcore above 1.45V - you say yours goes to 1.55! You may be fine W/taking chances like that but do you have the right to take those chances W/dwillingm's CPU? dwillingm is the person that pays for it if his CPU gets fried and Intel won't RMA for free. Personally I really think your suggestions are dangerous and you seem not to care what the OP's goals are - he might want to be able to run efficiently at idle too, and use sleep. dwillingm might want to use SpeedStep and C6 - you didn't even ask him, you just come in, assume he wants OC above everything like you, and throw settings in his face without any consideration to what he might want. If you had a little discussion about what his goals were FIRST, that might help; but IMO settings that make Vcore go over 1.5V is a no-no for recommendations anyway, unless the OP has specifically OK'd it. OC isn't everything. IMHO.

[dwillingm]

Don't worry, I am not trying to put more than 1.41 - 1.42 vcore into my chip anyways.

I got it stable finally (over 24 hours of prime) along with 30 runs of IBT. The final settings needed were:

1.37 vcore (this was needed (1.36 = crash)
1.2 VCCSA (this was needed, 1.175 = crash)
1.175 VTT / 1.625 VDIMM (not sure if these could go lower)
C-states disabled (this was needed, enabled them = crash)
LLC = high (this was needed, medium = crash)

I have a question about pushing the multiplier to 38 while maintaining 125 bclk. The bios says that the VCCSA and VTT support bclk over clocking, so should these voltages really need to go higher to run at 38 x 125 (vs. 37 x 125). The bclk hasn't changed.

Same thing for the memory. If I am locking the memory in at 2000 no matter what the multiplier is, shouldn't the memory be stable at the same vdimm / timings when using 37 x 125 vs 38 x 125?

I am sure I am over simplifying this, but would like to understand whats really going on.

If I know the settings required for 37 x 125 to be stable, can I reach 38 x 125 with more vcore alone?

38 x 125 and a little over 1.4vcore was getting too hot for my liking in IBT (like 82C). But in gaming, it isnt getting anywhere near that. I can turn all the case fans up to high, and have more acceptable temps in IBT at 38 x 125 (75C), and then run them the case fans at normal speed for gaming / everyday use while maintaining 38 x 125. Does this sound reasonable?

[HalloweenWeed]

The memory speed appears to be a locked speed, until you raise bclck, and then you see it is actually a multiplier. Try it. Raise Bclck to 101 (or 102) and see what your memory speed does. That said, yes, your mem speed is not changing but as you increase core speed the stress on the IMC increases, meaning you may need to increase VTT as well as you increase core speeds. You shouldn't have to adjust DRAM V or timings.

You are likely to need more VTT. Mine needs 1.3 @4.7GHz. But every CPU batch/mem combo is different. Also you will prob need at least 1.225 VCCSA - if your CPU is like mine. Another thing, if you try to OC to higher core freq using Vcore alone, you will get higher temps. If you can do it by raising VCCSA, VTT, and/or CPU PLL then by all means do that - you will get farther on your OC. Now that I have dropped the "CPU PLL" term, what about that? I have to have 1.9V to get to 4.7GHz, if I reduce it I get errors or BSOD. Play around with yours. Can you reduce it at all? If not, you may need to increase it to get to your next multi.

dwillingm wrote:
38 x 125 and a little over 1.4vcore was getting too hot for my liking in IBT (like 82C). But in gaming, it isnt getting anywhere near that. I can turn all the case fans up to high, and have more acceptable temps in IBT at 38 x 125 (75C), and then run them the case fans at normal speed for gaming / everyday use while maintaining 38 x 125. Does this sound reasonable?

If you never get near IBT temps IRL usage, then why not take it to near the max temp W/IBT? Personally, I take it right to 89. That's my cutoff. Bloomfield CPUs had TJmax 100C. As you know, most ppl took them into the 80s. Some to low 80s, some to high 80s (and a few into the 90s). I feel that the lower TJmax shouldn't mean you should go lower W/OC temp (providing it is 2*C under TJmax). After all, the silicon is not all that different (just tinyer). I think it is just Intel bean counters trying to reduce RMAs, they had a meeting and that's what they came up with - a lower TJmax. The CPU will downclock and save itself if it ever gets to TJmax, it is a failsafe - I have seen this happen (i7-920).

[dwillingm]

My PLL is set to auto. In the Bios it is at 1.88. Maybe I should lock it in at 1.9?

Keeping the VCCSA at 1.2 and VTT at 1.175, I bumped he multiplier to 38 and started raising vcore while running IBT

1.37 - bsod x01

1.38 - bsod x01

1.39 - bsod x01

1.40 - bsod x1e

1.41 - bsod x1e

1.42 - bsod - stable for an hour so far.

1.42 probably isnt 100% stable, but it is getting close. Maybe it could have taken less than a 0.05v to jump from the 37 to 38 multiplier if I had also bumped vtt to 1.2 and vccsa to 1.225.

Thanks HW for all your suggestions and help. I have learned a lot!