[SOLVED] Questions about i7 2600k overclock

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

Rumrunner 24

Distinguished
Feb 27, 2014
126
0
18,680
Im trying to buy a little more time before I upgrade my cpu.

I managed to get my 2600k to 4.4ghz by using a +0.05 offset with temps at 55c-63c during heavy gaming and high 20's at idle.

1. CpuZ shows my max VCore at 1.272 during prime95 small fft's
Imo, its not worth the extra few hundred mhz to quickly degrade my cpu.
What's a safe VCore for ever day use ?

I hear no more than 1.35, but others say as high as 1.45
Id like to stay below 1.3.

2.I noticed my the vid goes higher than my max VCore.
HW monitor shows my max Vid is 1.391 (Thats a little scary to me, but Im still kinda of new to this)

Is the cpu is receiving what the vid shows or can I safely monitor the actual VCore with hw monitor and CPUZ ?

Fyi: My cooler is a N520 http://us.coolermaster.com/product/Detail/cooling/hyper-series/hyper-n520.html

Thanks for any help
 
Solution
It's different for different manufacturers. If you are at -0.05 now, just add 0.05 and there's the starting point. A stress test will get you a stable load vcore. Btw intel states 1.52 as max safe. Idle vcore is a different point so you can be unstable at idle but stable at load or vice versa. It's typically idle that's an issue so usually what happens is people using a negative offset and use additional turbo voltage to raise the load vcore higher for a higher oc. You get the best of both worlds; undervolting idle but a high oc.

Llc will also affect vcore and it gets more complicated with a scaling levels. But anyways, just pay attention to vcore til it's stable. I don't know what other settings you changed but you shouldn't need to...
So everything was great until today, I noticed that the speed will flicker between 3.4 (stock) and 4.4 (stable oc) and back to 3.4 It mainly stays at stock though.

Its like the bios isnt saving my settings or something.

Would reflashing the bios help or do you think its something else.
 
Last edited: