Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => X99 Motherboards => Topic started by: computermensch on September 11, 2014, 07:44:03 am
-
The boot strap seems ureliable ... both F5 and F8b firmware .. both legacy boot and EFI / Windows Boot Manager.
Solution:
Please fix the error ...?
Problem:
Every now and then ... like in 1 out of 10 reboots ... the system (the board) will hang at the Gigabyte splash screen. Especially after Windows Updates. A push on the reset switch triggering a reboot ... may fix this.
BTW
For EFI: Set CSM, do not enable Secure Boot (if you have a Nividia or an AMD gfx ext card), do not enable legacy boot but set EFI Network stack and set UEFI network boot if you use a deployment service. If i.e. WDS on the same subnet - do not use IP-Helpers, but let PXE points to X64 boot image. Clean the disk using diskpart. Now Windows will part the system disk for the OS according to EFI (3 partitions).´Down load hot fix from MS for Win8.1. to remove the watermark stating Secure Boot was incorrectly setup (because Secure Boot basically not supported by many Nividia or AMD gfx cards). Remember, EFI is not something you "enable". It's a spec. working across the system. Most are after the EFI boot explained here.
-
It's already BIOS F9a.....please try......
-
Wau --- 1 day ... yeah, that may be it. I am actually using 2800 MHz 4x4GB DDR4.
... and thanks. I have just updated to F8b yesterday - apparently just before this one came out. ... the same day :)
-
Nope, that did not do it. Not the fix for this problem. Still hanging ocasionally ... after f9a ... had to reboot a few times again to make it through to Windows 8. Initially - straight after the QFlash update to F9a, the system would just behave strange and go "lights out" (power off) a few times.
Had to do F12 and select the Windows Boot Manager (EFI) to load the system. It's not pickiing the Windows Boot Manager ... especially after these system updates alike updating the firmware, doing a Windows update etc. Have to do it by F12?
The SSD with the Windows Boot Manager is attach to a SATA Express port. Will try and move it later on to a SATA port.
But definitely is a issue with referecing or loading the Windows Boot Manager on EFI it seems.
-
I'm running F5 bios and I'm not having any problem. But I'm not running windows 8 too.
Again here we are and the people that are starting to have problems are again the ones running windows 8.
I'm a Microsoft partner I will not run it. Yes I have it on one my computers. It is still at the testing level with me.
Till they really fix it. I will stick with windows 7. At this time I feel this board is the best one I have ever build in the i7 family.
GA-X99-UD4 - i7-5820K 3.30GHz - G.Skill 16gb DDR4 2133
-
It seems to be when the UEFI:NIC is registered somewhere in the boot sequence (and with a lower precendece than the disk ... i.e. coming after the ssd with the system part) that the boot sequence may hang (block).
So as a temporary solution - after you have used UEFI:NIC PXE IP4 / UEFI:NIC PXE IP6 + SSDD (Windows Boot Manager) in the boot sequence to i.e. deploy the os from a network service ...
... then remove UEFI:NIC IP4 + UEFI:NIC IP6 from the boot sequence in the BIOS.
That seems to fix it.
BTW Still needs to be fixed in the firmware ...
-
BTW Still needs to be fixed in the firmware ...
Yes they need to fix but for windows 8. They are trying really hard to fix that too. But what I see is they make one step forward and than two or three steps back.
Just hold on they have a new OS coming maybe by the end of this year or early next year. To replace windows 8 & 8.1 So you can throw that in to the mix as well.
-
Just to completely close this thread - in my case it was the unrealiable boot too that has just been corrected with a BIOS update (referred to in other posts in this forum as the boot loop). BTW I also had the HOTAS Warthog connected to the system.