GIGABYTE Latest Beta BIOS

[msallal]

is there any update bios for Z390 AORUS Xtreme, I still could not able to run the 10gbe ethernet on all bios version

[msallal]

I have same motherboard Z390 Aorus Xtreme and my 10gbe is not recognized at all, even in bios i see only NAN for 10gbe network adapter MAC address, I am struggling with this since i got the motherboard.
Any advice

[FranciscoCL]

Guys do you know any setting that I can tweak in the motherboard to prevent cold boot issues when having high FCLK. The system trains well but fails to start from cold boot. On many forums they suggest to increase the PLL voltage or enable ln2 mode but when enabling ln2 mode the system won't post at all. Cannot find the PLL voltage settings in B550 Aorus Pro. Any help would be appreciated.

I have the same board, latest BIOS.
t refuses to boot at 1900 FCLK, and I'm getting WHEA errors at 1933+, so 1867 for me (with 3733 16-16-16 RAM and a 5800X).

[rossi94]

I have the same board, latest BIOS.
t refuses to boot at 1900 FCLK, and I'm getting WHEA errors at 1933+, so 1867 for me (with 3733 16-16-16 RAM and a 5800X).

Hmm. 1.2.0.3 fixed my fclk holes. (Mine would only boot till 3833 and then on 3966 and 4000). Now I can be stable anywhere I tried, it even helped on the top end with 2033). But the whea 19s are really anoying. The performance is there if you turn them off and they were not showing up before a certain windows update, so it's definitly a firmware/software issue and AMD should really fix it.

stasio are you okay? Sorry for beeing hard on you, we are all just frustrated with the current state of the platform.

[Jason_Cruze]

I have the same board, latest BIOS.
t refuses to boot at 1900 FCLK, and I'm getting WHEA errors at 1933+, so 1867 for me (with 3733 16-16-16 RAM and a 5800X).

For me the memory and CPU trains and goes to 2033 FCLK with no issues, This has been the same for many BIOS revisions and I think that is the ceiling of my 5600x chip.
I can get everything stable, but once I power off and start my computer afresh it won't post.

So I'm stuck with 1900 FCLK as of now. I do not have any WHEA errors thrown in my PC. Just the system won't cold boot. On researching, it seems that the CPU PLL voltage resets itself after complete shutdown and does not retain the value it supposed to when it worked during the memory training process. Since I'm not sure of the setting in the mobo of gigabyte I'm stuck.

Interesting fact is that it didn't needed any tweaking and worked at 1967 FCLK in f11j bios revision based on 1.1.0.0 and did not have any cold boot issues.

[rossi94]

For me the memory and CPU trains and goes to 2033 FCLK with no issues, This has been the same for many BIOS revisions and I think that is the ceiling of my 5600x chip.
I can get everything stable, but once I power off and start my computer afresh it won't post.

So I'm stuck with 1900 FCLK as of now. I do not have any WHEA errors thrown in my PC. Just the system won't cold boot. On researching, it seems that the CPU PLL voltage resets itself after complete shutdown and does not retain the value it supposed to when it worked during the memory training process. Since I'm not sure of the setting in the mobo of gigabyte I'm stuck.

Interesting fact is that it didn't needed any tweaking and worked at 1967 FCLK in f11j bios revision based on 1.1.0.0 and did not have any cold boot issues.

More likely related to your dimms. But you can disable low p states and turn uncore on. It should help stabilze a suboptimal setting.

[Jason_Cruze]

More likely related to your dimms. But you can disable low p states and turn uncore on. It should help stabilze a suboptimal setting.

Still the same result. Something wrong with the BIOS.

[c300g97]

The only thing I can suggest is that it appears your bluetooth & WiFi wireless are possibly suffering some form of interference in your location. I never use either, am strictly a wired guy--wired is faster, more reliable, and more secure--that's my opinion, anyway. As a matter of practice, I disable bluetooth and wifi in my bios via the device manager and keep them disabled (my home network is wired Ethernet.) I would suggest that if possible you go wired with everything--also, going Sata 3 or NVMe or both for all of your drives I recommend (I even do my Macrium Reflect C:\ backups to a dedicated Sata3 partition on an internal hard drive.) My USB keyboard/mouse never drop out, and I use the 2.0 ports on the back, leaving a thumb drive on the USB bios port in the back for bios updates, etc. USB runs off the CPU, remember and is 100% CPU-dependent last I checked.

Since you state that you use a private shop, I'm wondering if he sold you a used motherboard on "special" without the benefit of exchange or return...;) Otherwise, where you buy it from should have no bearing on your being able to RMA the mboard to AMD. Assuming you are not the only customer of the private shop, he should have no trouble simply exchanging it with no additional charge to you--assuming these events are relatively close to the date of your purchase, anyway. It happened to me years ago--I've never forgotten it. I was pretty angry and when I returned to hash it out with the guy, he was gone! Disappeared like Houdini! Learned a valuable lesson that day.

This is just speculation, of course. It could be something as simple as your external USB drive being fairly old and slightly incompatible with the USB port you are using, etc.

Hope you can work it out! It seems like something simple to me that might be easily addressed with a change in your hardware strategies.

Yes the shop does have many customers, and it does sent RMA stuff to the prorietary companies... but they will test everything out before doing so, basically will take my motherboard and plug in some ryzen 3 3100 and test if mouse and keyboard works for 5 minutes, and then complain about the fact that now they've waisted time... I know the procedure already trust me, the motherboard was brand new, but i should've bought it online and spared me the chore of all this..

[Waltc]

Yes the shop does have many customers, and it does sent RMA stuff to the prorietary companies... but they will test everything out before doing so, basically will take my motherboard and plug in some ryzen 3 3100 and test if mouse and keyboard works for 5 minutes, and then complain about the fact that now they've waisted time... I know the procedure already trust me, the motherboard was brand new, but i should've bought it online and spared me the chore of all this..

I guess so...but instead of taking out your motherboard--take your whole system (minus kybd/mouse) in and ask him if he can tell you why it isn't working properly. But you are probably right about buying somewhere else--tell the guy what you think at the same time. Won't hurt to try...;)

[Funder]

could someone give me the f3 version of the aorus elite ax z590 please?

[rossi94]

MSI just released betas for 1.2.0.4, can we just skip 1.2.0.3 Patch C and get 1.2.0.4 sooner?

[baldersz]

MSI just released betas for 1.2.0.4, can we just skip 1.2.0.3 Patch C and get 1.2.0.4 sooner?

I think it will be quite some time before we see another BIOS release from gigabyte after their epic ransomware attack

[c300g97]

MSI just released betas for 1.2.0.4, can we just skip 1.2.0.3 Patch C and get 1.2.0.4 sooner?

That means Gigabyte will maybe release it , in december :D

[Jose Mar�a Alonso]

That means Gigabyte will maybe release it , in december :D

That was before ransom, they released eveything late.
Now, they arent even releasing them late.
Also no news here because Stasio still have no connection with GB servers.

[rossi94]

That was before ransom, they released eveything late.
Now, they arent even releasing them late.
Also no news here because Stasio still have no connection with GB servers.

Maybe the randsomers are going to give us our betas.