It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Well, I've been playing my self build for months now, no problems, I was playing today, wanted to restart, hit restart, and bam.

No more computer.

The power comes on, the fans spin, but just all of sudden nothing on the screen, not even POST.

My motherboard has an LED indicator that is read d7, and when I looked that code up in my manual, it says. "No console input devices are found"

I don't have a clue what that means. Also, too, the book shows a capital D7 for that, while it appears to be a lower case d7 showing up on my LED. But searching the codes in my manual shows NO codes beginning with lower case letters. So I'm guessing the capital versus lower case means nothing in this instance???

WTF happened?? All I did was hit restart, something I've done a billion times. Now all of a sudden I have no computer!!!!

Dog Dammit!!!


ADDED IN EDIT: The only input devices I could think of were the keyboard and mouse, so I plugged them into different USB plugs, and now I'm getting a different code every time I try and turn it on.
Post edited July 02, 2013 by OldFatGuy
Seems like something wrong with your keyboard.
That error message normally means your keyboard isn't plugged in, which is extremely unlikely to be causing your system not to boot ...
Plug in your keyboard.
I know this might be silly to ask, but is your keyboard really plugged in the USB port? If you use a wireless model, are the batteries okay?
The case on the error code is irrelevant. The display on the motherboard cannot display a capital D so it shows a lowercase "d" instead.

Did you make sure your keyboard is still attached. Also is it wireless? I have never seen a wireless keyboard cause an issue like this, but perhaps if it is the batteries maybe low and or dead and the computer cannot detect a keyboard?? I'm just throwing stuff out there, but for some reason the BIOS thinks you no longer have a keyboard attached.
Yeah, as I added in edit above, I plugged my mouse and keyboard into different ports, and was getting different codes but now I am getting the same code every single time.

A3 - which according my manual is IDE enable.

My SSD failed?
avatar
OldFatGuy: Yeah, as I added in edit above, I plugged my mouse and keyboard into different ports, and was getting different codes but now I am getting the same code every single time.

A3 - which according my manual is IDE enable.

My SSD failed?
In my experience, when a system won't boot up at all like that, it's usually a motherboard failure, which is especially suspicious since it seems to be giving you mixed messages as to why it's not booting.
avatar
OldFatGuy: Yeah, as I added in edit above, I plugged my mouse and keyboard into different ports, and was getting different codes but now I am getting the same code every single time.

A3 - which according my manual is IDE enable.

My SSD failed?
avatar
yyahoo: In my experience, when a system won't boot up at all like that, it's usually a motherboard failure, which is especially suspicious since it seems to be giving you mixed messages as to why it's not booting.
I spoke too soon on the mixed messages.

It stopping at A3 every. single. time. now.

I've tried about a dozen times, and it stops on A3 every time.
Read the manual and try a CMOS reset, If the problem continues remove everything from the motherboard (expect the CPU). Reboot the system and add a component on by one. Maybe you find the faulty one.
avatar
yyahoo: In my experience, when a system won't boot up at all like that, it's usually a motherboard failure, which is especially suspicious since it seems to be giving you mixed messages as to why it's not booting.
avatar
OldFatGuy: I spoke too soon on the mixed messages.

It stopping at A3 every. single. time. now.

I've tried about a dozen times, and it stops on A3 every time.
But it was giving you a different message at the beginning and then changed to a different one later, right?

I still say it's a motherboard issue. When the system won't post at all, it's usually PSU or motherboard. It could be memory. I had that happen once where a system wouldn't post because of memory, but I've seen more motherboard failures with these symptoms than memory or even PSU.
Ouch. My sympathies, mate. Given the varying and inconsistent responses it gives you, I'm afraid the MoBo is probably gone. Still, try mitsadoor's piece-by-piece process.
I'm not sure but like others have said, this sounds like a mobo issue. But the best thing to try is isolate each variable one by one. For example, try replacing the GPU if you have one and test that. If you have spare RAM, put those in then try that.
Well, thanks for all the replies.

It's just so hard to fathom the mobo going just. like. that. No previous symptoms. I'm playing away, just as I have for months, restart my computer, and boom. Just. Like. That.

You would think there might be warning symptoms, like a failure to boot here and there. Or a freeze up now and again.

Man, NOTHING. I mean NOTHING. Working perfectly one second, and literally gone the next????

Wow.

This sucks royal ass.
Do you happen to use an UPS? You might want to invest into that, it can really save your hardware.
Apart from this i can't really add anything, you already received good advice.
Post edited July 02, 2013 by aduken