CPU fried after core unlock attempt?

[ZorMonkey]

I've had a Phenom II X2 555 BE running on a an ASUS M4A88T-M for a couple years now. I've had it running with 4 cores unlocked for a while ages ago, but stopped to do instability issues. Well, today I decided to try running unlocked again. I've done some memory, cooling, and PSU upgrades in the last year, and I was bored, so figured it'd be worth a shot. Worse case I put it back.

Well, I got booted to the Windows logo, and it just hung there forever. Rebooted, and it didnt even post. I cleared the CMOS, and still no post. I removed all cards, still no post. Swapped around memory, eventually removing it all, and nothing.

All fans and HDs are coming alive. The power and HD LEDs are not. The MemOk light keeps flashing. No beeps at start.

So my guess is that toying with the core unlocker for those couple minutes killed my cpu. Sound accurate? Anything else I can try?

 

[SonDa5]

clear CMOS on motherboard bios.

 

[SnowBeast]

I cleared the CMOS, and still no post. I removed all cards, still no post. Swapped around memory, eventually removing it all, and nothing.

He already cleared CMOS. Sounds dead board to me.

 

[SonDa5]

He already cleared CMOS. Sounds dead board to me.

I missed that. Happens alot when I am reading threads from a smart phone.

If BIOS has a back up BIOS switch try that.


Either put a different CPU in the MB to see if system starts or try the CPU in a different working MB.

 

[ZorMonkey]

Well, I found part of the problem. Evidently when I was clearing the CMOS I knocked the cpu power cable loose. I guess I had been running with a loose cable for months! Now I need to figure out what else is broken,, or what I broke while troubleshooting...

Now I get lights and beeps, but still no video. Unfortunately the beep codes haven't been much help. I get one short beep almost right away, then after a few seconds the hd light will come on for a second, then I get 2 more short beeps. Not one long, two short. More like one short, 2 short if anything. I get the same beeps with any combination of memory installed. With no memory it beeps like crazy.

Now I'm leaning towards a dead motherboard, but still not too confident. I could probably try new memory easily enough, but I'm betting that all of my memory didn't go bad at the same time

 

[ZorMonkey]

ZorMonkey, you're an idiot. 2 short beeps means "Hey you cleared the CMOS and I can't boot until you set the system time." Plus, either the bios or your cheap hdtv aren't able to display the message over hdmi. Plug in a vga monitor, and you'll be able to fix everything up.