CPU/motherboard says "no" when trying to overclock

SgtSpoon

Member
Dec 25, 2007
69
2
71
I've been toying around with my i3 530 machine since 2 weeks now, and it has run at all kinds of settings : all-stock, stock cpu with memory at 1600, cpu at frequencies ranging from 3Ghz to 3.66Ghz, and that all ran fine, without even requiring large voltage bumps, and the temperature never went over 50 degrees celcius.

I knew from the beginning that i would settle for a moderate overclock (3.5Ghz), but yesterday i was bored so i tried 4Ghz. I tried:
- BCLK 200
- memory multiplier 8x
- cpu multiplier at 20
- cpu, qpi and memory voltage only a slight step up : memory at 1.56 (default 1.5), QPI at 1.15 (default 1.1), cpu at 1.16 (default 1.1)

It failed to boot, and also failed to recover automatically like i've seen it do before. I had to use the clear-cmos jumper to get it up again. The system was fine after that i restored it to all-stock settings.

But now, even if i try to overclock it even slightly, it fails to boot again, requiring another cmos clear. Even when i try 3.04Ghz and memory at 1600Mhz.

Am i missing something, or have i permamently damaged something? I have always been very conservative with the voltages.

edit : just tried configuring the setting step by step and rebooting each time (not into windows, just seeing if it posts) to try and find what the problem was:
- disable load line calibration : boots
- disable C-steps : boots
- set voltages vcore/qpi/mem voltages : boots
- bclk from 133 to 140 : boots
- bclk from 140 to 150 : boots
- bclk from 150 to 160 (this is the 3.5 overclock i've been running rock-stable for a week) : boots
- try to boot windows : restarts automatically, fails to boot, need to clear cmos
 
Last edited:

Ben90

Platinum Member
Jun 14, 2009
2,866
3
0
I doubt you damaged anything with those super conservative voltages. Its probably some obscure BIOS setting you need to change that you forgot about.

Just to check, you can get into windows with stock settings correct? If you can't then you probably corrupted the OS somehow and may need to repair/reinstall.
 

SgtSpoon

Member
Dec 25, 2007
69
2
71
Apparently it just works again.

Either i indeed missed some setting, or my computer just needed some sleep :)

It now runs : 3.52Ghz, 1600Mhz memory, C-states enabled. And i'm going to stop fiddling now and keep it this way, i like the fact that i can keep the c-states enabled.
 
Last edited: