If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
F5 BIOS 100% stable also but with F6 BIOS and Auto or Gen3 selected I get constant driver crashes/black screen (the system log is full of nvlddmkm related errors). Setting Gen2 instead of Gen3 makes everything stable again.
Just info.......
by Sin0822:
an update i just got, the issue with the nvidia driver issues and the newer BIOSes has been resolved, maybe even those BIOSes up there are the fix, if not then early next week.
thanks for the tip, but i don't intend on troubleshooting any further to see if the problem still persists in the F2k beta BIOS . the machine that had the problem happens to be a full-time (24/7) distributed computing machine (as opposed to a general purpose home PC), so getting it back up and running again was of the utmost importance. besides, the more times i'm required to flash a BIOS, the more things can potentially go wrong during the flash process. at any rate, i was just putting it out there just in case anyone else wants to do any further testing themselves, whether it be a tester, a developer, or a volunteer.
3- I am sure you went thru that but just to be sure ... reset CMOS (after flashing)...load "optimised settings'...save/exit...re enable igfx (like you did ..not "auto") and your other manual settings.
Plug your monitor on the igfx....shutdown..then monitor back to discreet with igfx still "enable"...force a "scan for hardware change" in Dev manager if it still don't show with your monitor on discreet.
I think you loose nothing at trying I guess
Hope it works !
No atm, as Ivy-E is not released yet (1 more month).
Virtualfred found a microcode for CPUID 206E4 in two BIOSses, and I found that too in an ASUS BIOS myself. Gigabyte BIOSses have a microcode for 206E2. Assuming that the step from 6Dx to 6Ex represents a change in architecture, it may be safe to assume the 6Ex microcodes are for Ivy Bridge. It would mean that maybe engineering samples are supported, but the 6E4 release-CPUs aren't.
However I am unable to verify that the CPUIDs mentioned are really for IBE. We could add support right away but at this point it seems useless
Virtualfred found a microcode for CPUID 206E4 in two BIOSses, and I found that too in an ASUS BIOS myself. Gigabyte BIOSses have a microcode for 206E2. Assuming that the step from 6Dx to 6Ex represents a change in architecture, it may be safe to assume the 6Ex microcodes are for Ivy Bridge. It would mean that maybe engineering samples are supported, but the 6E4 release-CPUs aren't.
However I am unable to verify that the CPUIDs mentioned are really for IBE. We could add support right away but at this point it seems useless
I just flashed 7a on my Z87X-UD5H and I think it's killed it!
The board posts but just sits at the initial bios screen with A2 on the post display but won't enter the bios or respond to any key presses. I've tried booting from the backup BIOS and that's doing the same. Have disconnected all the drives, using a single stick of ram and still exactly the same.
Any suggestions or am I in RMA land?
---------------------------------------------------------------------------------------------------------------------------------------------- Gigabyte Z87X-UD5H BIOS v F6L
16GB GeIL Dragon RAM PC3-12800C11 1600MHz Dual Channel (2x8GB)
Intel Core i7 4770k @ 4.7ghz
2 x EVGA 770GTX SC SLI
2 x Samsung 840 Pro 120GB SSD (RAID0) 2 x Hitachi 2TB HDD - (RAID1)
XFX Pro Series 850w PSU
Corsair Obsidian 900D
Cooled with a custom 360 rad and EK Supremacy CSQ Clean block with 6 x Corsair SP120 Quiet fans.
-------------------------------------------------------------------------------------------------------------------
Well ok this board seems to be determined to give me a heart attack and make me question all sense of logic.
So I found that if I physically unplugged all of the SATA ports I could boot into the BIOS (on 7a). Once in there I set the RAID controller to RAID and rebooted. Then when I rebooted, reconnected all the drives, boom back to normal.
Really have no idea why it was doing that but hey ho i'm back up and running.
---------------------------------------------------------------------------------------------------------------------------------------------- Gigabyte Z87X-UD5H BIOS v F6L
16GB GeIL Dragon RAM PC3-12800C11 1600MHz Dual Channel (2x8GB)
Intel Core i7 4770k @ 4.7ghz
2 x EVGA 770GTX SC SLI
2 x Samsung 840 Pro 120GB SSD (RAID0) 2 x Hitachi 2TB HDD - (RAID1)
XFX Pro Series 850w PSU
Corsair Obsidian 900D
Cooled with a custom 360 rad and EK Supremacy CSQ Clean block with 6 x Corsair SP120 Quiet fans.
-------------------------------------------------------------------------------------------------------------------
Stasio, you really are a champ! You are the one in the front line taking all the crap because Gigabyte isn't standing up to the plate. There are beta BIOS galore on this site. I wrote an all out rant to Gigabyte telling them that they dropped the ball all the way on their Z77 X79 boards with below average functional BIOS. But you, you mod BIOS all over the place and you seem to do a pretty good job of it.
If you don't work for Gigabyte than they should hire you.
If you enable support for external SATA in SATA config, the transition from BIOS to OS goes from seconds to about a minute. Then it takes Windows about 2-3 minutes to load. The problem went away when I disabled the external SATA support again.
I filed a bug with Gigabyte technical support.
CPU: i7 4770k at 4.3GHz Vcore=1.19v Vccin=1.8v Uncore=4GHz Vrin=1.09v
MB: Gigabyte GA-Z87X-UD4H (Rev 1) F9
Heatsink: Prolimatech Armageddon with 2 NF-A14's, Gelid GC Extreme TIM
RAM: 2x4GB Crucial Ballistix DDR3-1600 @1600MHz Vdimm @1.5v (auto) 9-9-9-24
SSD: Samsung 840 Pro 512GB; HD's: WD Black 4TB, WD Red 3TB
PSU: Seasonic X-750; CM N600 case Trophy Run: 5GHz
Could this be related to F7a for Z87X-UD3H? I reported this in OCnet too.
-------------------------------------------------------------------------------------
Tried searching but I couldn't find clear descriptions on the 3 different Marvell drivers from GB's Z87X-UD3H drivers site:
Marvell Storage Utility (4.1.0.2013), Marvell SATA Controller Driver (1.0.0.1061), and Marvell Preinstall Driver (1.2.0.1035)
I've only installed Marvell SATA Controller, and also the later Marvell mv91xx v1.2.0.1035.
With this, I'm trying to use my eSATA ports at the back panel but every time I attach the eSATA cable, everything seems to drag & slow down (i.e. mouse barely moves). It immediately goes back to normal as soon as I detach the cable. In the BIOS (FW 7a), I have Marvell SATA forced to eSATA and in AHCI mode for GSATA Controller. Though I already tried AUTO, nothing changed.
-------------------------------------------------------------------------------------
Well ok this board seems to be determined to give me a heart attack and make me question all sense of logic.
So I found that if I physically unplugged all of the SATA ports I could boot into the BIOS (on 7a). Once in there I set the RAID controller to RAID and rebooted. Then when I rebooted, reconnected all the drives, boom back to normal.
Really have no idea why it was doing that but hey ho i'm back up and running.
I have the same problem, my 20 sec Windows boot went to 2/3 minutes.
Meanwhile replaced f7a by F6 Original but boot time still effected, when I start with the ssd only boot time okay but
when I connect my 2 wd hd bootime increases quite a bit.
By disabling esata support got my boot time back to 20 sec.
an update i just got, the issue with the nvidia driver issues and the newer BIOSes has been resolved, maybe even those BIOSes up there are the fix, if not then early next week.
Is that fix also coming for the Z87X-OC which is facing the same since F5?
Comment