**Official e8400/e8500 Retail OC Thread

[Chri$ch]

same problem with DFI DK P35...

max stable FSB is ~505-510Mhz, max FSB 1M 536Mhz.

On Gigabyte G33 run prime with 550FSB (4.4Ghz)

[ArCElM]

Not a good 1M time, but low voltage for this clock (load ~1.39v)

this is on Gigabyte GA-G33M-DS2R

I don't understand, how can a 4.6Ghz get such a poor PI time? I mean, how is it possible? thats barely better than mine on 4.1Ghz - sexual clock speed on such a low voltage but I dont understand the performance, looking at that I would say I would grab that board the G33M but, hell, need explanation first

[Funky]

Here is what i managed to squeeze out of good old air cooling (TRUE).
Chip is Q746A482


9.391s - Intel Core 2 Duo E8400 @ 4815MHz 535x9 1.66v - Aircooled (TRUE) - AxeRam 800 @ 1070 Mhz 5-5-5-15 2.2V

[Chri$ch]

I don't understand, how can a 4.6Ghz get such a poor PI time?

5-5-5-15 timigs, low subtimings (performance level) + Gigabyte board (G33 chipset?)

[unclewebb]

Funky: Good work. Maybe someone around here should start a 9 second SuperPi club.

[vera]

same problem with DFI DK P35...

max stable FSB is ~505-510Mhz, max FSB 1M 536Mhz.

On Gigabyte G33 run prime with 550FSB (4.4Ghz)

It' impressive , p35 boards (mine asus p5k-e) sucks for 45nm , not boot 540fsb with my e8200 Q745

[mrcape]

Just got a second e8400 and I'm wondering if I should bother testing it or wait to see which chipset / bios is actually ready for it. I'm thinking P45 lol!

I know p35 and x38 are working but it still seems flaky.

[Mav451]

Just how much better would P45 be?

I mean, if it's KT133 >> KT266A bs all over again, I'm gonna be sad.

[Zeus]

I have a feeling the secret is in the termination voltage in conjuction with GTL voltage.

These 45nm cpu seem to need other values than Conroe.

The "cheaper" Asus boards have a fixed value for this which is optimized for 65nm cpu's.

Bios 1002 with 45nm cpu support have both these settings in bios but they actually do bugger all.

I now flashed to bios 1004 and it looks like i gained some stability, i can run prime at a tad lower voltage now, Asus probably changed the default GTL voltage value.

I'm gonna play with these settings soon to see if these work now with this bios.

Maybe i'm talking out of my backside but changing GTL value on the DFI P35 helps stability a great deal.

[nama]

HI guys, i hit a brick wall with my e8400, keep gettin the "FATAL ERROR: Rounding was 0.5, expected less than 0.4" message in prime past 4.3 ghz. aiming at 4.5 but no vcore will satisfy the beast. my assumption so far is that these chips dont need that much vcore to hit sky high but its other settings like cpu ppl, fsbt, and those gtl thing but have no idea what to set.

anyone running this chip on maximus formula?
so far am at 500fsb, stable @ 8.5 multi but when i change to 9 nuthing seems to work
@ 500x 8.5 am 24hrs prime stable blend
1.425vcore
1.5v cpu ppl (bios set)
1.54 fsbt(1.43 actual)
2.3vdim @ 5-5-5-5-3-35-6-3 @ 1200( passed 12 prime + 24hrs blend)
1.65nb
1.18sb
1.55 sb2

any tips on gettin it stable with multi 9 .

rig
maximus formula se (907)
e8400(Q745a372, 12/20/07, 1.1125vid)
2gb crucial ballistix tracer 8500
2x 80gb seagate sata raid 0
2x saphire 2900gt CF(disabled when priming)
Swiftech 220 compact kit(4x scythe 1500rpm fans on rad)
northbridge and cpu loop.
load temps at 1.425(nb39-41, cpu 54-58, cores 58-62 both same, sb 35)
idle 30cpu, 38cores, nb 38, sb 32)

@ 9x 500 tried 1.45, 1.47. 1.48.1.5 and 1.525(load at 63cpu) and nothing seems to work. any tweakin guru's please tip me. thanks.

[Zeus]

Did you try to find the max fsb first?

You might 've hit an fsb wall, more people report trouble to get over 500fsb on the maximus.

Try to find the fsb max with multi 6x first.

[mrcape]

Maybe i'm talking out of my backside but changing GTL value on the DFI P35 helps stability a great deal.

Adjusting gtls manually helps with stability in my case with the DFI, but it's guess work. I really wonder how it will be possible to have any auto setting for that if they expect to support both 45nm and 65nm. And if it has to be manually set, what should the values be for a given clock and vcore. And does that change from board to board, chipset to chipset?

I don't think anyone has these answers yet. I'd like to see a board & bios designed exclusively for 45nm and compare to what's currently available.

[Mav451]

I'm gonna watch this thread like a hawk regarding those GTL values...lol make another spreadsheet for that?

BIOS/OC/GTL? Or something.
But then we also have X38 vs. P35 difference, woohoo ;D

[unclewebb]

nama: I realize that Ballistix memory can run at DDR2-1200 and that your memory has been proven to be able to run at that speed but it's still a good idea to reduce the stress on your memory when going for maximum CPU MHz. Try running your memory at 1:1 and see if that helps any. There's no guarantee that all Wolfdales are going to hit 4.5 GHz and be 100% stable.

[Forsaken1]

I'm gonna watch this thread like a hawk regarding those GTL values...lol make another spreadsheet for that?

BIOS/OC/GTL? Or something.
But then we also have X38 vs. P35 difference, woohoo ;D

Raise gtl lower vtt then conroe .

[zoob]

I think it was Praz earlier in this thread that mentioned

CPU VTT 1.2
GTL 60/59/60

on a DFI X38

[nama]

Did you try to find the max fsb first?

You might 've hit an fsb wall, more people report trouble to get over 500fsb on the maximus.

Try to find the fsb max with multi 6x first.

i can go all the way to 550fsb. and its stable at 500x8.5 just i want to run multi 9. its just setting i can get right that why i need someone with gtl,ppl knowledge coz alot of guys seem to have success when they set the manually. am working on finding the right conditions but if someone else know it will save me time

[kitfit1]

Adjusting gtls manually helps with stability in my case with the DFI, but it's guess work. I really wonder how it will be possible to have any auto setting for that if they expect to support both 45nm and 65nm. And if it has to be manually set, what should the values be for a given clock and vcore. And does that change from board to board, chipset to chipset?

I don't think anyone has these answers yet. I'd like to see a board & bios designed exclusively for 45nm and compare to what's currently available.

I don't think anyone has all the answers either. But the art of overclocking is to be able to find the answers yourself. With the 65nm procs, clocking was very very easy. If you go back to the NF4's, getting a good clock was all down to setting up your ram properly, which a lot of peeps could never do really. With the 45nm procs, us clockers have got to use our brains and clock logicaly. Just dialing in a clock and it works, has gone out of the window. Old school trial and error, is where it's at now.

[nama]

nama: I realize that Ballistix memory can run at DDR2-1200 and that your memory has been proven to be able to run at that speed but it's still a good idea to reduce the stress on your memory when going for maximum CPU MHz. Try running your memory at 1:1 and see if that helps any. There's no guarantee that all Wolfdales are going to hit 4.5 GHz and be 100% stable.

thanks and noted. at these speeds 500fsb plus i noticed my memory doesnt like high timings. it reboots when stressing it. but works fine at tighter timings. will work on 1:1 and see if it helps any. will post my findings

[politenessman]

just got an 8400, q746a, pack date 1/10, from newegg nj warehouse. ordered yesterday. will stoke it up and report oc in a few hours. from googling, this (q746a) seems like a good batch.

[barzi]

Hmm my e8400 is getting hot! Coretemp gives 63C load, with 1.264vcore. This is on 4005mhz (445x9). Am i doing something wrong, or is this just a hot one? Or coretemp is wrong?

This is all with a Tuniq Tower 120, with stockfan on low.

[mrcape]

I don't think anyone has all the answers either. But the art of overclocking is to be able to find the answers yourself. With the 65nm procs, clocking was very very easy. If you go back to the NF4's, getting a good clock was all down to setting up your ram properly, which a lot of peeps could never do really. With the 45nm procs, us clockers have got to use our brains and clock logicaly. Just dialing in a clock and it works, has gone out of the window. Old school trial and error, is where it's at now.

I don't want to get into discussing the art of anything, but I'll agree that it takes a lot of testing and tuning when something so new is out. I've been doing it going back through NF2, and I always like to leverage forums for info to balance my own findings against.

A comprehensive data set on these setups could only help, especially entries for the same chip on multiple boards.

[Bail_w]

i confirmed there is no degration in my chip, i just lower the FSB termination voltage to 1.2v(from 1.5v) and Northbridge to 1.4v(from 1.55v) and i just passed 30 mins OCCT at 4.32ghz with 1.4v (as before). Also, i am running orthos at this moment, will report back results later.

[Mav451]

I don't want to get into discussing the art of anything, but I'll agree that it takes a lot of testing and tuning when something so new is out. I've been doing it going back through NF2, and I always like to leverage forums for info to balance my own findings against.

A comprehensive data set on these setups could only help, especially entries for the same chip on multiple boards.

Yeah I added a column for GTL data in the database. That way we're not entering data into two separate databases. But I have a feeling people's settings will be changing as they figure out what works...so hopefully everyone can update their entries.

[Xvys]

Hmm my e8400 is getting hot! Coretemp gives 63C load, with 1.264vcore. This is on 4005mhz (445x9). Am i doing something wrong, or is this just a hot one? Or coretemp is wrong?

I think the CoreTemps with the E8400 are meaningless. It doesn't matter if it reads 45C or 75C under load, as long as the computer keeps running, all is well. Intel has commented that only the cpu temp is important and they recommend 61.2C as the maximum cpu temp with the E8400. The cpu will automatically throttle-down if temps exceed the maximum.