I just fried my computer. Need some help here. (solved)

[Slick5150]

So I was just trying to move some wires around inside my computer, and I accidentally pulled the wires off of the switch for my cold-cathode tube which came into contact. Well, apparently that's not a good thing, and several sparks later my computer shuts off.

Now, I can tell the motherboard is getting some power anyways as the lights on the ethernet port will light up, but the PC will not power on. Is there any way I can figure out what happened, and what may have died? Does it seem more likely that the power supply got fried, or could the motherboard and other parts have been damaged?

Thanks for any advice.

 

[John]

pull the power cord from the power supply and let it sit that way for 2 hours. Plug the power cord back in and see if your system will POST.

 

[amdskip]

Originally posted by: John
pull the power cord from the power supply and let it sit that way for 2 hours. Plug the power cord back in and see if your system will POST.

Hit the power button too to kinda discharge the system. Also reset the cmos if need be.

I did a similar thing once messing with the cold cathod wiring and I fried a brand new seagate 60gb hard drive

 

[Slick5150]

Ok. I left it unplugged all night, cleared the CMOS, no go. Like I said, the motherboard is getting some power anyways as the ethernet port is active, but hitting the power button doesn't do anything.

Any ideas on a next step?

Thanks again

 

[EverCraft]

There's are alot of things that could be wrong, your motherboard being dead is one of them. But try some simple things first, like changing the power switch. This has happened to me twice, and just pulling the plug and letting the PSU chill solved the problem once. The second time I just took the whole thing apart and put it in a different case with no drives, and it ended up working ok.

 

[Slick5150]

Problem has been solved. Thanks guys.

I got home from work today and powered it on, and it booted up. Go figure.

 

[LeetestUnleet]

Originally posted by: PinwiZ
Problem has been solved. Thanks guys.

I got home from work today and powered it on, and it booted up. Go figure.

Careful - I had a similar problem and it went away for about a month, but now it's back