Having issues with overclocking your Core 2 Quad? Need some assistance!
Having issues with overclocking your Core 2 Quad? Need some assistance!
Hello everyone, here are my setup details:
CPU: Intel Core 2 Quad Q9400 2.66Ghz
MOBO: Asus Striker II Formula
RAM: 8GB (4X2) DDR2 800MHZ
GPU: GTX 650 2GB
PSU: 500W
OS: Windows 7 Ultimate 64-bit
It has been two weeks since I began attempting to overclock this processor. Initially, it functioned smoothly at 3.1Ghz with stable performance, and later reached stability at 3.3Ghz as well. The voltage settings remained consistent at 1.168 for both frequencies, showing no instability.
When temperatures were low, I attempted to push more performance from my older CPU, trying to achieve operation at 3.5Ghz. During this phase, I encountered blue screens, occasional freezes, and errors in Prime95. Eventually, I managed to run it using 1.256V, with temperatures reaching approximately 75°C during intense Overwatch sessions.
The next step was to try 3.6Ghz. However, stability remained elusive across all frequencies, with attempts to reach 1.3V also failing. Overwatch would frequently crash, and Prime95 reported persistent test errors.
Despite this, I achieved stable operation at 3.5Ghz using the same voltage (1.256v). When I increased the voltage further, crashes became more frequent, while lowering it to around 1.256v reduced them. However, even at lower voltages, crashes persisted.
Another observation: increasing the core voltage didn’t resolve the issue, as Overwatch would still crash and Prime95 would flag errors. Voltage levels above 1.168 consistently caused overheating.
I’m seeking guidance on this situation. I’m under pressure and can’t afford an upgrade at the moment. Here are the BIOS settings currently active:
- CPU multiplier: 8X (maximum allowed by BIOS)
- FSB MODE: Unlinked
- FSB: 1700
- RAM: 800
- Voltages: VCORE: 1.256, others auto
- Speedstep: Disabled
- C1E: Disabled
- LoadLine Calibration: Enabled
You have to consider the fact that 3.5 was extremely rare OC to hit even back in it's prime. Now here it is 10 years later and you tried pushing it (possibly) beyond its limits. There is a good chance the CPU is becoming "tired" and can no longer hit those numbers. It does happen.
Keep in mind everything I just said you could easily replace the word "CPU" with "motherboard" and it would still hold true. Trying a massive OC on 10 year old parts just isn't recommended unless you're OK with the possible consequences.
Having said all that, hopefully everything is fine and it's possible that you need to just do a factory reset in the BIOS and slowly start the overclocks from scratch until you find a stable limit again. Keep in mind it may...
You have to consider the fact that 3.5 was extremely rare OC to hit even back in it's prime. Now here it is 10 years later and you tried pushing it (possibly) beyond its limits. There is a good chance the CPU is becoming "tired" and can no longer hit those numbers. It does happen.
Keep in mind everything I just said you could easily replace the word "CPU" with "motherboard" and it would still hold true. Trying a massive OC on 10 year old parts just isn't recommended unless you're OK with the possible consequences.
Having said all that, hopefully everything is fine and it's possible that you need to just do a factory reset in the BIOS and slowly start the overclocks from scratch until you find a stable limit again. Keep in mind it may not OC as high as before. (This exact scenario happened to me years ago when I had an AMD 1100T)