GIGABYTE Latest Beta BIOS

[SpajdrEX]

stasio Any bios news for Z490 boards owners for SAM support? I mean nearly every other manufacturers got bios already :-/

[stasio]

stasio Any bios news for Z490 boards owners for SAM support? I mean nearly every other manufacturers got bios already :-/

They working on it...soon....

[g111]

Forgive me a silly question. If i update to F11 from F11n, will i be able to load my current setting profile or will it be deleted?

Yup, any time you change the BIOS it deletes everything, even your saved profiles. So take photos of your custom settings!

Does your system with latest bios keep cpu voltage 1.44-1.50 when idle? Is it normal?

.95v to 1.275v in desktop and during memtest stress testing for me. (5600x)

[jeffk]

Does F11 final solve the ethernet dying ?

Thx.

[rehsd]

Good news: A new PCIe setting in the F31 BIOS on Aorus Ultra to let me run PCIe for the GPU at a different gen than NVME.

Bad news: I'm getting poor NVME write speed for the first NVME slot.

X570 Aorus F31 BIOS >> PCIE settings

Are others seeing similar results?

[lmarcelus]

stasio Is there anything Gigabyte can do about the Realtek PCIe 2.5GbE Family Controller LAN driver/controller? It is a very known and documented problem with this controller, when under load it will randomly disconnect the Ethernet connection. It can happen in every motherboard that uses this controller, RTL8125, even using the latest Realtek Driver (10.45 - Dec.2) wont fix it.

[TrebleTA]

They working on it...soon....

They better be working on the Z390s too

[cder2]

Providing some feedback.
Flashed to F31, didn't change anything for me, still cant post past 1800flck, went back to f30. Suddenly a ton of WHEA Errors in my event log even though i have previously been stable at F30 with an 3600mhz/1800flck overclock for over a week.

Even setting things down to 1333memory with ultra loose timings and 1333flck stock flck the whea errors remain. Disabling core performance boost does take away the boosting but WHEA errors remain. Went back to f31 as f30 is no longer stable but errors remain.

Only when i set a static multipiler for my CPU other then the default 34 will the WHEA errors go away, right now i run a multipiler of 38 and the cpu is running all cores at 3800mhz, i set memory back to 3600 and flck to 1800 and i have zero whea errors.

My idea is that when i flashed to the F31 bios there was some hidden microcode in the bios that gets updated on the cpu chip, and even when you revert back to f30 that microcode remains in the cpu chip, and therefor even tho i flashed back to the my old stable bios f30 i am now having these whea errors.

What an absolute mess. I hope gigabyte can get this fixed, what can i do to push the agenda? Contacting their support seems to be sort of zero result, but i am thinking considering how many people are experiencing these WHEA errors and now me who previously had a fully working system for over a week now suddenly get them too my belief is that soon enough other people who have stable builds will get them when they update their bioses.

Hardware: 5950x
MB: Aorus extreme x579
Mem 4x16gb single rank 4000mhz cl19

[Stanzilla]

There is also still this issue with World of Warcraft and the newer versions of AGESA

[jeffk]

Does F11 final solve the ethernet dying ?

Thx.

Just so you know, its not. Tried an still have ethernet going down.

[prymortal]

stasio Is there anything Gigabyte can do about the Realtek PCIe 2.5GbE Family Controller LAN driver/controller? It is a very known and documented problem with this controller, when under load it will randomly disconnect the Ethernet connection. It can happen in every motherboard that uses this controller, RTL8125, even using the latest Realtek Driver (10.45 - Dec.2) wont fix it.

Ah Yes these issues.
Have you tried & re-done this after every driver update ~ Hardware > Device Manager > Network > Realtek Lan Right Click> Properties > Power Management & disabled all the options. Highly recommend doing this for the Intel Lan as well. It's fixed the "gigabyte bios complaints" to date I've seen on forums including mouse turning off one.
If the new drivers bad (going off experience it's possible), then try the windows 10 generic Lan driver. It worked well enough during early driver releases.

Ok so came to ask a Dumb question Is F31 Final or is there a F32 coming out soon due to the complaints of higher temps reported with this release? ~ Thanks

[g111]

stasio can you hazard a guess on when PBO2 will come out?

ps I lowered my vSoC back down to 1.125 from 1.18-1.19 it was changed to with F11. I'm not sure if the rise from the previous 1.125 is a bug or intended.. but it was and is stable at 1.125

[neo387]

stasio can you hazard a guess on when PBO2 will come out?

ps I lowered my vSoC back down to 1.125 from 1.18-1.19 it was changed to with F11. I'm not sure if the rise from the previous 1.125 is a bug or intended.. but it was and is stable at 1.125

Have a look back at his posts, think he said beta in January

As for the higher vsoc my guess it is intentional either in patch d or from gigabyte for a more foolproof higher fclk, although f11 for b550i still hits a wall after 1867.

Did not experience lan disconnects yet

[mgfirewater]

g111 i reduce my vosc to 1.07 (bios 1.084)

[g111]

Guys I have a question I've been wondering ever since I got this board.. is it normal for vDRAM to fluctuate this much? For example if I have my RAM voltage set to 1.35, it idle at 1.35v, but with load it will rise to 1.4v. This happens no matter the RAM voltage. Idles at x.xx, but adds .05v under load, as confirmed by HWInfo64. Is this by design? Does it happen to others?

This happened for this B550i Aorus Pro AX from day 1 across all BIOS revisions I've tried. I am now on F11, same behavior.
(I also have to compensate in the BIOS by setting a lower RAM voltage, because if I set to 1.35, it will actually be 1.4v idle and 1.45v load. This also happens in optimized defaults with voltage set to auto, with XMP profile.. RAM is supposed to be 1.35V at XMP, but will boot up with 1.4v - and of course go to 1.45v at load. So I have to undervolt to get correct voltage to RAM)