Underclocking with SetFSB damaged motherboard permanently!

Extreme6800

Honorable
Sep 20, 2013
15
0
10,510
I was using setfsb to slightly overclock from windows without having to restart and go to BIOS every time for the last couple of months, and since I was leaving the system on for many hours downloading I decided to underclock the FSB to waste less power and produce less heat, and I selected an FSB freq that was slightly lower than the minimum allowed by the BIOS (half the CPU/FSB clock) to see if I could get even more downclock.

Then the PC froze, like it happened many other times when I attempted excessive overclock, but this time it did not startup again, even after I cleared/reset the CMOS and removed battery, the PC tries to power on, all fans and disks start working and then immediately powers off for about 2 seconds and powers on and off again in an infinite loop without posting or beeping.

I didnt know that you could damage hardware like that by underclocking, because all clocks set by SetFSB were gone when the system booted again and damage is only associated with overclocking and heat, but apparently I was wrong.

Do you guys know any solution for this? Is it possible to purchase a clock generator and solder it on the MB? (or maybe not since it is a socket 775 mobo)
 

Extreme6800

Honorable
Sep 20, 2013
15
0
10,510
I dont think so, this is a Core 2 Quad CPU, from what I can remember the clock generator and memory controllers only got integrated inside the CPU with the Core i series Nehalem cpu´s, I will consult the mobo manual, but pretty sure the clock generator is in the motherboard in all pre socket LGA1555 mobos.
SetFSB does not even work with newer CPU´s because of this.
 

Extreme6800

Honorable
Sep 20, 2013
15
0
10,510
Nevermind, problem is fixed, I was putting back the battery and the jumper too fast, CMOS needs to stay totally off without external power for about 2 minutes before it is properly cleared.
System is working normal again, still it is strange that the clock generator does not reset properly with system power off and ignores BIOS settings if set to very low clock.