crazy power oscillation

downspiral

Junior Member
Nov 6, 2007
2
0
0
Long story short, I had a power surge. I had a thermaltake water cooler which is an all inclusive type deal that just has a water block for the processor.

The pump on it failed after this surge, and when I'd attempt to start my box up, it would get far enough to start up windoze, but then overheat (this was before I knew it was doing so) and crash the system cold.

Fast forward to now. I installed an air cooler (asus silent knight, massive hunk of copper) and got everything hooked back up with a fresh layer of arctic silver on my E6600.

Now, when I start the box up, it starts spinning everything up, all fans and all for FIVE seconds, at which point it crashes itself for TWO seconds, then this is where it gets weird - it starts itself back up for another five seconds repeating this whole process infinitely.

I tried a different power supply while taking every card out of the board and nothing changed - same strange oscillation!

Have I fried my processor? Or do the masses think it's my motherboard?

I am ready to order a replacement E6600, but I wanted some opinions before I do that because as you all know, once you open the box that thing probably isn't going back, and it would *suck* to open it and find out the processor really wasn't bad.

THANKS in advance!
 

Harvey

Administrator<br>Elite Member
Oct 9, 1999
35,057
67
91
The surge may have fried one or more regulator circuits on your motherboard. First, if possible, test your CPU on another board. If it works, the problem is most likely on your motherboard.
 

downspiral

Junior Member
Nov 6, 2007
2
0
0
That's what I really wanted to do, the problem is finding another board that I could pop the dual core in :(

Thanks for the reply!
 

Harvey

Administrator<br>Elite Member
Oct 9, 1999
35,057
67
91
A local shop may be willing to test it for you for a nominal charge, maybe $25 - $40. You have to decide if it's worth whatever they ask or whether it's better just to keep stepping with new stuff and test the CPU, later.

I've got the same problem with a possibly bad socket 754 CPU or motherboard. :p