Asus M5A97 DRAM LED solid and won't boot

[xNemesis]

Hi,
I just built my 1st Pc and it worked for a few days then earlier today I booted up my pc, logged in and everything went perfect so I went to the bathroom. when I came back my pc was frozen while booting. I turned of my computer and went to restart and it came up with the REPAIR WINDOWS or Continue Normaly so I went to repair just in case. A few moments after going pressing enter it froze again. I then restarted pc again and now it wont boot up. There is no video output and the DRAM_LED is staying solid and fans are running but wont boot.

Specs:
Case: Thermaltake V3 Black Edititon Mid Size Tower (With Stock 450w PSU)
CPU: AMD FX4100 (Stock HeatSink)
Graphics Card: PowerColor Radeon HD 6670 1GB
RAM: G.SKILL Sniper kit 2x4G
Motherboard: ASUS M5A97
HDD: Seagate Barracuda 500gb
DVD DRIVE: LG DVD RW SATA

Any Suggestion?
Thanks.

 

[Dawn1113]

By "no video output", I take it you cannot get into the BIOS at all? I hate it when that happens.

But moving on from that assumption, for starters, I would suggest that you try resetting the CMOS by removing the battery for a few seconds then putting it back in. (Before you do this, please check your mobo's manual for Clear RTC RAM procedure. Make sure you follow the instructions step by step.)

If still no joy, I'd try swapping out the RAM modules just to make sure it isn't faulty RAM.

Have you tried the reset button on the outer panel? Also, you may want to check that your GPU is properly seated. You never know. In fact, I'd check that everything is properly seated, including all the connectors and such.

Sorry I couldn't be of much help, but do stick around and wait a bit for the advice of the more tech savvy members.

 

[xNemesis]

Thanks for the help I'll try that now.

 

[xNemesis]

And what do you mean by " the reset on the outer panel"

 

[xNemesis]

It was faulty RAM going to get a new set of RIPJAWS and see if that works

 

[Dawn1113]

It was faulty RAM going to get a new set of RIPJAWS and see if that works

It's good that you nailed it right away. And -- you know what?-- I'd actually be a bit relieved it's just bad RAM. It could have been far worse: a mobo gone irreversibly awry, for instance. RAM is quite affordable nowadays.

Good job finding the cause so quickly.