E6600 Overclocking Thread

[Some1ne]

Yes, EIST = SpeedStep, as far as I know. If you're running BIOS 614 (and I think also 609), then I think the EIST option no longer appears. I'm not sure, but it seems like the board disables it by default.

 

[Geekwannab]

Originally posted by: Geekwannab

Originally posted by: JPS35
Okay, I was able to unplug the power and turn off the main switch, which did a great job!!! Thanks for the help!

Now, once again:

1. Recommendations for an aftermarket HSF?

2. Where is the EIST located in the BIOS?

1.I have the Ninja and it's great. Dig this, with stock HSF my load temps were like 63C No OC just stock everything. With the Ninja installed my load temps during full load(ORTHOS running for like 7 hours), was never went above 48C.Granted my E6600 was a week 27 and might running a bit cooler than the other weeks(24 through 26). Anyway, HSF recommendations are totally based on your budget and your OC needs. I wanted to get the Infinity, but read about the mounting problems on my mobo, hence I got the Ninja. I wanted atleast 3.4 outta my E6600. If you are not into OCing and need a good HSF and if you are on a budget, I recommend the Freezer pro.


2. Its in the CPU section of the BIOS where you disabled C1E. It must be right under it, something like Enhance Speed Step something something something.

OMG did I post this. Me English too bad, lol. I think I need to start proof reading before I click the "Reply to Topic" button.

 

[Krazyjack1000]

Originally posted by: Buckster
wow - Krazyjack1000- you've some much better Vcores than me !

what week is that ?

Hmm don't know where to find the week but on the box it says FPO/BATCH #L628A333
VERSION #D63625-001 Don't forget here in Australia we always get things last 🙂

Cpuz records it as Stepping 6 B2

 

[MiS Nemesis]

Just wanted to post back and inform everyone of the solution to my drastic problem. I ordered another P5W mobo and sure enough the problem still persist. My last option was to change the DUO core in case mine was busted. That didn't work, so far, I changed the Memory, Video Card, and CPU, that last was the power supply. I dropped a bad OCZ 700 PS and this actually fixed my problem. So for all those with a similar problem, try changing the PS.

 

[cmdrdredd]

Originally posted by: Krazyjack1000

Originally posted by: Buckster
wow - Krazyjack1000- you've some much better Vcores than me !

what week is that ?

Hmm don't know where to find the week but on the box it says FPO/BATCH #L628A333
VERSION #D63625-001 Don't forget here in Australia we always get things last 🙂

Cpuz records it as Stepping 6 B2

You have week 28. L6xx where xx = week.

 

[Some1ne]

Mine is a week 26 then.

 

[MiS Nemesis]

Hey Some1ne, have you updated your BIOs to 1201 or later? I am trying to follow your guidelines but some of the options do not exist. And I don't think I am doing this right. My Rated FSB is 1516.2 Mhz, and BUS speed is 379Mhz, and it seems my Multiplier is always at 9.

 

[Some1ne]

1201? When did that come out? The most recent BIOS I'm aware of is the 614 revision. Do you have a link to 1201?

 

[MiS Nemesis]

Actually I see 1305 as the latest.

<a target=_blank class=ftalternatingbarlinklarge href="ftp://dlsvr03.asus.com/pub/ASUS/mb/socket775/P5W%20DH%20Deluxe/P5WDH1305.zip">ftp://dlsvr03.asus.com/pub/ASUS/mb/socket775/P5W%20DH%20Deluxe/P5WDH1305.zip</a>


I wonder why they remove other versions of the BIOS?

 

[MiS Nemesis]

I just realized I have a different board than you. P5W DH Deluxe is what I have.

 

[scoobysix]

E6600 (Week 27, Noctua NH-U12F HSF)
Asus P5B Deluxe/Wifi
G.Skill F2-6400PHU1 HZ PC26400 2gb
Antec NeoHE 500w

Bios: 0614
CPU: 334x9 (3005ghz)
RAM: 835mhz (4-4-4-12, sub-timing 3-10-5-13)
PCI-E: 100
PCI clock: 33.33mhz
Vcore: 1.30v
Vdimm: 2.0v
FSB termination voltage: 1.30v
NB: 1.25v
SB: 1.5v
ICH: 1.057v

Idle
100% load (Orthos)

Does this look okay to everyone?

Going down to 1.20v on FSB termination voltage resulted in an error after 9mins of Orthos. Bumped it back up to 1.30v and it's all good.

1.2875v Vcore resulted in error after 2.5hours of Orthos.