OCUK Sandy Bridge, SB-E and Ivy Bridge 5GHZ Club

Well my new OEM cpu is quite different from my normal one. It does a higher suicide clock hitting the 55 multi. I have managed to run up to about 5550MHz (just)

Despite it having a higher clock it requires quite a lot more voltage to be stable at lower speeds. for 4.8 my main chip requires 1.3v this one needs 1.4v

I need to do a bit more learning but on overall I still think my first chip is better hitting 5.4 and running lesser speeds at lower voltage.
 
Hows the tweaking going simon? Still battling on with mine, the temps are so much higher with HT on I'm finding, around 7 degrees difference at load when turned on. Does this sound about right?

When I get a nice stable base of 12+ hours, I'll reseat the chip a few times to try and get an improvement, but cant see me getting this chip to 5ghz whilst staying under 70 degrees

Currently testing 4.9 ghz and am 2 hours into prime with a vcore of 1.385 giving a load v of 1.400

And bobbydigital, thats what I have done for the exact same reason. 5ghz just sounds right :D Have you tried the superpi run at a lower voltage?


Right I have given this OEM chip a fair bit of time tonight and I got it to 5.590MHz but not with any stability and it needed over 1.6v to get there. So although it's a better headline score it is not really useable.

I can't get it prime stable at 5GHz and even struggle to get Prime stable at 4.8GHz :(

What it does do is run prime at - 0.125v at 35 Multi that's 0.88 to 1.070 in CPUz switching between 1.6Ghz and 3.5GHz. Which is very nice thankyou, so this OEM chip is going in the NAS / Media Center box (Asus P8H67 Pro). Will do the switch tomorrow and put my 5.4GHz chip back in this machine.

Then I supose it's a case of waiting for a C Batch to come along :)
 
My OEM 2600K is on it's way back for RMA. It runs perfectly on the P8P67 Pro although the voltages are higher than I would like the top clock is good. But it will not run in my P8H67 Pro which is what it was brought for... I'm presuming the Intergrated Graphics are bad.

Anyway, so i'm sat trying to decide what to do... order another OEM or wait to see if some C batch turn up - although it seems the C Batch is far from a guarantee, really just the chance of lower volts ant temps.
 
The idea was that to join, was a challenge, but not too difficult to put people off.
I also order the results by the super-Pi score, so 5GHz is just to get in... it's still worth making the effort to move up the ladder :)

Remember that when I set the challenge the Bioses did not have PLL Overvoltage and before that change 5GHz was actually very difficult.

I'm sure some people will still disagree and be finding 5GHz quite a challenge.
 
Just wondering what clocks are IBT load temp 24/7 liveable like under 80c IBT load temp.
You guys should run IBT custom ram 8 threads 50x
If people want to run sandy bridge@5Ghz stable, then they should use IBT with 4 threads for i5 2500k and 8 threads for i7 2600k manually set with custom stress level and choosing 'free' memory from windows task manager and then run the program for 50 passes. Check your GFlops values and coretemps;)


There is a world of difference between getting a headline MHz with Super-Pi 1M score against a test where the machine is stable. the danger with pushing for a stable IBT overclock is that people will put extreme stress on thier components for a period of time that is not really sensible.

Personally, with my 2600K, I'm happy to run 1.5v and get a headline number if it means running the machine at that voltage for 10-20 minutes, but I would not run at that voltage or speed for hours. My happy balance is 4.8GHz at 1.35v for long term use and extended benchmarks.

As I said in the first post, we could have a Prime95 or other serious test as another thread, but thats not what this one is for... its supost to be fun and with fairly low risk.

Enjoy it for what it is.... and start another thread for a stable test if you want to.
 
It is a little cooler, but nothing to really notice.
In many ways it acts the same as my 5.4GHz chip. Everything felt the same up to 5.2 where one just does it and the other wont. I did notice that at 4.8 and 5.0 when I used Prime the 4th core always failed well before a BSOD so I think it may have one core that's weaker than the others... However I tried running 3 cores in the bios and it made no difference.

I'm going to stop trying and wait till the new revision Motherboards then try again.
 
I have been thinking along the same lines - I have a P8P67 Pro and was thinking of going for the Maximus, but the more I think about it the more I come to the conclusion that it will make no difference to the overclock.

Anyway i have an RMA number from OCUK for the Pro and am just struggling to press the button on the replacement board because of the price... I'm hopeing that it just might be a today special tomorrow morning :) HINT HINT
I'm just going to stick with the P8P67 Pro.

If the B3 version still has the same issues with Raid 0 then I will spend what I save on not upgrading to the Maximus on a Vertex 3 single drive later in the month.

I also have another retail 2600K sat at the RM sorting office for me to collect in the morning (you never know 5th time lucky)
 
Last edited:
What issues with raid 0 mate?

I have 2xVertex 2e 2.5nm 50GB drives in Raid 0 on the SATA 6GB slots and when I boot from cold it sees one drive wrongly (as a sandforce and only 1/2 size 25GB). I have to reboot upto 20 times before it sees it correcty and therefore boots from the Raid array.

The drives are both fine.. it is the motherboard causing the issue.
 
New one is L101B360 #3343 so its a very recent batch.

Umm this one seems quite nice. Only done a little testing but it allows the 55 multi at 100 blk in windows at 1.44v bios. Not stable, but looking promising.

Left it running prime at 5GHz 1.325v for a few hours but came back to a BSOD, but i don't think its far from stable.

That would make this rather a good chip if it can do low voltage at 4.8 / 5.0 GHz and yet still allow the 55 multi + Normally they permit none or one but I have not seen one do both before.
 
Ok 5.5GHz at 1.55v SuperPi run, cant be bad.
Have to admit i'm struggling to go further at the moment despite the voltage, determined to get a 6.6s Super-Pi score on the board though

5508MHz-SuperPi.JPG
 
Back
Top Bottom