Core 2 Duo Batch Number threads for overclocking

[Delavan]

Well kinda interesting that you own the same processor batch, it makes it easier to compare!

For the Memory, I didn't catch your drift. At stock I did set it up 1:1 FSB so "she" was running at 533 Mhz instead of 800Mhz. I 'm getting latencies and timings in the 3's that way. I'm just getting used to my system!

What mobo are you getting, sswilson?

[sswilson]

DFI infinity "Dark" 965-S.

As far as the memory goes..... What you want to do is take it out of the picture as much as possible.

You've already got it set to 533, so all that's left is to ease up on your latencies (try 5-5-5-15) until you find the max that you can get out of your processor, then tighten up your latencies from there.

[Delavan]

I just tried different settings and now it works!!!
I reached my number! 3.2 Ghz on my E6420 L644G289! Nothing surprising compared to the numbers some of you guys can squeeze out of a processor...

But anyway..I increased the FSB voltage by 0.1V and I increased the CPU voltage from 1.35 to 1.356...and now I post at 3.2Ghz (8X400), RAM 1:1.
I won't be able (I guess) to go higher, because I screwed up on the RAM I got. It's good at stock speed as far as all the reviews I read.
And I won't be able to sell them stick to somebody around, nobody is an enthusiast...They all say that a comp is just to receive/send emails...

Now I will test for stability/temperature...Orthos tonight!

Delavan

[Delavan]

Well, Orthos crashed to desktop after two minutes...

So I changed my settings to FSB volts = Stock, and CPU voltage = 1.36875V, Still at 3.2Ghz...

Now Orthos is on for 20 minutes (I know it's nothing)

TAT gives me a 43 Deg.Cel for each cores (Arctic Freezer 7 full throttle)

And Gigabyte's MOBO monitoring tool PC HEALTH gives a System T of 40 Deg.cel and a CPU temp of 35 Deg.Cel

Now how long do I have to run Orthos for to "qualify" for stable OC? And NOOB question...how do I take a screenshot?

Update...Orthos crashed after 38 minutes... BOUHOUHOU! Where is the love....

[sswilson]

Heh..... you should be reveling in the joy of the hunt!!!!! :)

IMO, the real kick of OC'ing isn't the end point, it's the work that goes into squeezing every last ounce of performance out of a system.... you can't get there overnight..... :)

As far as orthos goes...... bare minimum would be 8 hours to claim a stable system, but 24 is much better as I've had stuff fail after 10+ hours and the ultimate goal is to have a proven stable system rather than just be able to post #s.

[Delavan]

I manage to pass the 4 hours marks (Orthos) now at 3.2Ghz. I has to raise the CPU volts a bit (1.3875V), and the RAM a little +0.1V. FSB +0.1V...

The weird thing is that I got a much slower FPS in the first 3Dmarks06 test "return to Proxicon or something"...22FPS OCed instead of 66 stock clock. Quake 4 was blazing fast also. I got enough PSU juice, no prob there.

Any idea?

[sswilson]

Originally Posted by Delavan

I manage to pass the 4 hours marks (Orthos) now at 3.2Ghz. I has to raise the CPU volts a bit (1.3875V), and the RAM a little +0.1V. FSB +0.1V...

The weird thing is that I got a much slower FPS in the first 3Dmarks06 test "return to Proxicon or something"...22FPS OCed instead of 66 stock clock. Quake 4 was blazing fast also. I got enough PSU juice, no prob there.

Any idea?

Try loosening your mem timings one at a time. It could be that you're pushing one of them too far, and it's having to go around another full cycle before doing its job. (Did that make sense? If not I'll try to figure out a better analogy).

Mem timings are an art form all of their own. I spent a full day playing with different combinations of timings seeing how they affected super-pi scores on my S939 rig. Ended up squeezing an extra .5 seconds out of a 1M super-pi using the extended settings.

[Somed00d]

Originally Posted by Delavan

I manage to pass the 4 hours marks (Orthos) now at 3.2Ghz. I has to raise the CPU volts a bit (1.3875V), and the RAM a little +0.1V. FSB +0.1V...

The weird thing is that I got a much slower FPS in the first 3Dmarks06 test "return to Proxicon or something"...22FPS OCed instead of 66 stock clock. Quake 4 was blazing fast also. I got enough PSU juice, no prob there.

Any idea?

thought i would add my input.. Open CPU-Z, under Mainboard check your graphics interface link width is x16. if it is x1 you may have to change your pcie bus speed from 100mhz to somwhere between 100 and 110..

wish i could get my e6420 stable at 400x8.. running 390x8.. have L707A323 batch on a DFI Infinity "dark" P965-S

[Delavan]

Orthos stable "Blend test" 8 hours @ (8X400Mhz)@3.2Ghz

Thanks you all, I got good supports from you folks!

Ok, I "forced" PCI-E frequency to 100Mhz instead of running it at auto, now CPU-Z gives me a PCI LINK of 16x...Good to go.

For RAM timings, I found a review on my RAM (pretty much the only one on the net).

Mushkin 2GB EM6400 DDR2-800

That RAM is not very very good outside the "stock" settings. I didn't make a wise choice buying it...anyway I reached my expected overclock...
4-5-4-12-2T is the way to go for that RAM. It uses so odd RAM chips (Aeneon AET93F30D).

Sorry for the fonts...
The CPU got a 1.4V (I know lots of 6420 are running at stock volts...not this one....although CPU-Z reads 1.36V)
So BIOS CPU volts at 1.4V and CPU-Z monitoring 1.36V...
TAT temperature during the ORTHOS Blend test (8 hours)..44 Deg.cel..

Have a great day (I already made mine LOL @3.2Ghz!)

Now I'll have to work on the Graphics card!

[Babrbarossa]

Originally Posted by Somed00d

thought i would add my input.. Open CPU-Z, under Mainboard check your graphics interface link width is x16. if it is x1 you may have to change your pcie bus speed from 100mhz to somwhere between 100 and 110..

That's an interesting little quirk- is it just for the Dark?