GA-890FXA-UD5: No post (power error)

[Darby]

Basic information:
MB: Gigabyte GA-890FXA-UD5 Rev. 2.0
CPU: AMD Phenom II X4 965 3.4GHz C3
RAM: 4GB (2X2GB) Corsair DDR3 1600MHz C8 PC-PC12800
GPU: Sapphire Radeon 5870 1GB Vapor-X
PSU: Corsair HX850 850W
SSD: Intel X25-M 80GB
HDD: WD GreenPower 1TB, WD GreenPower 1,5TB & Samsung SpinPoint F1 750GB

Problem:
I just upgraded my system with a GA-890FXA-UD5 and 4GB of Corsair DDR3 RAM, the installation went smooth and without a single problem. When I first assembled the computer I used a Be-Quiet! Dark Power 650W

The system starts and everything runs, you can see the GPU-fan and the CPU-fan spinning (and all other fans connected to the motherboard aswell, you can hear the HDDs spinning up and the DVD-writer checking for a CD. But there is no post or boot indication on the monitor. I got the speaker for the case and plugged it in and listen to the beep-code. The beep-code contains of 11 short signals followed by a pause and then continues beeping. It does this in an infinite loop until the system is powered down.

I took a look in the manual and interpreters that as a Power Error, I tried another cable and also disconnecting everything except CPU, RAM and GPU, the problem still remains. I rebuilt the system just in case I forgot something, still no luck.

I now decided to buy a new PSU (just in case the 650W didn't deliver as it should, as 650 would be enough to run the system) and got myself a Corsair HX850 850W. I plugged it and to my despair, still the same beep-code. I now stripped the system to just the CPU and power cable just to check if I would get another beep-code this time, no luck still the same 11 short signal-loop.

I've also tried to reset the bios by removing the battery for a while and removing the motherboard and the PSU from the case to escape any potential short-circuit

As this is my first Gigabyte-board I'm unsure if I have missed something or if I just had the bad luck to get a defect board and need to request a new from the store.

And yes, I have connected the 8-pin 12V (even tried with a 4-pin).

Any help would be greatly appreciated as I already spent way above my initial budget.

[Dark Mantis]

Well you have already made a good start at faultfinding. You seem to have covered most of the obvious things. It would be worth removing the CPU and checking it for any damage.

[Darby]

Nope, the CPU is fine and I know it's working as the last time ran it was 48 hours ago. I also took out the motherboard from the case for a very close inspection and there is no indication of burned or damage circuits.

[Dark Mantis]

Well I think we can discount the PSU as faulty (mainly because I aslo use that one  ) so it is either the connections or the board. Try removing the RAM and graphics card and see what beeps you get.

[Darby]

Already tested that, still the same beep-code. It could be the power connections on the board is itself tho... never thought of that.

[Dark Mantis]

Yes look closely at the sockets on the board.

[Darby]

All the connections looks fine, even the power connections looks good. It seems to be the board then...

[Dark Mantis]

Yes I would have to agree. Take it back and get it changed if it was locally purchased if not RMA it. Better luck next time.

[Darby]

Aye, next stop RMA! Thanks for the help!

[Svindle]

I actually have the exact same thing going on. PC worked fine for about a week after i upgraded it, my current setup is:

Gigabyte 890FXA-UD5 (Rev 2.0)
4gb PC 10600 Corsair Ram (CT2KIT51264BA1339)
650 watt Corsair PSU
EVGA GTS 250
AMD Phenom II x6 1090T BE (@ 3.2ghz, stock speed)

When I power on the PC all the fans spin up, HDD's spin up, DVD drive checks for a disc, etc - Then I get 11 beeps from my system speaker. Much like the problems OP had.

I have, like OP, disconnected every peripheral from my PC. I have disconnected everything that is not necessary from the board, leaving only the CPU (and heatsink), RAM, and Video card connected to the mobo. Hell I cleared the CMOS with the button on the mobo (after the PC was powered down and the power cable disconnected). I even pulled the CMOS battery before I went to bed, woke up this morning and popped it back in. I have tried cycling both of my ram sticks through all 4 slots one at a time, all of which gives me the 11 beeps. The only time I get a different beep code is if I try to boot with no ram, then I get 12 beeps. I still get the 11 beeps, a pause, and then 11 more beeps, and a pause...so on and so forth.

Much searching through forums and various websites has not turned up any useful description of this beep code - only that it may or may not be a component of my computer that may or may not be working correctly. I have not had the chance to talk to Gigabyte customer service, as they are closed on sundays...

If OP is still watching this thread, did RMAing your board fix the issue? Or did you replace your ram?

Edit 1: Added a bit more description to troubleshooting and the cause of the problem.

Edit 2: This started as a system freeze as I was closing programs to turn my PC off for the night. I shutdown my media player (SongBird) and the system hung right there. I waited a couple seconds to see if maybe it was just some odd hardcore lag or something, but this wasn't the case. After about half a minute of waiting my system responded, but with horribly distorted audio that appeared to be stuck in a 5 second loop. I performed a hard shutdown and when I tried to reboot, I started having this problem.

[Dark Mantis]

The OP only posted this thread yesterday so there will be no feeback yet. We tried the motherboard without the memory and still had the same beep code. Actually your last remark sounds like a bad latency effect. Not that it helps much now.

[Svindle]

Oops, didn't even look at the post date. I hope this isn't an inherent problem with an otherwise outstanding motherboard -.-

[Dark Mantis]

It's only the second one I have seen on the forum so hopefully not.

[Svindle]

Any suggestions, anyone? I'm desperate to get this system back up and running asap. Seems odd that it can be running perfectly fine, without a flaw, one moment and then be completely dead the next. Albeit, I've yet to have a part break on me up untill this point...

[Dark Mantis]

Well basically if you have done as you say and the same as the OP then the fault we must presume is the same. I'm afraid it is an RMA. As a matter of interest were you running the memory in ganged or unganged mode? The only other possibility is the CPU but I feel there is more chance of the motherboard being the culprit.