5820k cannot alter the CPU ratio or BCLK settings.
5820k cannot alter the CPU ratio or BCLK settings.
Hi everyone,
I've been working really hard to reach 4.5GHz with my i7-5820k but keep experiencing issues whenever I try certain settings.
First, changing the BCLK value to 96, 100, 133 or 150 causes stability at 125, yet RAM speeds drop from 3000MHz to 2400/2666MHz when I adjust BCLK to 100 or 133. I can manage with 96 and 150 but struggle with the others.
At 125 BCLK, I tried various ways to narrow the gap between the CPU's multiplier (4.375GHz) and the CPU cache ratio (around 24x).
2a... I gradually increased the CPU cache voltage up to 1.15v and adjusted the offset by up to 0.200v several times before giving up, since I couldn't get past it.
I also disabled LLC (lv1 = disable), turned off SB Sprectrum, and enabled High BCLK Mode. Still nothing.
Nothing seems to work. No clear reason. My PC is acting like it doesn’t care. I’d really appreciate it if someone could help me get the CPU cache ratio closer to 3000MHz without changing settings.
This has been frustrating.
My current stable speed is -4.375GHz
CPU Vcore 1.270v // LLC Lv3
Thermals: idles 24-31C, stress 66C avg, maxes at 74C.
Playing games like Just Cause 3 and GTA5 rarely drops below 59C after long sessions.
If I change the cache settings at all, I can’t even post.
WHY IS THIS HAPPENING? I don’t understand.
Specs in signature
Increase Crank LLC to full capacity and raise voltage until posting and booting work. Reduce Cache multiplier until stability returns.
Crank LLC should be run at full capacity with increased voltage until posting and booting work. Reduce the cache multiplier until stability returns. LLC is already at its maximum (level 1). The CPU multiplier is currently set to 35 at 4375MHz, but the cache ratio is very low; auto-adjusting it to 24 at 3000MHz works well when the CPU reaches 4375MHz. I’ve found that optimal performance should be within 300-500MHz difference between them. I also tried up to 1.3v boost for the vcore. In CPU-Z, the multiplier is either 12x or 35x with no middle ground. It’s unclear if this is normal or problematic. The system remains very stable. I’m puzzled about why the cache resists changes and why reaching 4.5GHz isn’t possible even at high voltage.
Increase Crank LLC to full capacity and raise voltage until posting and booting work. Reduce the cache multiplier until stability returns.
Could be more effective in increasing the voltage. It's secure to raise to around 1.425V during the boot check. Testing at a lower level and using it regularly between 1.35-1.4V works well.
You might achieve better results by opening up the voltage a bit more. It's safe to try up to 1.425V for the boot test. Using it in a bench and everyday play in the 1.35-1.4V range works well. The question remains whether this is worth it—gained noticeable FPS during 4K recording when you increased from 4GHz to 4.25, then more at 4.375. A jump to 4.5 seems promising for smooth performance. For your CPU longevity, it depends on how well the thermal management handles 4.5; good thermals could keep it running longer even if it doesn’t last as long as stock.
CmdrJeffSinclair responds with detailed advice on overclocking, discussing safe voltage limits, potential performance gains, and the impact of higher temperatures on component lifespan. He emphasizes the uncertainty around exact longevity and suggests balancing performance with system stability.
Jossrik shares insights with CmdrJeffSinclair, discussing potential benefits of pushing voltage levels. He suggests testing up to 1.425V for booting and recommends staying within 1.35-1.4V during regular use. He questions whether the gains are worth it, referencing personal experiences where FPS improved noticeably during 4K recording after increasing from 4GHz to 4.25 and further to 4.375. He notes that while some players see better performance, actual gains in gaming remain limited. Jossrik is uncertain about long-term CPU health at higher voltages, emphasizing the unpredictability of thermal effects. He mentions past experiences with system longevity and suggests a cautious approach, balancing performance hopes against potential hardware wear. He concludes by expressing frustration after a failed attempt and a decision to move on.
I believe the main issue is why you're focusing on the issues from black overclocking.
I believe the real issue is why you're dealing with all the complications from black overclocking. What's the point? I just increased the Vcore to reach 4.5GHz, but it would crash under stress. Someone told me BCLK usually causes problems with high overclocks and needs careful adjustment. That's what got it started.