Asus X-99 A only boots to bios

Sindorius

Honorable
Dec 27, 2012
7
0
10,510
Hey everyone I need some help with a new computer I just put together. When I turn it on everything seems to be recognized fine (sees my gpu, knows i got 16 gigs ram, knows my cpu is there, remembers my bios settings) but I get a black screen with a flickering cursor then it boots straight to bios---no messages or anything. My specs are as follows:

Cooler Master Storm Stryker Full Tower Case
Corsair Dominator 4x4 GBs DDR
Asus X99-A Motherboard
Intel i7 5820K CPU
Gigabyte G1 970
Cooler master silent pro 1000W psu
Kingston HyperX 128 GB SSD (boot drive)
HGST 3 TB HDD
Seagate 500 GB HDD

Now I was using the same psu and hard drives in a pc before for a couple years and they all worked completely fine. But with new pc will not boot past bios at all. It recognizes all my hard drives as well, and all drives are in AHCI mode. I've tried disabling secure boot, fast boot, enabling/disabling CSM boot, setting kingston as top boot priority, unplugging every hard drive except the kingston, updating bios, and even unplugging all USB devices. Still boots up to a black screen with a flickering cursor then the bios. Anyone have any idea what might be wrong here?
 
Solution
What were the drives at on the prior system, if drives were set to IDE in the BIOS then it won't see them, try booting to a OS DVD and see, or try setting the drive selection type to IDE or possibly even RAID

Sindorius

Honorable
Dec 27, 2012
7
0
10,510
Yeah I wasn't too sure what they were set to previously, I was fairly sure it was AHCI but I don't know. Coincidentally messing around with IDE/AHCI in the BIOS fixed it somehow and finally booted, though I don't think I did anything I hadn't tried before. I hate not knowing what was the problem but hey, the problems fixed. Thanks for you help Tradesman.
 

ncgmcpherson

Distinguished
Apr 14, 2008
2
0
18,510
I am having a similar issue with a similar setup, except no HDDs just two internal 512gb Samsung 840 EVOs and same model external on USB3 for backup. Anyway, the blinking cursor. I have found removing the fast boot option in the BIOS so the system fully initializes before booting up gets rid of most of this problem.

I say most because occasionally something is still happening. Offhand it looks to me to be more Windows related. i.e. I get the POST beep, the Boot screen shows up showing the BIOS piece of the bootup, and then when it blinks over to the Windows 8.1 portion it will on occasion hang. I am thinking it's probably Windows 8.1 because of its integration via UEFI. I have Windows 7 and overall did not experience this problem, other than the Fast Boot. Admittedly, I've been fighting this for 2 months now. Getting 80% there has been as far as I've gotten so far.
 

qasasa

Reputable
May 13, 2015
2
0
4,510
I have a similar setup, i7-5930k on rampage 5 extreme, sli gtx 970 g1, 32gb ram and 1x 256 samsung 850 pro ssd + a bunch of 4tb hdds. 20% of the time the boot would stuck at the blinking cursor just before the windows logo. there was one time that only 1 gfx was detected but that was just once. I just disabled the fast boot option and I'll see if it fixes the problem.
 

Sindorius

Honorable
Dec 27, 2012
7
0
10,510
Yup I still have a similar problem happening. Now I barely ever get the boot problem at the blinking cursor, now it gets to the 'Starting Windows' page and just freezes there. That color window animation never appears, or freezes while it happens. I originally fixed this by setting my drives back to IDE mode which I guess they were in, though I was sure they were installed as AHCI. I'm really thinking its the motherboard here, and its not an issue the bios updates have solved yet either, which makes me afraid its a defect with the boards themselves. If it is I think ASUS owes us all some new working boards.
 

Sindorius

Honorable
Dec 27, 2012
7
0
10,510
I've heard disabling booting the usb with the computer boot might fix the problem, I'm going to try that and give it a week and see what happens. ASUS is making me sad with this generation of tech =(
 

chompi

Distinguished
Jan 27, 2011
2
0
18,510
I had the same issue and it turned out to be miss labeled devices...

My SSD had the name of my HDD, so i swapped the devices in the boot priority menu and it worked.. really strange...

Edit: It turns out the device labels are not wrong, the problem is my boot manager is installed on the hard drive and not on the SSD.