Official GIGABYTE Forum

GA-MA785GM-US2H Continuous long beeps at POST

absic

  • *
  • 5815
  • 529
  • Never give up; Never surrender!
    • Bandcamp
Re: GA-MA785GM-US2H Continuous long beeps at POST
« Reply #15 on: October 10, 2010, 10:00:42 am »
Hi Dan,

As always, when this kind of problem occurs it is a problem to find out what exactly is causing the problem and, of course, you only have a limited time to RMA the board if it is the component causing the problem. I know this is frustrating especially as you have now gone and bought a new PSU (sorry about that) but, on the bright side, at least you now have one that will do the job.

What I would do, if faced with this problem is go right back to the beginning. I have checked and your choice of CPU is OK for the Motherboard, without a BIOS update so we need to be looking at why the thing won't start. The best way to begin this kind of troubleshooting is to put together the PC outside of the chassis. Get your motherboard and place it onto a non conductive material, I use the Motherboard box for this. Then add the CPU and cooler, 1 stick of RAM in the first slot and, if possible attach a PS2 Keyboard. Don't forget to connect your monitor to the appropriate connector on the Motherboard. Attach the 24 pin and 8 pin power connectors to the motherboard. If you do not have a set of test kit switches attach just the Power switch and reset cables from your case to the appropriate headers on the motherboard (manual page 28) and the speaker then try and start the PC. What happens?
Remember, when all else fails a cup of tea and a good swear will often help! It won't solve the problem but it will make you feel better.

Re: GA-MA785GM-US2H Continuous long beeps at POST
« Reply #16 on: October 24, 2010, 03:52:43 pm »
Sorry for the long delay.  I was out of town.

I pulled the board this morning and ran it outside of the case and had the same problem.  I pulled all the memory out and it was the same.  Then I ran it with one 1G stick only of a different RAM (and it was an older RAM that I thought was bad) and what do you know?  It works.

So it was my newer, better RAM that was the problem.

Today I'll put the whole thing back together.  Thanks to everyone for helping me out (and keeping me from rushing back to MicroCenter with what I thought was a bad board).

Dan