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

[Dark Mantis]

Well something is faulty and you said they checked everything else out and was ok. Therefore the CPU must be faulty or at least incompatible.

[Darby]

Nope, I didn't send the CPU when I returned the board.

I think the solution will be to buy me a new CPU and try to sell my old rig to a friend to get the money back.

[Dark Mantis]

That's a definite way to lose friends quickly 

[Darby]

Hehe, the old rig works perfectly actually (yeah, you might be wondering why I updated in the first place )

[Dark Mantis]

It's the price we pay for having this hobby! 

[Darby]

*sigh*... Well I got the mobo back from the store and I even bought a new CPU, this time a Phenom II X6 1055T 125W, and guess what? Same 11 beep-code from the mobo. I must be missing something somewhere. The funny thing was I chose the GA-890FXA-UD5 over the Crosshair IV Formula because I was afraid it would have the heat problem. It seems that I can't handle a mobo from Gigabyte.

Any ideas on what I might be missing?

[Dark Mantis]

I am a bit busy right at the moment but I will go through the entire thread again and see if I can come up with the answer. I will post again later.

[absic]

OK,

I have gone back through the thread and I am at a loss to explain what is going on.

The only thing that gave me cause to ponder was your Graphics Card. Have you tried swapping that for something a little lower spec?

Ooo! Whilst typing this I just had another thought, what keyboard and mouse are you using? Are they  OK? I have seen so called DOA Systems spring to life with a different keyboard and or mouse.

[Darby]

I will try my older 9800GT as we write (). I'm using a SteelSeries Xai Laser with Logitech Illuminated, both working prefectly with this netbook and my old system.

[Darby]

Nope, same error with the old card aswell. Been thinking a bit and after reading the interesting information absic posted about memory speeds and the amd memory controller, could it be that the RAM won't underclock itself to 1333Mhz but rather keeps running at 1600Mhz creating this beep code? It won't explain how the other got the same beep code but if this error signals a memory problem that could be the problem. Just a thought...

Edit: scratch that, got a post with the old card however with using the lower pci-e x16... hmm

[absic]

It's a puzzle and that's no doubt.
It is always much harder to diagnose a problem at distance but I am forced to admit to a lot of head scratching here.  

I would suggest trying a basic mouse & keyboard just to totally eliminate the Logitech ones as the cause of the problem as there have been occasional issues with Logitech before.

If that doesn't work then try the different Graphics Card.

If that doesn't work try a different monitor. (Sounds stupid but we have had a couple of problems on the forum recently that were due to incompatible monitors)

I'll keep thinking and I'm sure Dark Mantis will offer further advice and/or moral support.  

[Darby]

Hurray, I got a POST, however with my old GFX card in the other pci-e x16 slot, I'm now going to try to get my new GFX card working using the same slot...

UPDATE1: Got a POST with my "new" GFX card, however only with one RAM connected and using another set of pci-e power cables...

[Darby]

UPDATE2: Found the problem, a faulty RAM-stick (and it was of course the one I used when I first tested running the system on one stick) as I got the system working using the default PCI-E power cables and got the system to post using the other RAM. A second RMA seems to be the solution to my problem noew located problem (deja vu...)

[absic]

Oh well, all's well that ends well....... I hope!

Good luck with your new RMA and let us know how things go.

[Dark Mantis]

A very good reason to have checked it with Memtest86 at the beginning. Ah, hindsight is a very wonderfull thing