Overclocking Intel Core 2 Duo E6600 2.4GHz/1066

[SLippe]

Okay, I've been trying to read around in here about overclocking this CPU. From what I can tell, I should be able to just up the FSB to at least 3.0GHz/3.2GHz. My question is this, do I need to change anything else?

My current idle temps at 2.4GHz (stock) with Tuniq Tower 120 (fan at 1700rpm/60%) are 27'/23' C.

I'd like 3.0GHz, at least. Thanks.

[Revs]

You'll need to up your vCore and maybe your RAM voltage if you OC it. 3.2-3.4Ghz shouldn't be a problem. Set others to auto unless you hit problems.

[grey_1]

On my P35 board I upped the fsb til it was just barely unstable, then backed off a bit. Left all voltages at default and had a good strong 3ghz OC. This was with an E4600 which is 2.4 stock.

Like Revs said though, start bumping vcore and vdimm if you want to shoot higher.

[Lfctony]

I left the voltage the same. Adjust the ram so they won't go over their rated speed and increase the FSB to 333. Lock the PCIe clock to 100 and the PCI clock to 33. You have 3.0ghz easy. I don't go any more, I prefer overclocking that is nowhere near the limit of the CPU and always on stock voltage. I also never overclock the memory... Disable any spectrum relevant entries you see, C1E, Speedstep. Also, put your ram timings manually (ie 5-5-5-18).

[Revs]

1.5 vCore and 60.1*C are the limits for that CPU

http://processorfinder.intel.com/Details.aspx?sSpec=SL9S8

[andy_nv]

FSB termination and north bridge voltage could also be considered.

[darkrider01]

With my old Xeon 3060 (Conroe 2.4GHz - same as E6600) I was able to easily get it to 3.2GHz. I dropped the multiplier down to 8, increased FSB to 400. It was stable at 1.375V. My temps never went over 40-45C, however, I am on water.

[SLippe]

So far, so good!

http://www.nvnews.net/vbulletin/attachment.php?attachmentid=32105&stc=1&d=1214513982

I do have some questions about Advanced Timing Control. I don't know if I need to change any of them and even if I do, I don't know what to change. The settings are as follows;

ACT to ACT Delay (tRRD) 4 [Auto]
Rank Write To Read DELAY 4 [Auto]
Write To Precharge DELAY 8 [Auto]
Refresh to ACT Delay 56 [Auto]
Read to Precharge Delay 4 [Auto]
Static tRead Value 4 [Auto]
Static tRead Phase Adjust 0 [Auto]

[styles-T]

i was able to get to 3.2 on stock cooling. my chip runs about 36 degrees on the cpu 44 degrees on both cores idle . you should be able to get another 200mhz out of your chip easy.

356 mhz x 9 multiplier
1.35vcore

[SLippe]

i was able to get to 3.2 on stock cooling. my chip runs about 36 degrees on the cpu 44 degrees on both cores idle . you should be able to get another 200mhz out of your chip easy.

356 mhz x 9 multiplier
1.35vcore

Yeah, for some reason I haven't had much luck with 3.2GHz, but I may toy with it some more. I'm 100% stable at 3.0GHz, but for some reason CPUz is showing my voltage at 1.312, which is weird, because in the BIOS I have it set at 1.35v. I better have a look, again...

[Revs]

Hey dude. My E6600 OC'd better with an 8x multiplier. Also the higher FSB will make your memory bandwidth.... wider :p

[SLippe]

Hey dude. My E6600 OC'd better with an 8x multiplier. Also the higher FSB will make your memory bandwidth.... wider :p

Weird, man, because I was thinking about going to an 8x multi when I tried for 3.2GHz or higher. LOL

Okay, I bumped the voltage in the BIOS to 1.375 and now CPUz shows this;

http://www.nvnews.net/vbulletin/attachment.php?attachmentid=32304&stc=1&d=1216203232

[Revs]

If you just want I nice, low-ish volt OC, I would go with 8x400 = 3.2Ghz. Over that and the volts need to go up quite a bit.

[SLippe]

If you just want I nice, low-ish volt OC, I would go with 8x400 = 3.2Ghz. Over that and the volts need to go up quite a bit.

I tried that, but for some reason it's not stable. I even had the memory at a 1:1 ratio. I think, and this is pure speculation, that it has something to do with my Northbridge temp (no fan, just a heatsink) or my PSU. I don't know why I think that, just a hunch. Well, until I can get a fan on that NB and/or a new PSU it looks like 3.0GHz (333x9) is going to have to do, plus my memory is running at it's actual speed of 1066 this way, too. ;) Thanks for your input, Revs.

[CaptNKILL]

Yeah, for some reason I haven't had much luck with 3.2GHz, but I may toy with it some more. I'm 100% stable at 3.0GHz, but for some reason CPUz is showing my voltage at 1.312, which is weird, because in the BIOS I have it set at 1.35v. I better have a look, again...

That is probably due to what people call vdroop.

The cpu voltage drops under load. I think its some sort of thermal or safety feature. It can be annoying while overclocking but its probably why our CPUs can take 1Ghz + overclocks 24\7 for years without failing.

Basically, you'll have to bump the voltage up more to compensate, and its up to you if you think its worth it. You'll get more heat (since the voltage will be higher at idle too), but you'll also get more overclocking head room. Since you're using a tuniq tower, you can probably go for it. Just watch your temps and use coretemp to monitor during testing. Most other programs don't report the correct temps.

I have my voltage set to 1.5v, which is pretty damned high, and under full load my CPU drops to around 1.44v. Thanks to the big ass cooler I'm using, the system has been rock solid for almost a year now. These chips are amazing. :)

[Revs]

Teh Capt's right SLippe, more vCore needed. My old Striker seemed to need alot of volts, I had it at 1.5v @ 3.36Ghz.

400Mhz FSB is a good OC cos like you said, you can run your memory at a 1:1 ratio. I would try again with higher vCore, 1.45v ish, if it's stable at that clock, drop the vCore to find the minimum vCore for that speed.

Have you disabled the 'spread spectrum' options, that usually helps. The P35 chipset can generally get well over 450Mhz.

[SLippe]

That is probably due to what people call vdroop.

The cpu voltage drops under load. I think its some sort of thermal or safety feature. It can be annoying while overclocking but its probably why our CPUs can take 1Ghz + overclocks 24\7 for years without failing.

Basically, you'll have to bump the voltage up more to compensate, and its up to you if you think its worth it. You'll get more heat (since the voltage will be higher at idle too), but you'll also get more overclocking head room. Since you're using a tuniq tower, you can probably go for it. Just watch your temps and use coretemp to monitor during testing. Most other programs don't report the correct temps.

I have my voltage set to 1.5v, which is pretty damned high, and under full load my CPU drops to around 1.44v. Thanks to the big ass cooler I'm using, the system has been rock solid for almost a year now. These chips are amazing. :)

Teh Capt's right SLippe, more vCore needed. My old Striker seemed to need alot of volts, I had it at 1.5v @ 3.36Ghz.

400Mhz FSB is a good OC cos like you said, you can run your memory at a 1:1 ratio. I would try again with higher vCore, 1.45v ish, if it's stable at that clock, drop the vCore to find the minimum vCore for that speed.

Have you disabled the 'spread spectrum' options, that usually helps. The P35 chipset can generally get well over 450Mhz.

Thanks, fellas. I'll mess with it more this weekend. I start my "vacation" on Sunday, so I'll have like 10 days off to mess with it. :) My temps have been really good, so far, so I don't think 1.45v or whatever will be too bad. I'll report back in a few days. Thanks, again.

[SLippe]

Steady at 3.2GHz (8x400) 1.475v. :thumbsup: What's weird is when I run Orthos, the VCore drops under 1.4 (barely). :wtf: Here's what it looks like under CPU-z with nothing running, except Firefox.

http://www.nvnews.net/vbulletin/attachment.php?attachmentid=32345&stc=1&d=1216581796

[jcrox]

1.475v?? that seems awfully high

[SLippe]

1.475v?? that seems awfully high

That's what I have it set at in the BIOS, but for some reason all monitoring software never shows it at that setting and it even drops below what is in that screenshot sometimes. Probably could get away with 1.45v. *shrugs* Temps are good either way.

[jcrox]

That's what I have it set at in the BIOS, but for some reason all monitoring software never shows it at that setting and it even drops below what is in that screenshot sometimes. Probably could get away with 1.45v. *shrugs* Temps are good either way.

Yeah, I think that's the "vdroop" people refer to. I think I run mine at 1.4 for 3.2GHz

[SLippe]

I just upped my vcore to 1.5v in BIOS, CPUz shows 1.45v. Bus is now @ 425 which puts me @ 3.4GHz with rated FSB @ 1700MHz while using a 2.5:1 (or whatever) ratio to put my RAM at 1063, just below normal speed of 1066. :thumbsup:

http://www.nvnews.net/vbulletin/attachment.php?attachmentid=32973&stc=1&d=1220425233

Now, let's see if I can run CoD4 for any amount of time...

[SLippe]

Okay, that was a big no-no. :o

Back to 3.2GHz (400x8) with 1:1 ratio.

[Revs]

Hiya SLippe. What's your temps like?

[SLippe]

Hiya SLippe. What's your temps like?

Currently...

http://www.nvnews.net/vbulletin/attachment.php?attachmentid=32975&stc=1&d=1220471540