• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

E6600, can't get stable at 3.6ghz (400x9) FPO#L632B086

smsmasters

smsmasters

smsmasters

Soldato
Joined
26 Aug 2004
Posts
3,278
E6600, can't get stable at 3.6ghz (400x9) FPO#L632B086

--------------------------------------------------------------------------------

My cpu is an e6600 FPO#L632B086
Motherboard is ASUS P5B Deluxe Wifi
Cooler is Arctic Freezer 7 Pro

Here are the overclock settings I have tested so far:
attachment.php


I have found that I am stable at 3.2ghz @ 1.3V either 400x8 or 356x9. At this voltage, my temps as reported by core temp are 33C idle, 54C load.

I have successfully tried 3.6ghz (400x9) but I get errors in the first seconds/minutes of orthos. Even a voltage increase to 1.5v does not improve stability. I have even tried upping the SB, NB, FSB voltages but I still get errors in orthos.

Any advice please how to get my cpu stable at 3.6ghz? I can boot into windows fine at <1.38V 3.6ghz (400x9) but I get errors in orthos.

I think I have a good chip, but I think I just need to find the perfect settings to get it stable at 3.6ghz.
 
your not clocking your memory at the same time are you? if so keep that at stock speeds for the mean time....just takes the memory out of the equation then.

What PSU do you have?

Also what is you vcore After any vdrop when stressed...you may need to set a higher vcore to avoid instability when cpu is at 100%
 
not all E6600 s will give you 3.6ghz stable, had a mate with one that was luck to give 3.2ghz...
 
I'm now on my fourth conroe, as my other 3 wouldn't do 3.6 GHz stable. One of them was an E6700 that topped out at 3.5Ghz on high end air. The rest were all E6600's and only my current one will run at that speed.

Don't believe everyone who says their chip runs at 3.6Ghz. Most haven't done proper stabilty tests like you are doing. All my conroes have APPEARED to be stable at 3.6Ghz, however only one truely was (24hrs orthos).

Try just a little more vcore, maybe 1.55 volts in bios. Are you getting any vdroop under load? Is your CPU flat? many have had to lap their conroes as in some cases the chip's IHS is badly warped.
 
Jay_t said:
Don't believe everyone who says their chip runs at 3.6Ghz. Most haven't done proper stabilty tests like you are doing. All my conroes have APPEARED to be stable at 3.6Ghz, however only one truely was (24hrs orthos).
Click to expand...

There's a lot of that going on - I've seen some really dangerous advise on overclocking going around lately. For example, look at this rubbish The OP here is telling people to pump maximum available voltages through the North and Southbridges in the bios setting. And thats before you've even started overclocking by 1mhz! Fine if you want to blow up your mobo, graphics card and harddisks, loose your data and start a fire :eek: .There's worse if you read through the post.

Realisically, 3.2 is a VERY GOOD overclock for any E6600. Anything more and you'll really start to push things. You may have found the limits of your CPU.

Besides, 3.2 is incredibly fast - do you really need to push your CPU to 3.6? Its just a number at this stage, you're already sprinting.
 
If its 54C load at 3.2ghz then its going to be passing 65+C at 3.6.


Get a better cooler and give it 1.525V in BIOS, about 1.45V actual (or you can do the Vcore pencil mod which I've done and 1.525V in BIOS = 1.515V in windows :D
 
You are jumping too high too fast.

Don't be pressured into believing every e6600 can do 3.6ghz, every cpu is different and there are many people out there who claim there cpu runs at XXX speed without testing it correctly for stability. Go slowly, test thoroughly.

You have not tested for stability correctly - 30mins is nothing on orthos I'm afraid, barely more than a SuperPI run. Go back to around 3.2 and see how much vcore it takes to get that stable before aiming higher. Test it for 8 hrs minimum - preferably 12hrs (see my sig). Once you have it stable at a given overclock then push it higher, not before otherwise you will run into the problems you are experiencing here as, no offence, I wouldn't even rely on 3ghz being stable with only a 30min orthos run. Testing it thoroughly in the first place will actually save time in the long run and will give you a more realsitic target of what your cpu can do. Good Luck :)
 
In response to the posts above:

My PSU is a hiper 480W (530W Peak)

My memory is fine I think since I can run 400x8. I guess I need more volts at load to get 3.6ghz.

I will try the vcore pencil mod. If I set 1.3V in the BIOS, it is 1.27V as reported by speedfan at idle. Under load it droops to ~1.25V.

I did try 400x9 (1.5V) but my load temps were around 70C! :(
 
Last edited:
w3bbo said:
You are jumping too high too fast.

Don't be pressured into believing every e6600 can do 3.6ghz, every cpu is different and there are many people out there who claim there cpu runs at XXX speed without testing it correctly for stability. Go slowly, test thoroughly.

You have not tested for stability correctly - 30mins is nothing on orthos I'm afraid, barely more than a SuperPI run. Go back to around 3.2 and see how much vcore it takes to get that stable before aiming higher. Test it for 8 hrs minimum - preferably 12hrs (see my sig). Once you have it stable at a given overclock then push it higher, not before otherwise you will run into the problems you are experiencing here as, no offence, I wouldn't even rely on 3ghz being stable with only a 30min orthos run. Testing it thoroughly in the first place will actually save time in the long run and will give you a more realsitic target of what your cpu can do. Good Luck :)
Click to expand...


To be fair, I only tested my current overclock for 2 hours on Orthos, and uptime now is 160 hours since the last restart and its been running SMP F@H clients for weeks now. :) Not a single problem yet :)
 
blend if your happy with the oc of the memory if not use the cpu one

Personally Id forget about the memory and concentrate of the cpu, if you clock one at a time and get it stable or unstable then you know it has nothing do do with the memory, then once your happy with the max stable oc of the cpu then work on bringing up the memory too:)

Just my 2c worth :)

edit

forget what im saying about the memory....forgetting you got a higher multi of 9
 
Last edited:
Concorde Rules said:
To be fair, I only tested my current overclock for 2 hours on Orthos, and uptime now is 160 hours since the last restart and its been running SMP F@H clients for weeks now. :) Not a single problem yet :)
Click to expand...

I don't really want to get into the 'how long to run orthos for' arguement because everyone has there own opinion on what is and isn't stable but if you are gonna run the program you may aswell let it run for at least 1 round (usually around 11-12 hours) otherwise its not completing a full cycle, thereby pointless running in the first place. I have had orthos fail immidiately on a system that was completley game stable - it all depends on what YOU class as stable and what YOU are happy with. Personally if my pc makes a computation error(FATAL ERROR) after 4 or 5 hours then I don't deem it stable. Your PC Concorde may well be more than stable at 2hrs - it may have done over 12hrs with ease if you had let it run that long, if however it had failed after 2hrs I personally wouldn't be happy with it and certainly wouldn't be running f@H on it tbh.
 
Anyway, I upped the vcore to 1.5125V (1.45V droop under 100% load) and I've been running orthos for 20mins so far... :D

Here's a screenshot. I think 1.5125V should be safe? ~70C load.

 
smsmasters said:
Anyway, I upped the vcore to 1.5125V (1.45V droop under 100% load) and I've been running orthos for 20mins so far... :D

Here's a screenshot. I think 1.5125V should be safe? ~70C load.

Click to expand...

Noticed the wallpaper, any chance of a copy or link pls :)

And i agree 70c does seem a bit high
 
tbh those temps wouldnt bother me, if it stays stable for a good few hours on orthos i would stick with it.

Just be yir own judge, you know the risks.
 
You must log in or register to reply here.
Back
Top Bottom