Re: GIGABYTE Latest Beta BIOS
Did they mention why they wanted F12i pulled?
None the less, last night I ran into a couple bugs with that version so I've rolled back to F12h.
The first bug was semi-serious, with the motherboard getting stuck in a Boot Failure Detected loop after making some adjustments to BCLK, voltages, and RAM multiplier. Even Load Optimal Defaults was producing Boot Failure Detected. Luckily, reflashing the bios fixed the issue. I have to admit that it bothers me that the Z77 UD3H seems to either store configuration data or gets corrupt in such a way which is impossible to get rid of short of a reflash.
On my old UD3H, I remember F12g having a similar issue related to Turbo. It got stuck in an endless 2-3 second reboot loop, and after clearing the CMOS it instead completely hung after POST which made it impossible to enter the BIOS. The F7 Backup Bios booted fine, and after a bit of fiddling I figured out a way to use QFlash to reflash any BIOS on my USB Flash to my Main BIOS while within the Backup BIOS. The reflash brought it back to normal, but I ultimately RMA'ed it because the Atheros NIC completely died a few days after that, and have been using my second UD3H for the past week.
The second was the Atheros NIC all of a sudden became unresponsive refusing to load any webpages, and my attempt to disable it semi-hung Windows 7 leaving me to forcibly shut-down. That could very well have been a driver bug in 2.0.15.16, since it resolved itself after rebooting. None the less a little bit concerning since this is my second UD3H, while NIC failure was the reason I RMA'ed my first UD3H.
I just hope Gigabyte is also working hard at fixing these unrecoverable BIOS corruption issues before they release the next stable. I'm stuck on these betas, since they are the only ones which have proper OPROM support for my RAID card and HBA.
Originally posted by stasio
View Post
None the less, last night I ran into a couple bugs with that version so I've rolled back to F12h.
The first bug was semi-serious, with the motherboard getting stuck in a Boot Failure Detected loop after making some adjustments to BCLK, voltages, and RAM multiplier. Even Load Optimal Defaults was producing Boot Failure Detected. Luckily, reflashing the bios fixed the issue. I have to admit that it bothers me that the Z77 UD3H seems to either store configuration data or gets corrupt in such a way which is impossible to get rid of short of a reflash.
On my old UD3H, I remember F12g having a similar issue related to Turbo. It got stuck in an endless 2-3 second reboot loop, and after clearing the CMOS it instead completely hung after POST which made it impossible to enter the BIOS. The F7 Backup Bios booted fine, and after a bit of fiddling I figured out a way to use QFlash to reflash any BIOS on my USB Flash to my Main BIOS while within the Backup BIOS. The reflash brought it back to normal, but I ultimately RMA'ed it because the Atheros NIC completely died a few days after that, and have been using my second UD3H for the past week.
The second was the Atheros NIC all of a sudden became unresponsive refusing to load any webpages, and my attempt to disable it semi-hung Windows 7 leaving me to forcibly shut-down. That could very well have been a driver bug in 2.0.15.16, since it resolved itself after rebooting. None the less a little bit concerning since this is my second UD3H, while NIC failure was the reason I RMA'ed my first UD3H.
I just hope Gigabyte is also working hard at fixing these unrecoverable BIOS corruption issues before they release the next stable. I'm stuck on these betas, since they are the only ones which have proper OPROM support for my RAID card and HBA.
Comment