intel core 2 quad q6600 kentfield g0 overclock

Having RAM with a higher frequency allows for higher FSB speeds, you can circumvent this (even if your case) by putting the RAM:FSB ratio on a divider. That way the speed of your RAM won't impact your overclock.

So, short answer is no. Long answer is yes.

Terronium 12 is correct, and I too agree.

Everyone has different guidlenes as to what a stable result in Prime is. Personally, I say 10-12hrs.
Some will say 8hrs is enough, but I have seen Prime fail (meaning unstable) at the 9hr mark.
But I think all will agree, 1 hour is not at all long enough. Not even close. So keep testing, just let it run overnight.


With a FSB, how much you can OC will depend highly on not only your settings, but the RAM itself.
As Terronium 12 mentioned, higher RAM will allow for higher OCs. This is why many OCers want 1066 Mhz RAM. its gives more Headroom.


Also, you probably do not want to push it too high with a stock CPU cooler.
So long as you stay at 65C or under (fully loaded) you should be fine. A better CPU cooler will allow for higher clock speeds in that temp range.

I'm not sure what you're asking. RAM won't help hibernation as I'm almost certain that's hard drive-dependent.

You're not going to "break" anything. Worse case scenario is the system halts -- you restart the system and perhaps adjust the voltage(s) a bit. I'd suggest reading a tutorial before doing anything further if you think you're going to break something.

sygnus21 said:

This of course will depend on chip, RAM, and motherboard, and heatsink used. BTW your temps are normal for what you're running given the heatsink you have.

I said that, you drunk.

So long as you watch your tempratures, and they stay in the range as recommended, Prime will not break your CPU.
And in fact, even if the CPU does get too hot, it will throttle itself and shutdown to prevent damage. But this is a worse case scenario.

As mentioned earlier, Id shoot for keeping it at or below 65C under load.

If its unstable, you get an error, many times a rounding error, and the test stops on the core that failed.
This is just an indication it is not stable and is making mistakes, but will not harm the CPU.