Asus Z97a Wont Post (Old Build)

Sep 19, 2018
5
0
10
First off this is NOT a new build. Worked flawlessly for 4+ years.

Problem:
Power-On the computer, fans spins up, the MOBO starts going through its LED blinking procedure before post. Boot Device LED comes on, stays on, and the computer does NOT post. If I restart it enough times (30+ times) it may start up. If it starts up, everything works perfectly. Having read the BOOT DEVICE LED, I replaced my Samsun 128gb PRO with a 250gb EVO and no change happened. The old PRO was showing a limited predicted lifespan (6months) according to a testing software. It has 8.37 TB of writes on it, and is only 3 yrs old. Regardless, the new SSD made no difference.
Im not sure where to look for a solution, before starting to replace parts. What can I test or do to fix this issue?

History:
I started noticing this problem about a year ago. But had not confirmed which LED was staying lit. I was usually just able to restart it once and have it work perfectly.

Parts:
Asus Z97a Mobo
Intel 4690K
Sapphire R9-280 (non-x)
32gb of GSkill Ripjaws 2133MHz ram 4 sticks
Corsair 750watt Gold Modular PSU
C drive (windows, and some programs) is 128gb Pro switched to 250gb EVO
D Drive is a Samsung 850 Evo (all programs)
E+F are Regular 3.5” Hard Disks for storage only.
 
I will give it a go tonight. The boot drive is never disconnected. I cloned the 128 to the 250, and left all drives attached. I have been able to boot successfully (after 30+ power-ons) so i know the drive is good. Just cant get it to start each time.

Just cant get it to post, cant even get to BIOS. If I see the ASUS symbol, it will start up fully, no problem. As you can imagine, most of the on-computer solutions involve a restart, and if i have to restart i get stuck in this problem again. Very frustrating.
 
Judging by the responses, im guessing this is not a common thing. I'll try ASUS support and see what comes back.

I cleared the cache on the CMOS using the jumper method, and tried every variation of of a single ram stick (with each stick), and only the boot drive connected. Eventually did fire up, but took many tries. Clearing the cache seems to have "helped" a bit. It seems like i have to boot fewer times now to get it to post. But more than once is still a problem.

Tried with the GPU back in, and all the ram back in, and with just the boot drive. Same as above.

Hooked up all my drives, same as above.


The issue remains that I cant get it to post. But if i can get to BIOS, it will start up perfectly.
 
32gb of GSkill Ripjaws 2133MHz ram 4 sticks

Without a part number or link to the memory, I wouldn't eliminate that as the problem.

Intel 4690K
Supported memory: DDR3-1333, DDR3-1600

Failed overclocking can lead to file corruption of the OS.

Just because you bought 2133MHz memory, that does not mean the memory is running at 2133MHz. Enabling XMP or just leaving the BIOS on default [Auto] settings can give different results.
 
Just leaving the BIOS on default [Auto] settings is not practical. Some people are afraid to change anything in the BIOS.

Nothing has been overclocked but your using memory for overclocking.

Repeated failed posts can lead to operating system corruption. I still couldn't say what 32gb of GSkill Ripjaws 2133MHz ram 4 sticks is or what it is running at. You may have 4 singles, multiple kits of two. It may be your choice of memory or memory settings in BIOS causing the PC to have trouble posting.

You can test for defective memory with MemTest86:
https://www.memtest86.com/
 
try a new cmos battery in case the old one went bad from age. try a test power supply see if the old power supply having issues (bad cap or part). on your mb see if a friend has a post it card see if the mb with one ram stick and a knonw good drive and onboard video still hangs at the same spot.
 
Took the machine into a repair shop. He said all the components work and respond except for the motherboard. He was unable to get a video output out of it, even when trying with known good components. Tested my power supply separately and it works fine.

The problem therefore lies within the motherboard.