Sign in with
Sign up | Sign in
Your question
Solved

Possibly fried something! Computer works, Boot Device LED is lit, no display to monitor

Last response: in Motherboards
Share
March 27, 2014 11:34:24 AM

So I just built my first PC and it went great! Got it up and running, gamed on it for 2 days, everything was perfect.

Then, like a freaking idiot, I powered down the computer so I could move it, but I didn't flip the switch on the PSU when I unplugged/plugged it in. Now, the computer boots up like normal, but nothing is displayed on the monitor, nothing. Neither HDMI or VGA.

When I power the computer, the motherboard goes through it's check, the LED's on the mobo blink in sequence of the system check, and then it shuts off for a moment, then starts again. When it starts again, it goes through the same process, but this time it makes it to the POST beep, a single beep (just like it has always done) but the Boot Device LED stays lit (and the computer doesn't shut down like it does the first time) and the monitor cannot detect the computer (not a monitor problem, I checked).

PLEASE tell me I didn't fry the motherboard because I bought Windows 7 OEM and I can't afford to replace both.

Asus Z87-A motherboard
1 8gb stick of RAM (which I've removed, replaced)
1tb HHD (Seagate)
ASUS Nvidia GeForce GTX 660 GPU
Raidmax 600W PSU

Best solution

March 27, 2014 11:45:15 AM

You won't need to replace your Windows 7. It's meant to be used on one machine, but MS is aware that motherboards aren't immortal. You may not even have to re-install, but you may need to re-activate. They'll let you.

As far as what's broken goes, you might also try connecting your monitor to the motherboard's video output (after you pull your video card). If you can't boot with just motherboard, CPU and RAM, you'll at least know your video card is probably okay.
Share
March 27, 2014 11:56:32 AM

Tukk said:
You won't need to replace your Windows 7. It's meant to be used on one machine, but MS is aware that motherboards aren't immortal. You may not even have to re-install, but you may need to re-activate. They'll let you.

As far as what's broken goes, you might also try connecting your monitor to the motherboard's video output (after you pull your video card). If you can't boot with just motherboard, CPU and RAM, you'll at least know your video card is probably okay.


Good to know about the Windows thing. I will try removing the video card when I get home (I'm at work now) but the response is greatly appreciated!!

So even though the video card seems to work ok (fans spinning) it could be blown?
m
0
l
Related resources
March 27, 2014 12:54:46 PM

It's very unlikely to be a problem with your video card, but I usually try to troubleshoot backwards from the obvious to the less obvious, with careful regard for what's easiest :)  The video card and the PCI slot can be hurt by a surge, and it's an easy check, and it gives you something to do (and ammunition if you end up talking to a tech).

So, for me, I'd pull those first, and see if booting with motherboard video gives you a different result. If not, then I'd disconnect the monitor altogether. Then try the RAM in each slot. Then pull the RAM altogether. It's a pain in the butt, but if the tech you talk to (if you have to talk to a tech) may very well ask you to do all of these things before they'll admit there's a problem with your motherboard.

One final thing. Don't assume that what you did (unplugging,plugging) had anything to do with your problem. Maybe it did, and maybe it didn't. I have seen PC components fail for many reasons, often between a simple off/on operation, and new (or relatively new) components are far more likely to do that than an older component. It's the nature of the beast. If you do end up having to talk to a tech before they issue an RMA, let him/her/it lead the troubleshooting. Don't give them an easy out by suggesting you broke it. Don't lie, but don't cut the troubleshooting short :) 
m
0
l
March 27, 2014 4:58:59 PM

You replaced the ram or just moved it to a different dimm slot? I had a very similar issue and it turned out to be a faulty stick of ram.
m
0
l
!