QFlash Bios updating utility out of date Gigabyte X79UD3 windows 7 bios ver F10

[WayMoreTaxPlz]

I have a Gigabyte X79 UD3 (rev.1.0) motherboard and would like to update my bios in order to install a new graphics card. My bios version is F10 3/5/2012 and I think the newest one is F20. I found the download for the F16 and F20 bios files and have tried updating using QFlash but none of them work. The message I get (whether I've loaded all three extracted files or just the .f20 file by itself onto a fat usb) is 'bios updating utility is out of date.' I'm guessing the updating utility is QFlash, and not the version of bios I'm trying to use. I've read on some other forums that some people use @Bios to flash their bios. I have gone through the Gigabyte support page and found a link to an @Bios download but it seems like i've only downloaded the install wizard shield. I don't know where to find this program to run it. I haven't found any like to updating QFlash and I don't know of any more recent bios versions. This computer is running windows 7 64 bit and has and intel i7 3850. How do I update my bios?

Here is the link to the Gigabyte page with the directions they give for flashing bios: http://www.gigabyte.us/FileUpload/US/WebPage/20/HowToReflashBIOS.html

 

[Paul NZ]

You'll have to contact gigabyte for an updated one

 

[WayMoreTaxPlz]

Waiting on Gigabyte to respond to my ticket. I'll post what they tell me.

 

[Crossvxm]

http://www.tomshardware.com/answers/id-2314400/latest-bios-update-reading-outdated-gigabyte-x79-ud3.html

^

On a second note, I've read that sometimes it's best to update via @BIOS then Q-Flash. You need the latest @BIOS and the other thing that @BIOS requires. My motherboard (Gigabyte F2A68HM-M Rev 1.1) did not accept my AMD A10-7860K when I flashed the latest FC BIOS via @BIOS. It DID update as my BIOS now showed "FC" but did NOT want to boot with it no matter how many times I cleared the CMOS, etc. Using my main build, I downloaded the BIOS file, tossed it on a USB and used Q-Flash and it worked. My point is, try updating using @BIOS to at least F16 maybe?