Something I bet no one considers

[[Dr. V]]

isnt it true that, even if the voltage is increased, if the CPU is kept under the correct temp that the stock cooler is rated by intel/amd to keep them, then the chip is fine?

Intel Core 2 Duo E6600 @2.4GHz and STOCK VOLTAGE with STOCK COOLING operates at 55*C Load (as an example)

VS

Intel Core 2 Duo E6600 @3.2GHz and 1.5v with a Big Typhoon (for example) operates at 55*C Load as well (as an example)

wouldn't those 2 scenarios (if it were to be like that) result in the same load on the CPU? or does simply raising the voltage no matter what the temps are affect the CPU more. what if the BT kept it 50*C (comperable to the above scenarios again)...what now? lower than stock?

[One4yu2c]

Originally Posted by ST!X

isnt it true that, even if the voltage is increased, if the CPU is kept under the correct temp that the stock cooler is rated by intel/amd to keep them, then the chip is fine?

No, as that assumes that temps are the only method by which a CPU can be damaged, which isn't the case.

[Phosphorous]

What voltage you at with the 3.2 clock Quake?

[Zambini]

My Core2Duo 6400 @ 3.2ghz (stock voltage OF COURSE! I'm not made of money and can replace a $200 cpu like that *snaps fingers*) runs 100% load all day all the time (FAH or games) and it never exceeds 45°C.
In fact, right now its 42°.

'course I have a Zalman cp9700

[Quakindude]

Originally Posted by Phosphorous

What voltage you at with the 3.2 clock Quake?

I set the voltage in my BIOS to 1.325V when I have it at 3.2Ghz. I run it at 1.3525V when I'm running it at 3.373-3.4Ghz. After voltage droop, it comes out to 1.3 for 3.2Ghz and 1.32 or so for 3.4Ghz. To actually get the full rated voltage of 1.3525V, I have to set the voltage in my BIOS to 1.362V. I've run it all the way to 1.45V which translated to 1.4V after voltage droop. I got my E6600 to 3.5Ghz with that voltage, but loaded temps quickly hit the upper 60's and settled at 71*C after an hour of benchmarking.

At 3.5Ghz, I got random BSoD. I blame this primarily on the chipset itself. I may be able to get it more stable at that speed by increasing the NB voltage, but I am quite satisfied with a 3.2Ghz and within spec voltage setting.

[Phosphorous]

Originally Posted by Quakindude

I set the voltage in my BIOS to 1.325V when I have it at 3.2Ghz. I run it at 1.3525V when I'm running it at 3.373-3.4Ghz. After voltage droop, it comes out to 1.3 for 3.2Ghz and 1.32 or so for 3.4Ghz. To actually get the full rated voltage of 1.3525V, I have to set the voltage in my BIOS to 1.362V. I've run it all the way to 1.45V which translated to 1.4V after voltage droop. I got my E6600 to 3.5Ghz with that voltage, but loaded temps quickly hit the upper 60's and settled at 71*C after an hour of benchmarking.

At 3.5Ghz, I got random BSoD. I blame this primarily on the chipset itself. I may be able to get it more stable at that speed by increasing the NB voltage, but I am quite satisfied with a 3.2Ghz and within spec voltage setting.

Cool deal. Just trying to get a comparison here. I was able to hit 3.5 on mine and was getting random weirdness. Temps were good, but sometimes it wouldn't fully load into Windows, I'd reboot and then it would. I backed it down to 3.2 and it's running like a champ now. Not sure of the voltage, but just wanted to get an idea of what you had so I could cross ref. with mine.

[Gig-O-Ram]

On 2.8Ghz my system seemed okay, but when I entered a game the system just froze up after about 5 minutes. This happened twice, only because after the first instance, I wanted to give the system the benefit of the doubt - maybe it was just a fluke - but when it happened again, after the same short period of time, I decided to back it off to the last good stable setting, which is where I've left it ever since and have had no problems.

I think the point made that any increase should be looked at as a bonus is a good frame of thought to be in. It's how I looked at it. I bought the CPU that I could afford at the time, and though it's stock speed (2.2Ghz) was less than the 3.2Ghz P4 I came from, I wanted to try to get a little bonus speed if I could. After playing with the settings for a while, I did. And knowing what I was doing could be dangerous, I chose not to go balls-to-the-wall on speed like I've seen some people do. I picked a good spot, and stayed there.

I've thought about trying to back everything down to stock settings and see if things are still stable, or if there has been some electron migration, which was brought up to me in another thread. But I don't know if that would yield a bad result or not.

[Quakindude]

I'm not totally convinced of electron migration being an issue when overclocking on air. I think it would be an issue once people start using TEC/Phase change coolers and warping their chips with lots of voltage and high as hell FSB's.

Anywho, if you have Farcry, try playing that game after doing CPU/RAM overclocks and/or video card overclocks. That game is so sensitive to overclocked components it isn't funny.

Also, Prime95 is a very good way to see if your memory/CPU overclock is stable.

[Gig-O-Ram]

Originally Posted by Quakindude

I'm not totally convinced of electron migration being an issue when overclocking on air. I think it would be an issue once people start using TEC/Phase change coolers and warping their chips with lots of voltage and high as hell FSB's.

Anywho, if you have Farcry, try playing that game after doing CPU/RAM overclocks and/or video card overclocks. That game is so sensitive to overclocked components it isn't funny.

Also, Prime95 is a very good way to see if your memory/CPU overclock is stable.

About Farcry (which I do have, BTW) do you mean it's sensitive to overclocked parts in a good way, or a bad way?

I'm pretty sure I've played it on this system the way I have it set, but I could be wrong. It's been a long time since I played it at all. I don't have it installed at the moment, but maybe I should put it on and see what happens. I know FEAR only got a little bit punchy on me because my video card - which is on nothing but stock settings - got really hot while playing it. Otherwise, it played better than I expected it too, given that I had a the video settings on max!

I have used P95 before, but probably not for as long as some do. I'll let it run for a short time, but I've never run it for like 24hrs or anything. Anyway, I've never run into issues though.

[One4yu2c]

Originally Posted by Gig-O-Ram

About Farcry (which I do have, BTW) do you mean it's sensitive to overclocked parts in a good way, or a bad way?

He means that if an overclock is unstable, FarCry has a good chance of discovering it. I've also found Super Pi's lengthy 32M calculation to be pretty good at rooting out unstable OCs.