E6600 won't go past 3.2

[Woodstriker]

I'm trying to get my E6600 to 3.6 so I can use my 6400 ram at 1:1. Problem is that when I try and run at anything above 3.2 I have to crank the vcore up to 1.45+ in order to even run stable for just a few minutes. Each .15v I give it, it seems to last 30 seconds longer with Orthos. I don't want to go above 1.41 cause the temps start reaching almost 60C on load and I would prefer to stay around 50C. Is there anything I can do besides cranking the vcore up to get a stable OC?

 

[kfcheung]

get watercooling? lol

 

[Woodstriker]

The temps aren't holding me back...

 

[mrmez]

Doesnt sound right dood.

My 4300 on water gets to ~3.1 @ ~1.35v

May be a 'dud' chip, more likely read up on the OC guides here, u may figure it out.

Also a full list of specs/settings can help ppl figure out what is causing the FU.

 

[Woodstriker]

Asus P5N32-E SLI
Mushkin eXtreme Performance 6400 2GB (2 x 1GB) (Timings on auto atm)
Tuniq Tower
OCZ GameXStream 700w PSU

I'm wondering if it could be that something isn't getting enough volts besides my cpu. What are some normal volts for each component at 350fsb and what is a safe range to stay in? I saw in the OC guide that CPUs should stay below 1.5v but I've seen people go to 1.55v.

 

[Woodstriker]

Here's a pic of my volts in nv monitor:

All those red marks next to the voltages don't look so good to me

 

[Xazax310]

Wood im in the same boat as you. My E6600 on my EVGA 680I mobo wont go past 1480Mhz, or 3.2Ghz.


It just the limit of the Chip. With my E6400 i hit 1600FSB No Problem. at 1.4625V but with the E6600 barely can touch 1500FSB without it crashing.

 

[BigCharb]

SUP MAN! i have the same problem. i can get to 3.4 OS stable but in a game it crashes. at 3.6 i get the same temp problems and very unstable(1.6v!!) oh, did i mention i'm using watercooling!! i heard that the first batch of E6600s were the best at overclocking, the ones i got and u have aren't the lucky ones. i know 3.6 is fast but 3.2 at 1.6FSB is fast enough and i haven't had any problems with lag and instability. if anyone have any ideas to brake this wall please tell, if not 3.2 is the best we can get

 

[ThunderChunky]

My 6600 (L640F) get boot into the OS fine at 3.4ghz but even with 1.46v loaded it will fail in orthos after a few hours. Temps are too high for my liking anyway at those volts. Right now im trying to find the min volts for 3.2ghz. But if you want to run at 3.2 1:1 with 800mhz RAM just set your multiplier down to 8x and bump the fsb up to 400.

 

[little_scrapper]

I just want to make a few quick comments.

Yea the later runs of C2D are not nearly as good at OC as the 1st 28 weeks or soo. Intel pulled a classic bait and switch. Well not really. But they built OVERKILL into the first 6 months or so's worth of C2d. Then they changed something. Shortened the "developement time" of the silicon or something. Resulting in less OC'ability.

Anyways, I run my E4300 at 3.0Ghz (week 42 I think) It maxes out at about 3.2ghs. But lately I have simply reverted back to the stock settings and run this puppy ice cold on air. I now Orthos max load temps at about 42C. Anyways, guess what, I cant "feel" any difference between 1.8ghz and 3.0Ghz. in gaming and especially online gaming. No difference felt. Ok maybe just the slightest lilt of diff playing PC game at high res.

So, the question is. Do you really "need" to run your CPU on the ragged edge? When all was said and done (finding the potential of my hardware) I reverted bact to stock and havent noticed a thing and havent looked back. The C2D's are just soo awsome in general taht running 2Ghz or 3.6Ghz just doesnt make that much difference. Unless your working.. video encoding/editing..etc. But if your working.. then just buy the highest CPU available and write it off as buisness expense. Cause that is exactly what is is at that point

Just food for thought.

 

[Woodstriker]

I actually do some video editing so every little bit helps but I agree that you won't see much difference. It's just adds to the epeen :lol:

I figured since I wasn't going to make 3.6 on a 9 multi I would drop down to an 8 and just keep the 3.2. The odd thing is that when I dropped down to an 8 and tried to run at 3.2 I couldn't even get my system to post. Maybe my problem lies with the NB not getting enough juice cause I really haven't been bumping the voltage on that. I'll fool around some more with the voltages and see if I can get some new results.

 

[noobie123]

I'm pretty much in the same boat but i have tried everything already and prob gonna conclude that you are going to need to up vcore to maintain stability.

I went as high as 1.6v to run 3.6ghz stable except temps were 70+...so i had to back off, not worth it imo. I also tried raising all those other voltages (nb, sb, fsb, mem,etc.) but no luck, only vcore did the job.

I did get 3.6ghz at 8mult, by same vcore was required for stablility.

 

[little_scrapper]

1.6 actual Vcore is too much!! IMO anything over 1.5-1.55v is pushing your luck of electromigration. Seriously. Im no expert but what I have read seems to indicate the over the 1.55v mark is not good for a prolonged running. Unless your have serious cooling.

I run my E4300 at 3.0 Ghz @ 1.36V and I get a Orthos load temp about 50C. Give or take depending on my ambient. I live in TX.

1.6v+....be careful!

In RE: to your not posting at 8x. My understanding of the NB freq., strap if you will, is that it is the (default multi/actaul multi) x the FSB X4 or something like that. I will review. But basically it say that lowering your multiplier will raise your NB freq.

 

[apache_lives]

I'm trying to get my E6600 to 3.6 so I can use my 6400 ram at 1:1. Problem is that when I try and run at anything above 3.2 I have to crank the vcore up to 1.45+ in order to even run stable for just a few minutes. Each .15v I give it, it seems to last 30 seconds longer with Orthos. I don't want to go above 1.41 cause the temps start reaching almost 60C on load and I would prefer to stay around 50C. Is there anything I can do besides cranking the vcore up to get a stable OC?

E6600
8x400 -> 3200
1.3750v
ASUS P5B-Deluxe Wifi
Corsair XMS6400 C5 2x1gb
All voltages stock otherwise!

Worked with stock cooling like this, now i have a TT Big Typhoon.

Try lowering the Multi to 8 and hitting the FSB1600 mark first.

4mb cache is a different story to the E6400 etc - it overclocks differently.

 

[deceneu]

I just want to make a few quick comments.

Yea the later runs of C2D are not nearly as good at OC as the 1st 28 weeks or soo. Intel pulled a classic bait and switch. Well not really. But they built OVERKILL into the first 6 months or so's worth of C2d. Then they changed something. Shortened the "developement time" of the silicon or something. Resulting in less OC'ability.

Anyways, I run my E4300 at 3.0Ghz (week 42 I think) It maxes out at about 3.2ghs. But lately I have simply reverted back to the stock settings and run this puppy ice cold on air. I now Orthos max load temps at about 42C. Anyways, guess what, I cant "feel" any difference between 1.8ghz and 3.0Ghz. in gaming and especially online gaming. No difference felt. Ok maybe just the slightest lilt of diff playing PC game at high res.

So, the question is. Do you really "need" to run your CPU on the ragged edge? When all was said and done (finding the potential of my hardware) I reverted bact to stock and havent noticed a thing and havent looked back. The C2D's are just soo awsome in general taht running 2Ghz or 3.6Ghz just doesnt make that much difference. Unless your working.. video encoding/editing..etc. But if your working.. then just buy the highest CPU available and write it off as buisness expense. Cause that is exactly what is is at that point

Just food for thought.

this 28 weeks issue, does it apply to all C2Dos or just to 6600?
this entire thing is BS, I was planning to buy an 6600 , but now, hmmm, I really dont know.

 

[Alsone]

You don't need to go to 3.6ghz to get you ram at 1:1.

Scale your OC back to 3.0ghz (9 x 334) and set your ram to "sync".

You'll find you have a ram speed of 667mhz at 1:1 (2 x 667 dual channel = 1336) (4 x334 FSB = 1336).

Thats what I'm running on the same board as you. Totally stable and fast, and stock voltage.

3.6Ghz ia an extreme OC to attempt even on a good chip.

 

[Woodstriker]

I've been having a lot of issues with the 8 multi. I don't even need to run any stressing utilities to get it to freeze. I'm wondering if it's the NB in this case cause I don't get any kinds of errors when running Orthos like I normally do. It just straight locks up. In fact if I only run Orthos it won't freeze but if I do anything on my drives like copying files or playing media, it will freeze up after a short period of time. What are some normal voltages for NB and maybe SB?

 

[darkwire]

You don't need to go to 3.6ghz to get you ram at 1:1.

Scale your OC back to 3.0ghz (9 x 334) and set your ram to "sync".

You'll find you have a ram speed of 667mhz at 1:1 (2 x 667 dual channel = 1336) (4 x334 FSB = 1336).

Thats what I'm running on the same board as you. Totally stable and fast, and stock voltage.

3.6Ghz ia an extreme OC to attempt even on a good chip.

Do you get better bench scores when having it synced? Why not just have it unlinked and clock your proc where you want it, and not underclock your ram?

 

[Alsone]

You don't need to go to 3.6ghz to get you ram at 1:1.

Scale your OC back to 3.0ghz (9 x 334) and set your ram to "sync".

You'll find you have a ram speed of 667mhz at 1:1 (2 x 667 dual channel = 1336) (4 x334 FSB = 1336).

Thats what I'm running on the same board as you. Totally stable and fast, and stock voltage.

3.6Ghz ia an extreme OC to attempt even on a good chip.

Do you get better bench scores when having it synced? Why not just have it unlinked and clock your proc where you want it, and not underclock your ram?

All syncing does is ensure that the FSB: RAM speed are always kept at the right speeds, ie matching.

There's no virtue in having the ram speed faster without increasing the fsb as it will actually slow the system as the cpu will have to skip memory cycles in order to communicate. This could in fact slow the system. Hence why 1:1 is regarded as the ideal ratio, its becuase the FSB and memory cycles always coincide.

I could clokc the processor higher, but at 3.2 or so its unstable and as I'm on stock cooling I don't want to up the vcore or start loosing the memory timings. Yes the extra speed might be worth it, but the extra temp and all the hassle of having to keep resetting the BIOS isn't.

As for benches, it performs superb at the speed its at with memory and fsb at 1:1.

21,847 Dhrystone and 18,282 Whestone in Si Sandra.

That puts it slightly behind a 6800 Xeon in Dhry but slightly ahead in Whet. So overall performance is around the 6800 Xeon mark which is a significantly faster chip.

A standard E6600 score around 4,000 points less on both tests.

 

[little_scrapper]

but if I do anything on my drives like copying files or playing media, it will freeze up after a short period of time.

If your getting freezing up when accessing your hard drives then you need to look at your SB as all your hard drive as well as other stuff is going through the SB. If your SB is too hot, look into geting some air across its HS. If is doesnt have a HS, get one on it. If the HS doesnt feel warm, try reseating the SB HS as it may not be set properly and not transferring heat as it should.

As for that last statement, if your SB HS isnt seated properly, your SB could be overheating and the HS on it may not even feel warm.

Just some thoughts.