climbing the Ghz ladder... sort of

[stopthekilling77]

Hey all! I'm doing what I've been putting off since I last killed my CPU... overclocking past the 3.0Ghz mark.
After an evening of learning trial-and-error and having various degrees of disappointments... I've made it to the 3.1Ghz mark Now this amazing feat was tough and I would like to thank some people...

No wait. #$@#ing 3.1Ghz after 4 hours of trial and error? NO WAY!
So here I'll outline my issue with this 3.1Ghz wall I'm at. I am STILL LEARNING how to OC and I'd appreciate some patience (Most of what I've learned has been from the overclocking guide by graysky )

So I started out with 3.0Ghz, stock everything else. Memory/FSB is unlinked, Vcore @ 1.3500v, NB voltage @ ~1.33v and now I'm at 3.1Ghz with these specs:


I ALMOST get to log into XP with an FSB of 1575, Vcore at 1.375v, and NB at 1.50v (3.15Ghz, real FSB of 393.75 versus how my BIOS does it) but it hangs at the login screen.

I'm a bit frustrated because I know chips are all different, but this is a B stepping, G0 revision E6750... I expected a tiny bit more out of this chip.
Also, my RAM kit, Mushkin DDR2 800 with Micron D9 ICs, are loosened up at 5-5-5-15 and are steady at 2.0-2.02v and have passed Memtest86 v 1.70 test 5 (thanks Alathald) )

I'm wondering just where I should go from here. My last E6750 made it to 3.4-3.5Ghz no sweat without even budging on the Vcore (before I found out one of the cores was bad)

So... what's next for me?

[DMB2000uk]

What's next? Break down in tears...

As unfortunately it looks like your last CPU was much more suited for overclocking. On a random CPUz screenshot you posted a while back with your old CPU it was showing 1.232v vcore (yeah i deliberately went looking). Your current stock vcore is nearly 0.1v more than that, which in terms of CPU's is a lot. The 1.32v~ vcore is about as high as intel will push them with stock volts before they bin them down to the next CPU category. My E6600 was the same, which meant I ran it at 3Ghz most of the time as going much beyond ~3.2 Ghz took the voltage up exponentially, which meant it just wasn't releasable to run it that high.

All I can suggest now is to try throwing more volts at it until you aren't happy with the volts its running at.

Try bumping the vcore another notch and see if it stabilises your 394FSB clock.

1.4v - 1.45v is the max I'd go with air.

Dan

[martini161]

oh so you thank alathad but not me? i see how it is that thing i was telling you about last night may be called cpu vtt, cpu fsb or something else

[stopthekilling77]

hahaha btw i found the cpu vtt, it wasn't with the other options o.O go figure right? what should i do with it?

and @ Dan, i guess i'll keep at it a tiny bit more, but if i have to live with 3.1, I may just go back down to 3.0 to take all that stress off the chip : sigh :

[martini161]

well from where did you buy the chip and when?

[stopthekilling77]

Just to not let that question go unanswered, the first chip was bought from Newegg in August 07, it was RMAed early this year.
ANYWAY, I did some thorough reading of graysky's guide, looked at the Intel specs for my chip, and I decided to play within 1.4v-1.5v for the vcore.

More to come soon, I'm running Prime95 right now at 3.0Ghz as my 3.0Ghz and 3.1Ghz OC were both unstable with the settings I had used last time.
I'm determined to get as much out of this chip as I can, aiming to push up to 3.33Ghz and I'll be happy.

[stopthekilling77]

Okay, so I'm making a little bit of headway.

Shots:

cpuz_3150Mhz.PNG (30.52 KiB) Viewed 5736 times

hwmonitor_3150Mhz.PNG (45.06 KiB) Viewed 5736 times

I'm testing at 3.15Ghz now with those specs. Assuming I test okay in Prime 95, what would be the next step to getting that 3.33Ghz OC that I want?

[stopthekilling77]

Froze a few minutes in, looking at my voltages and all, what would you do? I'm "safe" up to 1.5v so I'm open to suggestion.

[martini161]

safe up to 1.5 in bios or safe up to 1.5 in cpuz?

[stopthekilling77]

HWMonitor has been off less than .01v every time I've changed voltage settings in the bios - CPU-Z has been reading WAY off.

In all actuality I could probably lower my vCore @ 3.0Ghz right now because I'd gone from 1.38v trying to get 2.95Ghz to work in a jump to 1.45v to see if 3.2Ghz would work. I'll minimize my vCore and see how my temperatures are when it's stable, just for reference.

[martini161]

cpuz is probably closer

[stopthekilling77]

Due to vdroop or something?
thats a whole 0.1v discrepancy... o.o

[martini161]

yup, my board has a .125 vdroop under load

[Bio-Hazard]

My MSI board has around 0.075 vdroop at my OC of 3.6 @ 1.50v bios.

All boards have the problem, some more than others...............