Sabertooth 990FX R2.0 CPU and/or RAM red leds problem

iis7cw

Honorable
Aug 9, 2013
18
0
10,510
Hi,I am having some problems with my new PC.
I bought it in components and i putt it all together(everything is fine here).
my PC:

Sabertooth 990FX r2.0
AMD fx-8350
8gb hyperX blu-->it's not on asus qualified ventdor list

When i try to turn on PC red cpu light turns on and everything work except monitor(thats becasue cpu doesn't work)

or

Cpu red led turns on and after that PC turns off

or

cpu red light turns off for 1 sec than turns off and then RAM RED LED turn on and PC turnd off after that

or

cpu red light turns off for 1 sec than turns off and then ram red led turns on for 1 sec then off 1 sec then on 1 sec and then system boots up


I've experienced all of the above

WTF is going on,is my MBO "broken" or is it because of RAM?

Please help,this is really frustrating to look at
 

iis7cw

Honorable
Aug 9, 2013
18
0
10,510


I managed to update bios to 1903 ,latest version
Sometimes my PC boots up fine!! But usualy it doesn't

???
 

iis7cw

Honorable
Aug 9, 2013
18
0
10,510
i tried every RAM combination,one ram,two rams,even another set of rams

still the same


Can this problem appear if there is no grounding in house?

Or my MBO is semi-correct?

I am using latest BIOS,1903...will it help if I downgrade BIOS?
 

iis7cw

Honorable
Aug 9, 2013
18
0
10,510


I am not sure am I going to be able to flash another BIOS...but if i succed which BIOS to flash?
 
Use the flashback.
Connect the 24 and 8-pin power cables, but don't start the board. Just make sure that the power supply is ON.
Unzip and rename the BIOS file downloaded from ASUS.
Save it on a FAT formatted USB stick.
Connect the drive to the Flashback USB port.
Press the Flashback button for 3 seconds.
Wait until the process finishes.
Unplug the power cord and remove the CMOS battery for few minutes.
Start the board.
If still the same, then try reseating the CPU. Use the stock cooler, if available.
If still no go, then I would RMA the board and/or the CPU.
They might be faulty, or got damaged during the troubleshooting process.