Quick Q6600 Overclocking Question

Associate
Joined
20 Feb 2009
Posts
748
Location
Perthshire
Got bored and thought i'd push my CPU a bit more for my crossfire setup.

Q6600 @ 3.5 Ghz

*1.5 V Core*

Been running Prime 95 for like 30 mins now and it seems stable I guess but temps are getting pretty scary, 71c on full load.

So my question, is it stupid to have it running at this temperature as i've read people don't like it to go over 65c ?

I was just gonna run Prime tommorow during the day and see how it fairs. I mean I read everyone on about 24 hours Prime test n stuff and don't see what the big deal is. It's not like it's gonna run 4 cores 100% in real life gamming ect and actully sustain thoes temps.

What do you guys think ?
 
71c is fine when stress testing, my own personal limit when i had a q6600 was 75c. At 3.8ghz, 1.512 vcore. It stayed at 68-68-62-62, albeit the cpu and TRUE were both lapped.
 
Thanks for the reply, well that makes me feel a bit better about it. How do you feel about the amount of time I should stress test it for ?
 
I'd stress it for 8 hours if I were you. Up to 80 degrees C should be ok on 100% load. It will never usually go 100% load anyway even in most games.

Or download Intel Burntest and run the maximum level of stress on 4 cores and see what happens.
 
8 hours of prime95 small fft is a good test for cpu stability, followed by 8 of blend to test ram. There are other test programs such as intel burn test and LinX, typically theese will generate higher temps than prime small fft.
 
Well I just put back in my other gfx card as was overclocking it with one out so that I could get to the jumper to clear CMOS, now I ran prime and temps went up to 76 and then failed :( Any ideas on why that would be at all ? Do you think having another card in there is stressing the mobo or something, should I increase PLL ?
 
I run my Q6600 @ 3.6ghz 400x9 / 1.460v temp dont go above 50 with the H50-1 cooler. I havent messed around enough to get a stable 3.8 - couldnt be botherd lol. but its easy doable.

Have you checked your memory settings etc? sometimes you have to lower the mem and give some more V to it (check your mem guidelines though)
 
Back
Top Bottom