GA-X99-UD4 can't go to bios setup

[lisboa]

Please can some one help me!! It boots with no problem in the windows 8 but when I try enter bios setup in a cold boot it freezes in a blank screen. So I disconnected all sata hard disk and it goes to bios. What is happening with Gigabyte boards?

[dmdilks]

It might be windows 8 causing the problem. Because windows 8 uses UEFI and it will boot really fast.

Try to just disconnect the drive that has windows 8 on it and see what happens. All I can say is update the bios.

All of the X99 boards are having problems. I have the same board and so far I have not had any problems.

But again I'm not running or will not run windows 8. Plus I'm a Microsoft Partner too.

 

[lisboa]

It might be windows 8 causing the problem. Because windows 8 uses UEFI and it will boot really fast.

Try to just disconnect the drive that has windows 8 on it and see what happens. All I can say is update the bios.

All of the X99 boards are having problems. I have the same board and so far I have not had any problems.

But again I'm not running or will not run windows 8. Plus I'm a Microsoft Partner too.

If I disconnect the driver that has windows 8 it will go to Bios. But it should not be like that.

[dmdilks]

It could be that drive that is causing the problem. I have had brand new drive that are bad. Do you have another drive that you can install windows on and see what happens.

[Extradry]

It could be that drive that is causing the problem. I have had brand new drive that are bad. Do you have another drive that you can install windows on and see what happens.

I have the exact same problem on the same board (Win7 btw). All drives work properly. It will boot up into windows with all drives available, but as soon as i try and enter the bios(updated to F9) it will just hang there with a blank screen. I have tried each drive individually with the same issue (2 SSD 2 SATA 3.5'). Anyhow i will try a few different settings in the bios when i get a chance just really annoying having to disconnect all the drives eveytime I enter the bios.

[dmdilks]

How do you have you drives connected. The last 4 by themselves are standard sata device connection.

I have the same board and I have 2 SSD, 3 HHD, DVD, & DVD/rw.  My DVD drives are in the last 4.

[Extradry]

How do you have you drives connected. The last 4 by themselves are standard sata device connection.

I have the same board and I have 2 SSD, 3 HHD, DVD, & DVD/rw.  My DVD drives are in the last 4.

I have tried just the boot SSD in both first two and the last 4 on its own to no avail. What is your exact setup? Maybe its a setting in the bios I overlooked.

[dmdilks]

I have my 2 SSD setup in raid controller. The other thing is how did you set up windows just normal or with UEFI. Does it boot up with a windows boot manager in the bios for first boot?

But when first set up the computer before I got the 2 SSD I ran it in AHCI and normal boot no UEFI to make sure everything work.

[dmdilks]

I just double check everything to make sure how the drives are connected.

#1 SSD - #2 DVD drives - #3 WD 10,000 rpm drives

In the bios the sSata controller is set to AHCI

The Sata controller is set to Raid. Plus the SSD's show up as [UEFI sandisk] & [Intel Volume 0] in the bios as the 1st & 2nd boot.

It was first set up with [Intel Volume 0]. But when I updated the bios it now has [UEFI sandisk] too. I can boot to either one of them.

[Extradry]

I just double check everything to make sure how the drives are connected.

#1 SSD - #2 DVD drives - #3 WD 10,000 rpm drives

In the bios the sSata controller is set to AHCI

The Sata controller is set to Raid. Plus the SSD's show up as [UEFI sandisk] & [Intel Volume 0] in the bios as the 1st & 2nd boot.

It was first set up with [Intel Volume 0]. But when I updated the bios it now has [UEFI sandisk] too. I can boot to either one of them.

Well so I pulled all the drives out and set the PCH to RAID and it worked! Although i had to go back to ACHI and into windows to change the registry from ACHI to RAID but it worked. Thanks alot mate that had me stumped for a while!

[dmdilks]

Well so I pulled all the drives out and set the PCH to RAID and it worked! Although i had to go back to ACHI and into windows to change the registry from ACHI to RAID but it worked. Thanks alot mate that had me stumped for a while!

The thing is on that Intel controller the AHCI & Raid are basically the same. On the other controller you can only run that one IDE or AHCI. Now if it is working that way that is all that matters right.

[Curvin]

I have just encountered this one as well.

Windows 7 Pro SP1 x64 , so it doesn't have nothing to do with Windows 8.

Samsung 850 Pro SSD / Seagate 1 and 2TB SATA HD's.

X99 UD4 Rev 1.0 BIOS F11 and F12 , it will not enter BIOS if any SSD's or HD's are attached. aThe work around of  shifting the controllers to RAID from AHCI is not acceptable to me , Gigabyte need to address this directly and correctly.

I have a development/test system using the same board which is on an earlier BIOS ( F5 ), and it does not display the behaviour, so it is something that has been introduced in the later BIOS's.

An interesting point is that I had managed to do a final configuration of the BIOS after flashing the latest official F11 BIOS , with all HD's attached, but since that initial set up I have not been able to enter BIOS with SSD/HD's attached.

V.C

[DropBear]

As it turns out, the Samsung 850 series SSDs are not currently on the qualified list of supported SSDs.

Follow the the 'SSD Support List' link on the page to check your SSD.
http://www.gigabyte.com/products/product-page.aspx?pid=5284&dl=1#

[Curvin]

I am still currently trying to pinpoint the exact cause but I can inform those reading in that it has nothing to do with model/vendor of SSD.

I have also tested Intel 520 / Samsung 840 Pro, both on the compatibility list , with the same deployed Windows 7 SP1 Pro image and each SSD prior to imagining would enter BIOS fine , but as soon as it is imaged will display the same issue.

Reverting back to a base image and the issue is not present.

In short , an installation or configuration on Windows has somehow tripped this issue, which I need to clarify so that it does not happen on future installs. I am a specialist system builder, this is not a one off build, so I need to have the issue clarified and resolved before I can deploy systems to clients.

V.C

[wrangler]

I haven't  been able to try it yet but someone told me that a workaround is using F12, like your going to select a boot device and then selecting to enter setup as opposed to hitting the Del key to enter bios.