Trouble on Overclocking my Core 2 Quad Please Help!!!

Aug 10, 2018
18
0
10
Hello everyone, here are my specifications:
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

So, it´s been 2 weeks since i started trying to overclock this processor.
First i got it working at 3.1 Ghz very stable, and then i got it to work at 3.3Ghz stable as well.
The voltages for these two frequencies were the same: 1.168. Both working fine with no instabilities.
Since the temps were quite low i tried to get some more out of my old CPU, so i tried getting it to work at 3.5Ghz.
So i had some blue screens, some freezes and some errors on Prime95, but i managed to get it to work using 1.256 V and the temps would get about 75C Max on very stressful teamfights on overwatch.
So here it comes the dumb part: i decided to try 3.6Ghz. I couldn´t get it to run stable at any frequencies (i tried getting it up to 1.3V). Overwatch was crashing and prime95 was finding torture test errors.
Because my temps were getting too high and i couldn´t get it to run stable i decided to go back to 3.5 Ghz, and here my trouble started.
When i got it back to 3.5 Ghz using the same voltage i used before (1.256v) overwatch would crash and prime95 would find errors again. The thing is, i did get it to run stable on these configs.
When i increase the voltage the crashes occur more frequently, when i get them around 1.256 they occur less frequently. I tried increasing and decreasing in many amounts, i even tried to get it back to 3.3Ghz (a frequency that i had never seen any crashes or errors or anything before) and the crashes still appeared.
There is one more thing: Doesn´t matter how much i increase the VCORE, on both cpuz and HWMonitor the voltages won´t go higher than 1.168

I know it´s a bunch of text, but i really need some help! i really can´t afford to get an upgrade right now.

Here are the BIOS settings i have running right now:
CPU multiplier: 8X ( the maximum the bios will let me get)
FSB MODE : Unlinked
FSB: 1700
Ram: 800
Voltages: VCORE: 1.256, all the other voltages on auto.
Speedstep: Disabled
C1E: Disabled
LoadLine Calibration: Enabled
 
Solution
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...

mgallo848

Commendable
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)
 
Solution