Boot issue (No POST)

[SizableRapter]

Hey LTT Forums,

 

 

Earlier my Desktop Crashed while playing a game (hasn't happened before), the monitor hung for a good six, eight seconds before the display input wasn't found, Now after this happened I tried booting the system back up, everything spun up (GPU(s) fans, fans, hard-disk), so a googled around and saw resetting the CMOS might (I use this lightly), work. After attempting to reset the CMOS i put the battery back in booted up the system where everything did exactly the same after booting right after the crash.

 

Now to be quite honest in the current situation I'm thinking the Board is pretty much dead, but I'm not 100% sure thats why I've come here to see if anyone is able to help me in this situation, as everything has been fine for a good six/seven months.

 

- Austin

[C0LL0SS0S]

plug the speaker in and tell us which code it beeps when booting

[SizableRapter]

 

plug the speaker in and tell us which code it beeps when booting

 

 

It posted fine this morning, it only after this crash I've got nothing from it, nothing is actually being "bleeped" while booting.

[JeffreyEagan]

Your board is most likely dead.

[SizableRapter]

Your board is most likely dead.

 

Exactly my thought, just need some insight on why out of the blue the system would crash and the board well die.

[JeffreyEagan]

Exactly my thought, just need some insight on why out of the blue the system would crash and the board well die.

Could be a short, could be a failed IC that burned out and bricked something, could have had too much current flow through a trace and cut the connection. Who knows.

[Master Disaster]

What exactly is it doing (or not doing) during boot, you never actually said?

What are your specs?

How exactly did you try the CMOS reset?

[SizableRapter]

What exactly is it doing (or not doing) during boot, you never actually said?

What are your specs?

How exactly did you try the CMOS reset?

 

While booting basically nothing, other than spinning up the fans (GPU, Cooler, other fans), booting the HDD and the SSD, optical drive. No beep at-all while booting (it normally beeps once after booting), other than that absolutely nothing.

 

Edit: I forgot to say, My Keyboard and Mouse are lighting up after I press the power button (usually they light up until the GPU Output is 'Outputing', and then turn off until its almost at the Login Screen), along with this the HDD Indicator is blinking as usual and any lights that are usual lit up are lit p.

 

 

I use a screw driver on the CLR-CMOS prongs with a screwdriver, I also tried removing the battery.

 

As for the specs I had them noted on a notepad, I'll have to find that to get you the exact specifications.

 

But off the top of my head.

8GB DDR3 Ram

AMD-FX (Socket AM3+)

Gigabyte GA-990FXA-UD5

XFX R7900 Series Double-D (removed the other two to check if it was a GPU issue)

[Master Disaster]

Did you unplug the power from the machine before shorting the jumpers?

If so then unplug everything non essential to boot, all SATA devices, any additional PCIe cards except one GPU, all USB devices and all ram except for one stick, try again to boot. If it still fails repeat with each stick of ram until you've tested them all.

[SizableRapter]

I did unplug my system while doing this.

 

I'll unplug everything now that isn't really needed and see if that resolved my issue (FYI: I only have on stick of ram), and if this doesn't work should I expect that my Board is bricked?

 

Update: Nope, that isn't help with the issue.

 

Did you unplug the power from the machine before shorting the jumpers?

If so then unplug everything non essential to boot, all SATA devices, any additional PCIe cards except one GPU, all USB devices and all ram except for one stick, try again to boot. If it still fails repeat with each stick of ram until you've tested them all.

[SizableRapter]

I did unplug my system while doing this.

I'll unplug everything now that isn't really needed and see if that resolved my issue (FYI: I only have on stick of ram), and if this doesn't work should I expect that my Board is bricked?

Update: Nope, that isn't help with the issue.

[Master Disaster]

Finally remove and reseat the CPU. Only do this if you've got heat paste mind.

If that fails then its likely a dead board.

[SizableRapter]

Finally remove and reseat the CPU. Only do this if you've got heat paste mind.

If that fails then its likely a dead board.

I'll probally buy a new board to be honest better safe than sorry, and no I don't have any thermal paste let alone anything to clean it, looks like I'm rebuilding

[Master Disaster]

I'll probally buy a new board to be honest better safe than sorry, and no I don't have any thermal paste let alone anything to clean it, looks like I'm rebuilding

Isopropyl Alcohol is just about the best cleaning fluid you can get, you can get it at Chemists if your in England, USA I have no idea.

Your gonna have to clean it up anyway when you change out the board.

[SizableRapter]

Isopropyl Alcohol is just about the best cleaning fluid you can get, you can get it at Chemists if your in England, USA I have no idea.

Your gonna have to clean it up anyway when you change out the board.

 

I'm ware of that, Just I'm not really bothered about buying a new board right away before I contact Gigabyte about the issue, along with AMD. Whats getting me is the fact that the Computer restarted after the "crash", baring in-mind that I had a game running the background while I was viewing a site and talking to someone on skype, this whole thing has really got me thinking about what could have caused the issue (as a month or so before one of my SSD's died out of the blue).

[SizableRapter]

I'm ware of that, Just I'm not really bothered about buying a new board right away before I contact Gigabyte about the issue, along with AMD. Whats getting me is the fact that the Computer restarted after the "crash", baring in-mind that I had a game running the background while I was viewing a site and talking to someone on skype, this whole thing has really got me thinking about what could have caused the issue (as a month or so before one of my SSD's died out of the blue).