Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with AMD processors => Topic started by: regit on January 05, 2016, 04:02:05 pm
-
Hi
I made new bios to Gigabyte 990fxa-ud3 rev4.0
i don test because dont have motherboard ,but should work fine.
You can t kill motherboard because dual bios back backup bios if something get wrong.
It f4a witch some changes :
OROM AMD RAID MISC 4392 - 3.2.1540.6 uppdated to 3.3.1540.19)
OROM AMD RAID MISC 4393 - 3.3.1540.17 updated to 3.3.1540.19)
EFI AMD RAID - 1.0.0.45 updated to 1.0.0.49)
EFI AMD Utility - 1.0.0.45 updated to 1.0.0.49)
OROM Realtek Boot Agent - 2.60 updated to 2.64)
EFI Realtek UNDI - 2.027 updated to 2.035)
EFI Broadcom UNDI - 14.0.6 updated to 17.0.5)
OROM Broadcom Boot Agent (new rom 16.8.0)
I wil add vishera fix in next version, and update amd agesa .
(http://i68.tinypic.com/2z7fzwn.png)
https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg (https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg)
-
I wil add vishera fix in next version, and update amd agesa .
I would be interested in how you do this as I believe the ucode micro patches are compiled in source in inside
the EFI AMD AGESA OrochiPI I could not find tables in bios.
see my post here on the ver 3.0:
http://forum.giga-byte.co.uk/index.php?topic=16626.0
-
Hey!
Your Custom-Bios does work pretty good!
Is there planed a Update ? ;D
-
Yep, flashed it as well and all good so far!
-
Hey!
Your Custom-Bios does work pretty good!
Is there planed a Update ? ;D
Update v2
-updated EFI Broadcom UNDI to 17.2.1
-update OROM Broadcom Boot Agent 17.2.0
-PatchID_0x06000832_23.07.2014
CPUID 0x00600F20; Patch 0x06000832; Errata #691, #699, #704, #708, #709, #734, #740, #778; as per AMD documentation .
(microcode patch resolve a potential system stability issue affecting AMD Opteron 6300 series and AMD FX series ,Phenom II X6 processors running VMware)
https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg
IF sombody flash with fx cpu make me screnshoot from regedit
HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0]
to see fix works
-
Hey!
Your Custom-Bios does work pretty good!
Is there planed a Update ? ;D
Update v2
-updated EFI Broadcom UNDI to 17.2.1
-update OROM Broadcom Boot Agent 17.2.0
-PatchID_0x06000832_23.07.2014
CPUID 0x00600F20; Patch 0x06000832; Errata #691, #699, #704, #708, #709, #734, #740, #778; as per AMD documentation .
(microcode patch resolve a potential system stability issue affecting AMD Opteron 6300 series and AMD FX series ,Phenom II X6 processors running VMware)
https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg
IF sombody flash with fx cpu make me screnshoot from regedit
HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0]
to see fix works
Not sure if I am missing anything, but my attempt to flash a 990fxa-ud3 V4.0 mothrboard with Qflash results in an invalid image warning.
Robert
-
I'll add that I did have the previous modded version, but hadn't tried it. I just updated using it - so far it seems to work OK. So I imagine there is some issue with the second version.
Thanks
Robert
-
I'll add that I did have the previous modded version, but hadn't tried it. I just updated using it - so far it seems to work OK. So I imagine there is some issue with the second version.
Thanks
Robert
Try now, i upload probably fixed version
-
I'll add that I did have the previous modded version, but hadn't tried it. I just updated using it - so far it seems to work OK. So I imagine there is some issue with the second version.
Thanks
Robert
Try now, i upload probably fixed version
That version seems to work.
Thanks very much
Robert
-
Okay, flashed v2 and the CPU screenshot is here:
http://pasteboard.co/2laqqlLA.jpg
1 thing to note is the system is booting twice after bios update ( first boot screen twice) - not sure this means old bios has been restored? The patch level reported is 822 (not 832).
However, all seems to work nicely!
-
Hey!
Your Custom-Bios does work pretty good!
Is there planed a Update ? ;D
Update v2
-updated EFI Broadcom UNDI to 17.2.1
-update OROM Broadcom Boot Agent 17.2.0
-PatchID_0x06000832_23.07.2014
CPUID 0x00600F20; Patch 0x06000832; Errata #691, #699, #704, #708, #709, #734, #740, #778; as per AMD documentation .
(microcode patch resolve a potential system stability issue affecting AMD Opteron 6300 series and AMD FX series ,Phenom II X6 processors running VMware)
https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg
IF sombody flash with fx cpu make me screnshoot from regedit
HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0]
to see fix works
Regedit shows the following entries on my machine.
Robert
[HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0]
"Component Information"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"Identifier"="AMD64 Family 21 Model 2 Stepping 0"
"Configuration Data"=hex(9):ff,ff,ff,ff,ff,ff,ff,ff,00,00,00,00,00,00,00,00
"ProcessorNameString"="AMD FX(tm)-8320 Eight-Core Processor "
"VendorIdentifier"="AuthenticAMD"
"FeatureSet"=dword:2c3b3dfe
"~MHz"=dword:00000dbc
"Update Revision"=dword:06000822
"Update Status"="Newer Patch Not Available"
"Previous Update Revision"=dword:06000822
"Platform Specific Field1"=dword:06000822
-
Here my screenshot!
-
Okay, flashed v2 and the CPU screenshot is here:
http://pasteboard.co/2laqqlLA.jpg
1 thing to note is the system is booting twice after bios update ( first boot screen twice) - not sure this means old bios has been restored? The patch level reported is 822 (not 832).
However, all seems to work nicely!
Yee i know , i will make one more update with update fully amd agesa, but all older module should be updated to see it you can enable raid mode in bios , (chose amd controller not marvell) restrat pc and go you should see version of bios it should be 3.3.1540.19 .
-
Okay, I walked the plank and enabled RAID in bios (no choice AMD or Marvell)
Next boot I ended up with a blue screen (system HALT after raid made some initial checks) ... then Win7 asked to repair the boot disk - I hate RAID hence never used it!
btw, there is no raid bios version info as far as I could see - no time to look, it was very quickly.
-
Okay, I walked the plank and enabled RAID in bios (no choice AMD or Marvell)
Next boot I ended up with a blue screen (system HALT after raid made some initial checks) ... then Win7 asked to repair the boot disk - I hate RAID hence never used it!
btw, there is no raid bios version info as far as I could see - no time to look, it was very quickly.
Press ctr f
-
.......
Press ctr f
nope :)
-
.......
Press ctr f
nope :)
Update v3
-add fx cpu fix
https://drive.google.com/file/d/0B4rC7reRUp6QVEhKNVd5TzFOWXM/view?usp=sharing
Can somebody look into registry and looks it sholud be new microcde now
-
Okay, updated to v3 and CPU CurrentPatchLevel now reports ...832 hence has been updated.
http://pasteboard.co/2C40MUwA.jpg
However, the initial double boot (after flash) persists. So far seems to work nicely :)
-
Regit:
Can you summarize what are the advantages of the bios that you have designed, especially for FX processors and Windows 10?
Thanks
-
Regit:
Can you summarize what are the advantages of the bios ...
He just updated the bios components (as outlined in his post #1) with a more recent revision of those components - hence consider it a maintenance release which should have been done by Gigabyte.
-
Regit:
Can you summarize what are the advantages of the bios ...
He just updated the bios components (as outlined in his post #1) with a more recent revision of those components - hence consider it a maintenance release which should have been done by Gigabyte.
Thanks AgentFXA.
A doubt:
The double boot (after flash) is every time you start the computer or just after flashing?
-
Regit:
Can you summarize what are the advantages of the bios ...
He just updated the bios components (as outlined in his post #1) with a more recent revision of those components - hence consider it a maintenance release which should have been done by Gigabyte.
Thanks AgentFXA.
A doubt:
The double boot (after flash) is every time you start the computer or just after flashing?
Only 1 time after flashing
-
I installed with Q-flash, but I still indicating bios F4A, is this normal?
-
I installed with Q-flash, but I still indicating bios F4A, is this normal?
Yee its normall i dont change version and date but i will do it ;D
-
flashed v3 and the CPU screenshot:
GA-990FXA-UD3 Rev 4.0 FX8350 memo 16 GB Kingston
-
......
The double boot (after flash) is every time you start the computer or just after flashing?
Only 1 time after flashing
Yep, it happens only once after the update
-
Update v4 :
change date to 2016.01.04
change version to f4x
update microcde for cpu
Date:2010/02/17 CPUID:100FA0 PatchID:010000BF -> Updated Date:2011/10/24 CPUID:100FA0 PatchID:010000DC
Date:2010/03/11 CPUID:100F41 PatchID:010000C6 -> Updated Date:2011/10/24 CPUID:100F41 PatchID:010000DB
This Microcode update will fix Errata #438, #440 and #573 as per AMD documentation in Newer" AM3 CPUs having CPUID 100FA0 Phenom II X6 CPUs, CPUID 100F41 Opteron
Link in first post
-
Update v4 :
change date to 2016.01.04
change version to f4x
update microcde for cpu
Date:2010/02/17 CPUID:100FA0 PatchID:010000BF -> Updated Date:2011/10/24 CPUID:100FA0 PatchID:010000DC
Date:2010/03/11 CPUID:100F41 PatchID:010000C6 -> Updated Date:2011/10/24 CPUID:100F41 PatchID:010000DB
This Microcode update will fix Errata #438, #440 and #573 as per AMD documentation in Newer" AM3 CPUs having CPUID 100FA0 Phenom II X6 CPUs, CPUID 100F41 Opteron
Link in first post
The name and date of Bios change in windows.
In UEFI Bios continues F4a and the same earlier date.
In regedit, I do not notice changes
Is there way to update AGESA?
In "UEFI bios updater" it is not possible
-
Update v4 :
change date to 2016.01.04
change version to f4x
update microcde for cpu
Date:2010/02/17 CPUID:100FA0 PatchID:010000BF -> Updated Date:2011/10/24 CPUID:100FA0 PatchID:010000DC
Date:2010/03/11 CPUID:100F41 PatchID:010000C6 -> Updated Date:2011/10/24 CPUID:100F41 PatchID:010000DB
This Microcode update will fix Errata #438, #440 and #573 as per AMD documentation in Newer" AM3 CPUs having CPUID 100FA0 Phenom II X6 CPUs, CPUID 100F41 Opteron
Link in first post
The name and date of Bios change in windows.
In UEFI Bios continues F4a and the same earlier date.
In regedit, I do not notice changes
Is there way to update AGESA?
In "UEFI bios updater" it is not possible
Data and version it probably probaly in 2 modules(so need one more change in hex file to be in bios see)
You have latest microcde for fix fx i update this in v3 and v4 have this too but now i update for other cpu as phenom x6 and opteron so you cant see change in regedit because you dont have phenom x6 or opteron.
Latest agesa is 1.5.0.6 you have 1.5.0.5 is imposiple us Uefi updater is need change hex value the same as microcode cpu, IN AMI Bios update Agesa is very hard , i update succesfull agesa to 1.5.0.6 in my ga990xa ud3 rev1.0, because i have this motherboard and i can look how it works. If find some more time i will try update this in your motherboard.
-
Update v4 :
change date to 2016.01.04
change version to f4x
update microcde for cpu
Date:2010/02/17 CPUID:100FA0 PatchID:010000BF -> Updated Date:2011/10/24 CPUID:100FA0 PatchID:010000DC
Date:2010/03/11 CPUID:100F41 PatchID:010000C6 -> Updated Date:2011/10/24 CPUID:100F41 PatchID:010000DB
This Microcode update will fix Errata #438, #440 and #573 as per AMD documentation in Newer" AM3 CPUs having CPUID 100FA0 Phenom II X6 CPUs, CPUID 100F41 Opteron
Link in first post
The name and date of Bios change in windows.
In UEFI Bios continues F4a and the same earlier date.
In regedit, I do not notice changes
Is there way to update AGESA?
In "UEFI bios updater" it is not possible
Data and version it probably probaly in 2 modules(so need one more change in hex file to be in bios see)
You have latest microcde for fix fx i update this in v3 and v4 have this too but now i update for other cpu as phenom x6 and opteron so you cant see change in regedit because you dont have phenom x6 or opteron.
Latest agesa is 1.5.0.6 you have 1.5.0.5 is imposiple us Uefi updater is need change hex value the same as microcode cpu, IN AMI Bios update Agesa is very hard , i update succesfull agesa to 1.5.0.6 in my ga990xa ud3 rev1.0, because i have this motherboard and i can look how it works. If find some more time i will try update this in your motherboard.
Thank you for your effort
see:
http://www.theregister.co.uk/2016/03/06/amd_microcode_6000836_fix/
-
Update v5
Fix data and version for bios bulid
Update microcode for fx and opteron cpu
Date:2014/07/23 CPUID:00600F20 PatchID:06000832 -> Updated Date:2016/01/25 CPUID:00600F20 PatchID:0600084F
Link in first post
-
Hi:
The name and date of Bios change in windows.
In UEFI Bios continues F4a and the same earlier date.
PD: BIos extractor tool,
Have you link for download?
-
can you make photo or something where is old date because i dont have uefi bios. :'(
-
yes
-
Okay, bit clearer here is the old date in v5:
http://pasteboard.co/2OopzqPF.jpg
-
I have noticed that the bios has the new patch ( 0x0600084f) (F4X) decreases processor performance (FX8350) with respect to F4a.(0x6000822)
In approximately 1%.
I have done several tests and always gives me the same.
-
You will never have the same resulatat , i do this test few time and look 100 points is not a diffrent
(http://i64.tinypic.com/xc101y.png)
bechmark alway gives other values because system all time work and do something heavy or light
-
Sorry
I mean ALWAYS it gives me higher in the F4a
Anyway, that's not your fault, but the patch
May be it sacrificing performance for stability.
-
Hello all, Been following this thread and using this BIOS since v1 and finally decided to register.
First off thanks for continuing work on this board where gigabyte has left off. This BIOS is definitely an improvement over the official releases.
I have noticed a few quirks though, perhaps others have noticed as well. I use this board with an AMD 8350 8 core and 8G of 1333 DDR3 and a gigabyte R9 270x.
My first issue is I have never been able to manually set northbridge or HT speeds. On occasion I can set 2400 on the northbridge but regardless of voltages or LLC settings etc it is not stable.....also the multipliers seem to be locked to 13x and 11x respectively, perhaps this part is normal for this board. Anyways, oddly enough if I raise the base clock the raised NB and HT clocks are stable. I can set 225mhz and the machine will run 2900+ on the HT and 2600+ on the NB. Temps get a little out of hand at load but my point is the board will do it. Why cant I manually set any speed for these values with success? I am currently running 215mhz which yields 2800 HT 2400 NB stable and runs reasonably cool. My previous board: Asus M5A97 r2.0 could easily run 2600 \ 2600 and could even go beyond with a little effort. I believe the 990FXA to be superior to the M5A97 so I don't understand the wall I'm hitting currently.
My second issue is with HPC setting in BIOS. If I boot the computer and allow it to boot windows without interruption I hold any core speed constantly as is supposed to occur. However, if I enter BIOS -To monitor temps or voltages etc- and then boot to windows from within BIOS HPC is over ridden and the CPU speed fluctuates mostly below half speed, occasionally hitting 3.8 - 4.1 GHz but never close to to my set 4.51. It is also much more "crashy" in windows. Is there any reason why I'm stable and rock solid if I simply let the computer start uninterrupted and unstable if I boot windows from within BIOS?
Thanks again for your continued work and Thanks to anyone who can shed some light on this
Zyro
-
The underlying bios for the patching here is the unofficial version F4a - a hotfix (for the cpu fan issue) and not meant to be overclocked. There are no OC safeguards in place in this bios version hence you're on your own risk. This might explain some of your quirks.
Personally I think the v4.0 board is Gigabyte's worst release I came across - there was a reason a v4.1 board has been rushed out and is now replaced with v5.0
-
I advise you to write to:
technical support in taiwan and insist with the publication of a new Bios
I just did it
http://esupport.gigabyte.com/Login/Index?ReturnUrl=%2f
"Question: Do you have plan to upgrade the bios ?, since F3 has serious problems with the speed cpu cooler and F4a not been published.
In addition there is a new AGESA code.
And to suit Windows 10"
-
The underlying bios for the patching here is the unofficial version F4a - a hotfix (for the cpu fan issue) and not meant to be overclocked. There are no OC safeguards in place in this bios version hence you're on your own risk. This might explain some of your quirks.
Personally I think the v4.0 board is Gigabyte's worst release I came across - there was a reason a v4.1 board has been rushed out and is now replaced with v5.0
Thanks for the replies and opening a dialogue with me on this,
Yes I realize this is an unofficial bios and I'm using it as unintended, but I do feel it is the best performing bios I have tested thus far on this board which when acquired had ver F2. As for the safeguards....I do believe some if not all are functioning. If I set 2600 on the HT and quite often when I set 2400 the machine will hang for a moment...the LEDs in my case will dim then brighten and the machine boots to stock setting and gives a warning of the previous settings failure. The machine also throttles or outright shuts down if I exceed 75C for more then about 5 seconds on either the NB or CPU (both temps are usually within ~ 5 degrees of one another). So something is saving me I have to think.
I come from Intel land lol My previous C2D quad 9550 2.8 Could hit 5.0 at 1.65V on the core. Way in excess of standard settings but she took it....I rarely set that speed outside of hypothetical testing scenarios and usually ran at 4.6 @ 1.55V or so....it held up for 6+ years before the motherboard gave out, an MSI x48C platinum. The 9550 survived. AMD is a completely different animal of course, my last exposure to AMD was a K6-2 333 and I've never owned one again until now.
I've, of course, had to re evaluate my previous OC techniques. I don't feel that this is a bad board....or maybe I somehow got a blessed one? lol Its hands down superior to the ASUS M5A97 R2.0 I had first and replaced after less than a month. I just don't think it had the VRM capacity to drive this chip -FX8350- or sufficient cooling to push it. My original query still remains tho....why cant I ever adjust the HT or NB speeds? Regardless of official BIOS or otherwise? Even if I set the exact values that "Auto" determines or one step up or one step down it fails. Why MUST they be left to auto? Why is there no multiplier flexibility here? This is the only feature the M5A97 had over this board and I wish this wasn't the case since I am certain that the machine performed better when the HT and NB frequencies where in line with each other.....example 2600\2600 etc
My observation about core speed being variable if I boot override thru bios vs just letting the system start normally and holding stable with HPC set was not commented upon.....can anyone else confirm this? Try booting as I have mentioned....once normally, uninterrupted and once thru bios both times with HPC set. Do you see the same thing I do? Is HPC overridden if u manually boot your windows drive from bios? I'm only guessing HPC is overridden here....I haven't investigated much past the root cause...my interest was centered on holding core speed and once I saw that allowing the machine to boot uninterrupted held core speed I dug no further and continued to push my clocks.
Thanks for the comments thus far and looking forward to more in the future,
Zyro
-
I advise you to write to:
technical support in taiwan and insist with the publication of a new Bios
I just did it
http://esupport.gigabyte.com/Login/Index?ReturnUrl=%2f
"Question: Do you have plan to upgrade the bios ?, since F3 has serious problems with the speed cpu cooler and F4a not been published.
In addition there is a new AGESA code.
And to suit Windows 10"
Good Morning, well morning for me anyways :)
After batting this post around in my head throughout the night I have the feeling that there likely wont be a new release, at least not specifically to suit windows 10. The board is 8.1 certified and there is little diff between 8.1 and 10, please educate me if I'm wrong here but the slope of OS development was sharper from win 7 to 8 than it was from 8 to 9....er 10 -still hate they skipped 9 to distance themselves from 8....so stupid- So in that light why re invent the wheel so to speak when there is little diff between the 2 under the hood? Virtually anything that works in win 7 will work unhindered in win10 and even more so the case when using windows 8 designed software on windows 10....no probs, no performance hits nothing. So why, outside of marketing gimmicks, would you need to stamp win10 on this board when nothing has really changed from the motherboards perspective? Also, and perhaps most damaging, as you say, 4.1 and subsequently R5 were rolled out fairly quickly. R5 being fairly recent too for a ~ 4 year old chipset which some speculate is a dead end. I digress....my point was with age not on this variants side, 2 "redo's" of the same model ahead of this one and the A series socket getting all the attention -FM2 is it?-..... can we really expect much, if any development on this platform, officially anyways? The 9000 series 8 cores were meant to breath life back into this platform but from what Ive read fell far short of this goal..... 225W TDP being just too much for anything but the elite boards and even they -MSI 990 gaming, sabertooth 2.0 etc- have trouble wielding that chip. Just seems like too many nails in the coffin.
My view, which I may be alone in, is this is a very capable board and CAN bring out the best from the FX processor, mine anyways, you just have to be patient and willing to work at it, which I understand is not everyone's cup of tea. However, I have noticed that most people who come across Modded BIOS threads and the like are slightly more computer savvy than the average joe and don't mind tinkering under the hood. That said my current config, as far as the most recent AIDA64 extreme is concerned, can keep pace with a 4th Gen i7, and outrun the other FX8000 CPUs easily which isn't too shabby I don't think. By no means am I done yet tho lol :D
I do agree with you tho Jorge, Id love to see more official work done on the 4.0 but I just don't see it in the cards. On this I do hope I'm mistaken.
Thank you for initiating this thought exercise and I look forward to your counterpoints
Zyro
-
...........Why MUST they be left to auto? .....
Zyro
You can just use the + key to change the desired value once hi-lighted
other than that I am not into OC hence no skills here ;)
-
...........Why MUST they be left to auto? .....
Zyro
You can just use the + key to change the desired value once hi-lighted
other than that I am not into OC hence no skills here ;)
Yes I understand that I can adjust frequencies ie 2200 2400 2600..... but I cannot manipulate multipliers unless I'm seriously missing something.....the multipliers seem to be locked at 13x on the HT and 11X on the NB with no adjustment possible. also setting any value other than auto on either of these fields results in instability.... I have no choice but to set Auto here....which baffles me. Id like to hear input from the BIOS modder on this as they have dissected this BIOS and recompiled it. Of course any input is welcomed :D
Possibly there is a language barrier here? Perhaps I could assist with that if I'm not coming across clearly? I do use a lot of slang and shorthand which can be difficult
Zyro
Thanks for your reply, Id be happy to share data and screenshots on my results if needed
-
BIOS custom 990fxa ud3 4.0 v6
Change:EFI Realtek UNDI 2.036
(Previus of regit 990FXA-UD3 4.0 v5)
https://drive.google.com/folderview?id=0B1PruOcm5ygMaTdYVVdYeVBRUms&usp=drive_web
-
Thanks Jorge,
works fine and looks like this is becoming sort of a new sport - EFI bios updating!?
-
Hello again,
I was beginning to think this thread was dead.
Can anyone confirm my previous observations? Is anyone able to adjust their NB \ HT separately? I have to leave it set to auto as I have said or it fails almost 100% of the time. The only way I can raise HT and NB clocks is to overclock the FSB. Can anyone confirm this?
Thanks for the update to the bios, every little bit counts. EFI is wasted on me though, in my opinion it offers no home user benefits over legacy. Secure Boot to me is like eXecute Disable Bit 2.0 or "Boot Time Virus Protection" 3.0 lol. Please correct me if I am wrong, but in speaking with our regional I.T. at work that's what we came up with, essentially useless with no performance gains over legacy. I welcome input on this as well as I have avoided implementing EFI over legacy because of this view I have.
Zyro
-
... Is anyone able to adjust their NB \ HT separately? I have to leave it set to auto as I have said or it fails almost 100% of the time. .........
Yes, you can adjust both separately but anything beyond 2200/2600 (default) will not boot or freeze while booting - maybe voltage adjustment needed? However, as mentioned before, I am not into that.
EFI advantages are support for bigger HDD storage (2+ TB) and more partitions (4+ partitions per drive) including fault management. I am using UEFI boot since quite a while and it works nicely and is better responsive overall. The only setback is that most diagnostic tools fail on UEFI devices - like partition resizing etc. Windows7 Disk Management is limited too on EFI devices. Other than this all is working fine.
-
Is it possible to edit a multiplier higher than 10x on RAM speed ?
got 2400mhz Rams but cant get higher than 10x... so i have to speed up the Bus (220mhz) .. but not everything likes the 220mhz :'( so I have to set up the voltages a bit high...
http://valid.x86.fr/t6iauf
-
Wa?
....your 95xx CPU supports up to 2133 ram speed hence sounds about right!
http://support.amd.com/en-us/search/faq/295
-
exactly officially it only runs at 2133 mhz, my run at about 2300MHz and I want more .. would be good if I can fix it on the Multi instead of the Base Clock :'(
-
I would think it's locked there for a reason.
The 9xxx series CPUs are hot beasts and not good at oc'ing at all ... it's an 8350 oc'ed to the max.
-
i had the 8320E before .. at same speed and same voltage (yeah strange world^^) is the FX9590 colder ???
i dont know why but thats good for me :D
and my Corshair H80i is doing a good job, i just hit few times more than 70°c with the CPU (Stresstest like Prime95 and few testings on fan-settings)
But it still would be nice if someone can unlock the multiplier :)
-
Could this work on a 990FXA-ud3 non rev4?
-
Could this work on a 990FXA-ud3 non rev4?
It is only for rev 4.0.
What is your motherboard?
-
Hi
I made new bios to Gigabyte 990fxa-ud3 rev4.0
i don test because dont have motherboard ,but should work fine.
thank you.
a month ago my pc started to crash under load and few times I had to use start clean thingy in WX, well i tryed to update drivers back and forward and then the bios, now lucky for me how flashing bios today is plug and play,
I updated to 9FXAUD34.F3 and in the end got it working for idle things like youtube etc... but any real load it it would freeze up with in minutes.
now with 990fxa ud3 4.0 v6 with bios mostly set to auto, boster and tree hugger thingys disable, it made it thru p95 and at this time core 4,7@ 1.5v multipier 23.5
memory profile xmp does still not work and stil im only getting 667 works
but I can play game and in a quick test up to 120 fps in dying light cpu some part almost at 100% but the Tri-X R9 390X in lane 1 was running up to 79c but gigabyte r9 390x in lane 1 was rising on the fast track to 100c
but thank to you I can start to finish setting the pc up and hopefully later on I can start oc it
oh spec Gigabyte 990fxa-ud3 rev4.0/9590 2x 390x/ax1200/ 32gb dominator platinum/c drive is HyperX Predator 240GB /games on sm951 ^^
-
I hate gigicrap bios, but jorgecorazondeleon work is AWSOME.
v6 bios work perfect on my 4.0.
Thank you so much. After ZEN appear i will give this board and fx8350 to my nephew.
-
I hate gigicrap bios, but jorgecorazondeleon work is AWSOME.
v6 bios work perfect on my 4.0.
Thank you so much. After ZEN appear i will give this board and fx8350 to my nephew.
The real merit (and idea) is of REGIT
-
Hmm, I did not see a single problem with any of the bios updates here but same mobo does not mean it's same hardware overall.
-
I've just been reading all these posts, awesome!!! Is it just this motherboard version you can write BIOS for or any others..
Interesting Subject indeed, keep up the good work..
*I'd be happy to pay for an update to my BIOS :D
-
I've just been reading all these posts, awesome!!! Is it just this motherboard version you can write BIOS for or any others..
Interesting Subject indeed, keep up the good work..
*I'd be happy to pay for an update to my BIOS :D
Yee , it can be done witch all motherboard .
What is your mobo?
-
A last update planed or is still everything up to date :D ?
-
A last update planed or is still everything up to date :D ?
v7
-updated EFI Realtek UNDI to 2.036
-updated EFI Broadcom UNDI to 17.2.2
link in first post
-
A last update planed or is still everything up to date :D ?
v7
-updated EFI Realtek UNDI to 2.036
-updated EFI Broadcom UNDI to 17.2.2
link in first post
Thanks! So far it seems to work fine on my system.
Did anyone ever figure out what was going on with the F3 bios cooling fan issue on resume from standby? Gigabyte still has that bios on their web site. I suspect that the issue must only have affected certain machines.
-
thank you so much.
-
is working ok v7.
-
this bios v7 is newer from : https://drive.google.com/drive/folders/0B4rC7reRUp6QZkdwSVZaX2k4a3M
or the same with v7 from december 16?
-
update v8:
- OROM LAN Realtek OROM 2.65
- EFI LAN Realtek UNDI EFI 2.039
-
update v8:
- OROM LAN Realtek OROM 2.65
- EFI LAN Realtek UNDI EFI 2.039
Yep, all good!
working nicely on my box - thx!
-
working just fine. With this mod bios for over 1 year, no problem at all.
Cpu overclock ok, ram overclock ok, zero freezes, locks, shutdowns etc.
I really like this.
I will remain on this ud3 and my ud5 till ryzen v2 appear.
-
same here works
however my 9590 was NO silicon lottery and it give up, so I put the x6 1055T@3653MHz bus 14X 261MHz and dram 870MHz.
so later I will try to get it to 3.9MHz
-
Hello...First of all : great work with this bios moddings.
My question is....will there be any mod which supports NVME boot on that board or the mods already are able to.
:)
-
well I run os on kingston hyperx predator m.2 pcie adaptador and no problem oh and I have steam on 951 m.2 in a pcie adaptador
-
flashed version 8 - installed windows 10 on my samsung 960....tried to boot and....bios doesn't show the drive :D
seems it doesn't like booting from nvme
good thing now is that i have a newer bios version than my previous F3 :D
-
flashed version 8 - installed windows 10 on my samsung 960....tried to boot and....bios doesn't show the drive :D
seems it doesn't like booting from nvme
good thing now is that i have a newer bios version than my previous F3 :D
I can try add nvm if you want
-
that would be awesome :) thanksy
-
that would be awesome :) thanksy
try this:
https://drive.google.com/open?id=0B4rC7reRUp6QLTVZdVBNRVBCZlE
Important:
The "BOOT" section of the UEFI BIOS and the shortcut to the "Bootable Devices" will not show the NVMe SSD, although it may be bootable!
After having installed the NVMe supporting OS in UEFI mode onto the PCIe/M.2 connected SSD, you will see the new bootable system drive listed as "Windows Boot Manager"
Write if work if no i will try something other.
-
It WORKS !!!
it's so perfect. Windows 10 Installation 6 minutes 33 seconds...In BIOS i clearly can choose Windows Boot Manager on Samsung 960
Thank you sooo much !
-
It WORKS !!!
it's so perfect. Windows 10 Installation 6 minutes 33 seconds...In BIOS i clearly can choose Windows Boot Manager on Samsung 960
Thank you sooo much !
So good.
Update v9
-add NVMe support
download
https://drive.google.com/drive/folders/0B4rC7reRUp6QeDRGRHlhWk5CdXc
-
Ok i forget add this too:
update v10
- update EFI Realtek LAN UNDI v2.040
download:
https://drive.google.com/drive/folders/0B4rC7reRUp6QeDRGRHlhWk5CdXc
-
Hi
I made new bios to Gigabyte 990fxa-ud3 rev4.0
i don test because dont have motherboard ,but should work fine.
You can t kill motherboard because dual bios back backup bios if something get wrong.
It f4a witch some changes :
OROM AMD RAID MISC 4392 - 3.2.1540.6 uppdated to 3.3.1540.19)
OROM AMD RAID MISC 4393 - 3.3.1540.17 updated to 3.3.1540.19)
EFI AMD RAID - 1.0.0.45 updated to 1.0.0.49)
EFI AMD Utility - 1.0.0.45 updated to 1.0.0.49)
OROM Realtek Boot Agent - 2.60 updated to 2.64)
EFI Realtek UNDI - 2.027 updated to 2.035)
EFI Broadcom UNDI - 14.0.6 updated to 17.0.5)
OROM Broadcom Boot Agent (new rom 16.8.0)
I wil add vishera fix in next version, and update amd agesa .
(http://i68.tinypic.com/2z7fzwn.png)
https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg (https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg)
Thanks a lot!!!
-
Hi,
Thanks for all updates. Works perfectly.
Could you add an option like a fast boot / ultra fast boot for raid settings? (Also adding fast boot for windows boot settings idea is not bad) I have Kingston HyperX Fury ssd raid 0 array. Asrock Amd boards have a ultra fast boot mode setting in bios and raid setups as fast as intel but other manufacturers does not have this option in am3+ motherboards.
Thank you again.
-
Hi,
Thanks for all updates. Works perfectly.
Could you add an option like a fast boot / ultra fast boot for raid settings? (Also adding fast boot for windows boot settings idea is not bad) I have Kingston HyperX Fury ssd raid 0 array. Asrock Amd boards have a ultra fast boot mode setting in bios and raid setups as fast as intel but other manufacturers does not have this option in am3+ motherboards.
Thank you again.
Hi,
is impossible without moterboard. It will take to much time...
-
Hello,
I am on the v10 customized/modded Bios and after I wake the computer from sleep, it works fine but sometimes I get buzzing noise that PWR_FAN (where I have hooked the water cooler's pump) has zero rpm, even though pump's LED lights blue and it seem to actually work (seems like the speed sensing on PWR_FAN is not working properly). This leads to crazy high rpm on fans and showing high temperature on CPU (based on HWInfo64). After reboot, all goes back to normal. I had this occasional problem even on F4a. Does someone else also experience this? BTW, thanks for updating the BIOS which should be done by Gigabyte and they should be sending you guys boxes of chocolate for doing their job.
Thanks.
-
Hello,
I am on the v10 customized/modded Bios and after I wake the computer from sleep, it works fine but sometimes I get buzzing noise that PWR_FAN (where I have hooked the water cooler's pump) has zero rpm, even though pump's LED lights blue and it seem to actually work (seems like the speed sensing on PWR_FAN is not working properly). This leads to crazy high rpm on fans and showing high temperature on CPU (based on HWInfo64). After reboot, all goes back to normal. I had this occasional problem even on F4a. Does someone else also experience this? BTW, thanks for updating the BIOS which should be done by Gigabyte and they should be sending you guys boxes of chocolate for doing their job.
Thanks.
This has been mentioned before and is a just buggy bios the fan or temp fault causes the buzzer to sound, I seem to remember if you connect the pump to the sysfan 1 or 2 and disable the it does not have this problem.
I think it is because of bugs in the acpi implementation.
have you reset the nvram/cmos, as a mismatch in bios config can cause weird issues?
-
Hello,
I am on the v10 customized/modded Bios and after I wake the computer from sleep, it works fine but sometimes I get buzzing noise that PWR_FAN (where I have hooked the water cooler's pump) has zero rpm, even though pump's LED lights blue and it seem to actually work (seems like the speed sensing on PWR_FAN is not working properly). This leads to crazy high rpm on fans and showing high temperature on CPU (based on HWInfo64). After reboot, all goes back to normal. I had this occasional problem even on F4a. Does someone else also experience this? BTW, thanks for updating the BIOS which should be done by Gigabyte and they should be sending you guys boxes of chocolate for doing their job.
Thanks.
This has been mentioned before and is a just buggy bios the fan or temp fault causes the buzzer to sound, I seem to remember if you connect the pump to the sysfan 1 or 2 and disable the it does not have this problem.
I think it is because of bugs in the acpi implementation.
have you reset the nvram/cmos, as a mismatch in bios config can cause weird issues?
Thank you for your reply. Yes, I did reset the CMOS. And, it does not happen often. I could change it as mentioned but only SYS_FAN2 is non-speed controlled fan header (similar to PWR_FAN) and, I think, the cables to water pump and other fan now hooked on SYS_FAN2 may not be that long to enable swapping them. Also, I use the speed controlled fan headers for fans that can change the speed.
Again, thanks.
-
Bios seems ok as usual. Fantastic work.
We need to donate some beer to Regit.
-
As mentioned above you can do it yourself too
http://www.win-raid.com/t154f16-Tool-Guide-News-quot-UEFI-BIOS-Updater-quot-UBU.html
-
Hello,
I am on the v10 customized/modded Bios and after I wake the computer from sleep, it works fine but sometimes I get buzzing noise that PWR_FAN (where I have hooked the water cooler's pump) has zero rpm, even though pump's LED lights blue and it seem to actually work (seems like the speed sensing on PWR_FAN is not working properly). This leads to crazy high rpm on fans and showing high temperature on CPU (based on HWInfo64). After reboot, all goes back to normal. I had this occasional problem even on F4a. Does someone else also experience this? BTW, thanks for updating the BIOS which should be done by Gigabyte and they should be sending you guys boxes of chocolate for doing their job.
Thanks.
This has been mentioned before and is a just buggy bios the fan or temp fault causes the buzzer to sound, I seem to remember if you connect the pump to the sysfan 1 or 2 and disable the it does not have this problem.
I think it is because of bugs in the acpi implementation.
have you reset the nvram/cmos, as a mismatch in bios config can cause weird issues?
UPDATE: I did finally got extending fan cable and swapped the pump and system fan and it seems solved the issue. Thx.
-
Can you possibly create custom BIOSes for other Gigabyte mobos as well? Specifically, for the GA-970A-UD3P rev 1.0 in order to resolve GNU/Linux compatibility issues.
Thank you for your answer!
-
Can you possibly create custom BIOSes for other Gigabyte mobos as well? Specifically, for the GA-970A-UD3P rev 1.0 in order to resolve GNU/Linux compatibility issues.
Thank you for your answer!
Yes
Download:
https://drive.google.com/open?id=0B4rC7reRUp6QWWxSYW9CTUF4alk
I will add AMD patches later in free time
Update v11
- OROM LAN Realtek OROM 2.66
- EFI LAN Broadcom UNDI EFI 20.2.0
download:
https://drive.google.com/open?id=0B4rC7reRUp6QZkdwSVZaX2k4a3M
-
Is it possible to create a custom BIOS for 990XA-UD3 FD? I really need some of these features and the BIOS hasnt been updated in years.
-
Hi i am running the V11 Bios. i notice that you say that Bootable NVMe is now possible. Can someone give me a crash course on how. i plan on getting an addon card and a PM961 from samsung.
-
Is it possible to create a custom BIOS for 990XA-UD3 FD? I really need some of these features and the BIOS hasnt been updated in years.
Yes
-
Hi, how do I flash this custom bios? Using qflash? But the custom bios is a *.bin file whereas the official bios are something like *.f4
-
I just wanted to say thank you for making this custom bios! It has let me hold off on buying a new machine while still getting a new drive that will be useful when I do.
I had some trouble installing Windows 10 because I didn't know anything about UEFI. If anyone else gets stuck with the installer telling you it can't install on the nvme drive you have to make a UEFI version of the Windows 10 installer USB with rufus and then it will let you install.
So confirmed working on Gigabyte 990fxa-ud3 rev4.0 with Samsung 970 EVO 250GB.
-
I just wanted to say thank you for making this custom bios! It has let me hold off on buying a new machine while still getting a new drive that will be useful when I do.
I had some trouble installing Windows 10 because I didn't know anything about UEFI. If anyone else gets stuck with the installer telling you it can't install on the nvme drive you have to make a UEFI version of the Windows 10 installer USB with rufus and then it will let you install.
So confirmed working on Gigabyte 990fxa-ud3 rev4.0 with Samsung 970 EVO 250GB.
Thank you for letting us and I hope your PC performance is boosted with the new nvme drive... I am thinking about doing an upgrade too
-
I would like to ask if anyone is running this motherboard with 64GB of RAM? I bought recently 32GB (2x16GB) modules from ebay and tried to make them work... they didn't work with auto settings in the bios so I managed to make them work for a short period with tons of trial and error by tweaking the settings but I didn't have a stable setting and I was coupling them with some other sticks... still I think if they work then it will be great to have a motherboard from that generation run on 64GB stable... I am willing to give it another shot but right now I am skeptic that I can even make the 32GB sticks alone (I always have to add another stick to make it boot)...
-
I would like to ask if anyone is running this motherboard with 64GB of RAM? I bought recently 32GB (2x16GB) modules from ebay and tried to make them work... ....
This board can do max 32GB ram and the memory list shows 4GB per ram side is max hence 8 GB stick is the limit. In other words 8GB sticks in 4 slots = 32GB
-
I would like to ask if anyone is running this motherboard with 64GB of RAM? I bought recently 32GB (2x16GB) modules from ebay and tried to make them work... ....
This board can do max 32GB ram and the memory list shows 4GB per ram side is max hence 8 GB stick is the limit. In other words 8GB sticks in 4 slots = 32GB
Actually it's able to work up to 40GB, I used 2x16GB and 2x8GB and managed to make it work by tweaking the settings but for some other reasons my computer wasn't stable (overheating) then I removed them for fixing but I lost one of the 8GB (a pin was broken)... since then I am running with some other sticks but I only get 18GB recognized by windows (2GB reserved)
I did an update of the microcode of the bios for this motherboard and I will upload the file soon... I used NvmExpressDxe_Small instead since I've read some on the forums say that it's recommended because it's faster and obviously smaller than Fernando initial implantation...
I will do some testing and upload the files.
PS: posting captcha is annoying and hard to decipher
-
I am plain going by the manual hence this info
-
Hello Regit,
Would you be so kind to make this modifications in the 990fxa-ud3 rev1.0 bios to have nvme boot?
Best regards,
TSoft
-
Hello Regit,
Would you be so kind to make this modifications in the 990fxa-ud3 rev1.0 bios to have nvme boot?
Best regards,
TSoft
Sorry is inpossible, it can be done only with motherboard support uefi bios
-
Hello everyone,
Thanks for custom BIOS. Works fine to me.
Can anyone tell me what causes an Ultra ATA CRC Errors on SATA SSD Samsung 860 PRO?
I hoped that after this update, everything would be ok with a drive but on occasions that errors come back again. I replaced SATA cable, even connect to the different power cable.
My setting is AHCI mode, but I think about changing 'On Chip SATA Type' to 'RAID' and see what happens. Anyone had the same problems?
-
Hello everyone,
Thanks for custom BIOS. Works fine to me.
Can anyone tell me what causes an Ultra ATA CRC Errors on SATA SSD Samsung 860 PRO?
I hoped that after this update, everything would be ok with a drive but on occasions that errors come back again. I replaced SATA cable, even connect to the different power cable.
My setting is AHCI mode, but I think about changing 'On Chip SATA Type' to 'RAID' and see what happens. Anyone had the same problems?
Greetings,
Maybe the drive has a formatting error, bad cells or a failing controller?
Maybe the custom BIOS you are running has a problem, error or compatibility issue.
Might changing the operate mode of the controller help, sure. Maybe?
We can only speculate. Where to start... Test the drive, verify its health. Does it behave similarly in another system?
-
Hello everyone,
Thanks for custom BIOS. Works fine to me.
Can anyone tell me what causes an Ultra ATA CRC Errors on SATA SSD Samsung 860 PRO?
I hoped that after this update, everything would be ok with a drive but on occasions that errors come back again. I replaced SATA cable, even connect to the different power cable.
My setting is AHCI mode, but I think about changing 'On Chip SATA Type' to 'RAID' and see what happens. Anyone had the same problems?
Greetings,
Maybe the drive has a formatting error, bad cells or a failing controller?
Maybe the custom BIOS you are running has a problem, error or compatibility issue.
Might changing the operate mode of the controller help, sure. Maybe?
We can only speculate. Where to start... Test the drive, verify its health. Does it behave similarly in another system?
The errors were even on F2 BIOS version. I did RMA and they replace the drive for a new one. Problems still remain. Other HDD drives haven't any errors for years.
I try to run a LiveCD Linux system and test a drive.
I read on Samsung forum the problem is compatibility Samsung 860 drive series with AMD Controllers and they recommend run on Intel Controllers.
I connect to laptop Dell E6400 and test the drive for one hour and there wasn't any new Ultra ATA Errors.
Anyone have Crucial MX500 experience on that mainboard? Is running fine?
-
Hello Regit,
Would you be so kind to make this modifications in the 990fxa-ud3 rev3.0 bios to have nvme boot?
Best regards,
P4nk
-
Hi
I made new bios to Gigabyte 990fxa-ud3 rev4.0
i don test because dont have motherboard ,but should work fine.
You can t kill motherboard because dual bios back backup bios if something get wrong.
It f4a witch some changes :
OROM AMD RAID MISC 4392 - 3.2.1540.6 uppdated to 3.3.1540.19)
OROM AMD RAID MISC 4393 - 3.3.1540.17 updated to 3.3.1540.19)
EFI AMD RAID - 1.0.0.45 updated to 1.0.0.49)
EFI AMD Utility - 1.0.0.45 updated to 1.0.0.49)
OROM Realtek Boot Agent - 2.60 updated to 2.64)
EFI Realtek UNDI - 2.027 updated to 2.035)
EFI Broadcom UNDI - 14.0.6 updated to 17.0.5)
OROM Broadcom Boot Agent (new rom 16.8.0)
I wil add vishera fix in next version, and update amd agesa .
(http://i68.tinypic.com/2z7fzwn.png)
https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg (https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg)
Hi
will this custom bios work on GA-990FXA-UD3 (rev 3.0)?
-
WoW, people still using this ancient chipset?
-
Hi
will this custom bios work on GA-990FXA-UD3 (rev 3.0)?
no it wont but this will:
it will boot nvme and is the latest un released FDN bios that I modded with the latest option roms and microcodes at the time.
https://forum.giga-byte.co.uk/index.php?topic=16626.0
-
not everyone has a bag of money for these things. ;)
WoW, people still using this ancient chipset?
-
I updated this firmware with the proposed fixes, except the boot (broadcom boot agent 20.6.0), in which the UBU tool, apparently does not contain the version above.
Hi
I made new bios to Gigabyte 990fxa-ud3 rev4.0
i don test because dont have motherboard ,but should work fine.
You can t kill motherboard because dual bios back backup bios if something get wrong.
It f4a witch some changes :
OROM AMD RAID MISC 4392 - 3.2.1540.6 uppdated to 3.3.1540.19)
OROM AMD RAID MISC 4393 - 3.3.1540.17 updated to 3.3.1540.19)
EFI AMD RAID - 1.0.0.45 updated to 1.0.0.49)
EFI AMD Utility - 1.0.0.45 updated to 1.0.0.49)
OROM Realtek Boot Agent - 2.60 updated to 2.64)
EFI Realtek UNDI - 2.027 updated to 2.035)
EFI Broadcom UNDI - 14.0.6 updated to 17.0.5)
OROM Broadcom Boot Agent (new rom 16.8.0)
I wil add vishera fix in next version, and update amd agesa .
.
https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg (https://drive.google.com/folderview?id=0B4rC7reRUp6QeDRGRHlhWk5CdXc&usp=sharingg)
-
Can you possibly create custom BIOSes for other Gigabyte mobos as well? Specifically, for the GA-970A-UD3P rev 1.0 in order to resolve GNU/Linux compatibility issues.
Thank you for your answer!
Yes
Download:
https://drive.google.com/open?id=0B4rC7reRUp6QWWxSYW9CTUF4alk
I will add AMD patches later in free time
Update v11
- OROM LAN Realtek OROM 2.66
- EFI LAN Broadcom UNDI EFI 20.2.0
download:
https://drive.google.com/open?id=0B4rC7reRUp6QZkdwSVZaX2k4a3M
Hello.
https://drive.google.com/drive/folders/0B4rC7reRUp6Qdnl2MUNfdEctaEk
990-xa-ud3 rev 1.0
unstable for me.
-
that would be awesome :) thanksy
try this:
https://drive.google.com/open?id=0B4rC7reRUp6QLTVZdVBNRVBCZlE
Important:
The "BOOT" section of the UEFI BIOS and the shortcut to the "Bootable Devices" will not show the NVMe SSD, although it may be bootable!
After having installed the NVMe supporting OS in UEFI mode onto the PCIe/M.2 connected SSD, you will see the new bootable system drive listed as "Windows Boot Manager"
Write if work if no i will try something other.
Hi! I can't seem to access the drive. Can you help me, please?
-
I am so glad I found this custom bios to upgrade my 990FXA-UD3 Rev4.0 to support NVME boot for a Samsung 980EVO. I downloaded the bios from the google drive and flashed it using @Bios utility from Gigabyte. I installed the NVME using PCIE adapter and cloned my existing SATA SSD to the new NVME and change the boot order to pick the Windows Boot Manager for the NVME drive and it booted without any issue. Thanks so much to Regit from making this possible. It's a good MB and this enhancement makes it even better.