Heres the deal. When I got my Q6600 a year ago, all I did was bump the FSB up to 333 for 3GHz (stock voltage in BIOS) and that has been working great up until now. It was never really Prime stable, but it NEVER crashed/locked up or blue screened for a whole year unless I tried to run Prime so I wasn't concerned.
Last night I decided to dust off the BIOS (which I haven't opened in a year) and go for 3.2GHz. I dropped the multi down to 8x and upped the FSB up to 400. I also upped the voltage in the BIOS to 1.450v. Made sure the RAM (DDR2-800) was running at 1:1 (stock) and it booted into Windows perfectly fine.
Prime95 ran for about an hour before the system locked up. Not a BSOD, just I lost all input (mouse, keyboard, etc) and I had to reboot. I wasn't completely upset as that got farther then my 3GHz OC got with Prime95 so I tried to do a real-world test that my 3GHz could do perfectly fine. I set x264 to encode a Blu-ray.
That failed after about an hour aswell.
I can deal with it failing stress tests, but I can't deal with it failing real-world stuff.
What am I missing?
As it sits now with the voltage set at 1.450 in the BIOS:
Last night I decided to dust off the BIOS (which I haven't opened in a year) and go for 3.2GHz. I dropped the multi down to 8x and upped the FSB up to 400. I also upped the voltage in the BIOS to 1.450v. Made sure the RAM (DDR2-800) was running at 1:1 (stock) and it booted into Windows perfectly fine.
Prime95 ran for about an hour before the system locked up. Not a BSOD, just I lost all input (mouse, keyboard, etc) and I had to reboot. I wasn't completely upset as that got farther then my 3GHz OC got with Prime95 so I tried to do a real-world test that my 3GHz could do perfectly fine. I set x264 to encode a Blu-ray.
That failed after about an hour aswell.
I can deal with it failing stress tests, but I can't deal with it failing real-world stuff.
What am I missing?
As it sits now with the voltage set at 1.450 in the BIOS: