What's limiting my Overclockability (E6700)? (pics inside)

StYle

StYle

StYle

Associate
Joined
5 Dec 2007
Posts
8
Hello all,

I've recently bought a new CPU cooler so it was time to get some overclocking done.

Here's the parts I'm working with:
  • E6700
  • ASUS P5W DH Deluxe
  • 600W OCZ GameXStream
  • 2x1GB G.E.I.L. PC2-6400 CL4
  • Thermalright Ultra 120 eXtreme (Scythe S-Flex 1600RPM mounted on it)

Here's a picture of its current state:

oc1jl2.jpg



With an untouched Vcore (auto in BIOS), it runs stable at 3.15Ghz.

I've now manually set the Vcore at 1.3375 and increased the FSB to 320, Orthos gives errors quickly as you can see above.
I set the RAM timings to 4-4-4-12 in the BIOS before, loosened them up to 5-5-5-15 to see if it's any more stable, without any results.


What do you guys think I should try next? (I was hoping to reach at least 3.4Ghz)

Thanks in advance,
StYleY
 
On my E6600 @ 3.4 I had to put my Vcore to 1.45v

So I would suggest upping that - (not liable for any problems that might occur)
 
Thanks for your quick reply.

Upping the vcore really seems to be the only way to get it stable I guess then?
The reason I'm hesitating is because I barely increased the FSB, increased the Vcore from Auto to 1.3375 and it's not stable, expected such a small FSB increase to be stable after I turned the Vcore up a notch or two.


I'll try increasing the Vcore a little more, see how that works out. Be back soon. :)
 
Yeah maybe vcore ... my E6600 is on auto @ 3.6ghz and cpu-z reports it as 1.392, is listed as 1.4 in bios.
A friends E6700 seemed to hit a wall @ 3.2, We didn't spend time tweaking it TBH we just found the max overclock on auto volts that was prime stable. 3.2 it was.
 
StYle said:
The reason I'm hesitating is because I barely increased the FSB, increased the Vcore from Auto to 1.3375 and it's not stable, expected such a small FSB increase to be stable after I turned the Vcore up a notch or two.
Click to expand...

You've got a 500Mhz overclock which is not too shabby.
 
Okay, here's a little update:

I think I've definately hit a wall at 3.3Ghz.

At first it wouldn't POST if I tried putting the FSB any higher than 330.
I then manually set Memory Voltage to 2.1, it posted with 3.4Ghz but couldn't get it stable.
I tried the 3.4Ghz with a max vcore of 1.4125, it's just not stable. (If I put it any higher than 1.1425 it turns into red in the BIOS, there's probably nothing wrong with that but I don't like the looks of it)

I think I'm keeping it at 3.3Ghz with a vcore of 1.4, seems to be perfectly stable.


You guys agree?
 
As long as your temps are fine then don't worry about zapping it with more vcore. I've never encountered a C2D processor that required nice little nudges in a linear relation to clockspeed.

They've always done about 3.something ghz on stock vcore...then a little more voltage for 50-100mhz...then a sudden massive kickarse vcore requirement for another few hundred mhz.


If your temps are good then you can squeeze more out of her! Don't puss out!
 
Okay, I've had dinner and have decided to give it all another go.

Unfortunately, my 'perfectly stable' vcore 1.40 & 3.3Ghz OC isn't as stable I thought.

The Orthos Blend (cpu&ram)-check gave me an error after 7 minutes...?
Still more vcore? --> (Gonna try some more vcore now.)
 
1:1 with FSB.

Running 3.4Ghz @ a vcore of 1.425 now, still getting errors quickly after starting an Orthos-stresstest. :S


Update: The MP has automatically dropped to 6x, CPU speed is now 2042Mhz?

What on earth is going on? I've read something about this before, someone please explain.

oc2su9.jpg


Voltage is fluctuating a lot in CPU-Z aswell.
 
Last edited:
Speedstep, will reduce the multiplier when idle, soon as you start stress testing or
gaming the multiplier will rise to 9x.

Rob

If you want to disable this you will need to disable EIST & C1E.
 
RJC said:
Speedstep, will reduce the multiplier when idle, soon as you start stress testing or
gaming the multiplier will rise to 9x.

Rob

If you want to disable this you will need to disable EIST & C1E.
Click to expand...

This has never happened to me before ?

It's a E6700 with a 10x multiplier.

EIST & C1E are disabled, I can't manually set a VCore with them enabled..


Update: I decreased the vcore from 1.4250 to 1.14125, it no longer uses a MP of 6, it's back to 10, voltage isn't fluctuating either, Orthos-stresstest finds errors very quickly.

I'm hesitating about putting the vcore higher than 1.4125 now because of what just happened. :S
 
Last edited:
Adding more vcore is usually fine, chips rarely get zapped because of increased voltage. I go all the way up to 1.58V with my E6600 (only for benching though, I can never get it stable as my RAM sucks).
 
StYle said:
This has never happened to me before ?

It's a E6700 with a 10x multiplier.

EIST & C1E are disabled, I can't manually set a VCore with them enabled..


Update: I decreased the vcore from 1.4250 to 1.14125, it no longer uses a MP of 6, it's back to 10, voltage isn't fluctuating either, Orthos-stresstest finds errors very quickly.

I'm hesitating about putting the vcore higher than 1.4125 now because of what just happened. :S
Click to expand...

For some reason I thought you had 6600, then yes it would be 10 x if it was speedstep. :)

Rob
 
Another update:

The 'speedstep' issue seems to have fixed itself, I don't get voltage fluctuations or MP drops anymore.

Current speed: 3.4Ghz.
Current vcore: 1.45V.

Been running Orthos for 5mins and counting, gonna try 3.5 in a sec, possibly even 3.6.
 
Keep pushing, Im yet to push upto 3.6 on my comp. But its running so good @ 3.4 im enjoying playing games at the moment.
 
Hmm...


3.4Ghz @ 1.45 wasn't Orthos-stable after all.

Tried 3.5 @ 1.45 anyways but it would barely boot into windows, didn't bother with 3.6.

Am I really out of options? All there is to it now is increasing the vcore till its stable?
 
You must log in or register to reply here.
Back
Top Bottom