I am attempting to overclock my Q6600 ... going for 3.2 right now (8x400). Mainboard is Gigabyte P35-DS3L. Vista Ultimate 64. RAM is operating at spec ... no overclocking there.
After some playing and slowly increasing my vcore, I seem to have something Prime95 stable, however there is suddenly a new problem I can't explain, and I'm not even sure if it is related to the overclock.
Basically the last two times I have left the system running Prime95, I have come back to find it frozen, and the display is getting no signal. I have no choice but to reboot. However, upon reboot, I check the Prime95 logs and there are no reported failures. The last time Prime95 session ran for 8h (I left it while I was at work - but I could see from the logs that it was running for 8h) but it stopped at some point and ended up in this 'frozen' state.
I have a few other voltages topped up with a +0.1 just for the sake of stability ... FSB, PCI-E, DDR. Vcore is set at 1.38750 in the bios but cpuz reports it as 1.34 idle and 1.31ish under load (the infamous vdroop i have heard so much about).
Just wondering if this is something people have seen before. If the CPU core is unstable, wouldn't prime fail? Could it be related to PCI-E? I have it set to 100MHz so it shouldn't be scaling at all with my 400 FSB. Throughout my testing so far, Prime would typically fail pretty quickly (within 2h) and it would say so. Now I have no Prime failures, just system lockup. My temps aren't outrageous ... < 65ish under full load.
Any ideas?
After some playing and slowly increasing my vcore, I seem to have something Prime95 stable, however there is suddenly a new problem I can't explain, and I'm not even sure if it is related to the overclock.
Basically the last two times I have left the system running Prime95, I have come back to find it frozen, and the display is getting no signal. I have no choice but to reboot. However, upon reboot, I check the Prime95 logs and there are no reported failures. The last time Prime95 session ran for 8h (I left it while I was at work - but I could see from the logs that it was running for 8h) but it stopped at some point and ended up in this 'frozen' state.
I have a few other voltages topped up with a +0.1 just for the sake of stability ... FSB, PCI-E, DDR. Vcore is set at 1.38750 in the bios but cpuz reports it as 1.34 idle and 1.31ish under load (the infamous vdroop i have heard so much about).
Just wondering if this is something people have seen before. If the CPU core is unstable, wouldn't prime fail? Could it be related to PCI-E? I have it set to 100MHz so it shouldn't be scaling at all with my 400 FSB. Throughout my testing so far, Prime would typically fail pretty quickly (within 2h) and it would say so. Now I have no Prime failures, just system lockup. My temps aren't outrageous ... < 65ish under full load.
Any ideas?