Official GIGABYTE Forum

Overclocking, Benching, Events, Tweaking & Modding => Overclocking motherboards with Intel processors => Topic started by: noodi on May 07, 2011, 01:32:13 pm

Title: P57 UD4 + i7 2600k OC - bad chip or I missed something?
Post by: noodi on May 07, 2011, 01:32:13 pm
Hi all,

I got i7 2600k on gigabyte P67 UD4. 2x2gb ddr3 1333mhz exeram EP3001A (oc one)
Cpu is watercooled with EK suprime HF, triple rad with 3 noctua p12's and a DC4 pump. idle temps are 29-31, max load up to 60-61.

Bassicly I want a stable 4.5ghz HT on oc.
I just cant get it. Every time linx with avx commands stops and I get BSOD 101 eror (more vcore)
My vcore is 1.375 already, witch is wayyy more then needed (other chips do 4.8ghz stable).

Vram is 1.64 runing 1600mhz cl9
max TDP is 140w
LLC on
turbo is off - so manual multi is 45x
Every other adv. cpu setings is off.
I tried incresing every other voltage by few steps - nothing..

What am I missing? Cant be that bad chip..
Title: Re: P57 UD4 + i7 2600k OC - bad chip or I missed something?
Post by: Dark Mantis on May 07, 2011, 02:07:05 pm
Hi and welcome to the Gigabyte Forum.

All chips are different and so you can't expect the chip you have to behave as well as the chip next to it. That said I wouldn't have thought you would have had a problem reaching where you are with stability.

I haven't had much experience with the 2600K but I have played around with the 2500K and that seemed to clock very well. To be fair I did have the Engineering Sample but even so I wouldn't have expected much difference.

Have you tried loading Optimised BIOS Defaults and starting fresh. You should be able to take it most of the way just on the multiplier. Your Vcore seems a bit high.

What is your default memory timings and voltage ?

Check this out for more info:

http://forum.giga-byte.co.uk/index.php/topic,4072.0.html

Title: Re: P57 UD4 + i7 2600k OC - bad chip or I missed something?
Post by: noodi on May 07, 2011, 04:42:05 pm
def memory is 1.5v 1333mhz with cl9 :P
I read all guides and tips for OC it..
Must be memory, il try at def.