GIGABYTE Latest Beta BIOS

[Olnium]

Hi,

I have a B550m Aorus Elite Rev 1.0, Win 11, Ryzen 5 5600g, 16Gb (2x8) Crucial Ballistix @ 3200 XMP.

Bios version is F14e. I've had nothing but problems with this since I got it about 3 weeks ago. It won't detect my Intel AX200 WiFi PCIE card reliably. When it does detect it, it's gone from BIOS and device manager after next cold boot. I've been using a TP-Link AC1200 USB adapter in the meantime and that keeps disconnecting or dropping from USB 3.0 to USB 2.0 speed. Finally, every 4th day or so, I get the "New CPU installed, fTPM NV corrupted" message on boot and the only way to proceed to Windows is to clear the keys and manually unlock my bitlocker drives. CMOS battery is presumably ok because settings are kept when this happens.

Is there a fix for any of this? Should I revert to F13, which is the last stable release? The board came with F10 but I don't think that has support for G series Ryzen.

[rehsd]

I notice that with F35d on my Aorus Ultra, AMD fTPM is enabled by default (for Win11). This is fine; however, it takes precedence over the hardware TPM by default. I had to disable the fTPM to have the system use the hardware TPM in my system. Does that sound right? Wouldn't it make sense to default to the hardware TPM over the less secure fTPM?

[rehsd]

Another think that I've noticed with F35d is that it messed something up with my USB. My webcam no longer works for Windows Hello on bootup into Windows. It works after subsequent locking of Windows, but not on the initial boot. I have cleared CMOS and loaded defaults in BIOS, but it didn't help.

[Boing]

Why did B350 and X370 get AGESA 1.2.0.5 before B550/X570..?

[Waltc]

I notice that with F35d on my Aorus Ultra, AMD fTPM is enabled by default (for Win11). This is fine; however, it takes precedence over the hardware TPM by default. I had to disable the fTPM to have the system use the hardware TPM in my system. Does that sound right? Wouldn't it make sense to default to the hardware TPM over the less secure fTPM?

I don't think fTPM is less secure at all, as it came on the scene long after the original TPM did. It's just integrated into the hardware in the motherboard now instead of being an optional hardware peripheral you could add. My current motherboard, purchased 2.5 years ago, an x570 Master, supports fTPM in hardware. An advantage of fTPM is that its capabilities can be improved with a software driver--but that doesn't mean it's a software-only feature. Most AMD motherboards ship with fTPM today, and it's a bios controlled feature, which would not be the case if it was software-only. As the latter revision ot TPM, I would stick with fTPM. I ran fTPM under Win10 without a problem for the last couple of years. I never bought an optional TPM module.

[rehsd]

I don't think fTPM is less secure at all, as it came on the scene long after the original TPM did. It's just integrated into the hardware in the motherboard now instead of being an optional hardware peripheral you could add. My current motherboard, purchased 2.5 years ago, an x570 Master, supports fTPM in hardware. An advantage of fTPM is that its capabilities can be improved with a software driver--but that doesn't mean it's a software-only feature. Most AMD motherboards ship with fTPM today, and it's a bios controlled feature, which would not be the case if it was software-only. As the latter revision ot TPM, I would stick with fTPM. I ran fTPM under Win10 without a problem for the last couple of years. I never bought an optional TPM module.

Thanks for the response, @Waltc.The fTPM is part of the AMD (in my case) CPU, not part of the motherboard. AMD has had to patch their fTPM in the past due to security issues (e.g., 2018 Firmware TPM Updates | AMD). It seems that fTPM and dTPM both have their ups and downs, related to security. I found this article helpful: Thoughts dereferenced from the scratchpad noise. | fTPM vs dTPM (3mdeb.com). Thanks!

[rubene66]

lets hope next year we get a bios without usb disconnect drop out issues for B550!

[rehsd]

lets hope next year we get a bios without usb disconnect drop out issues for B550!

Ya', I had a ton of issues when the older AMD AGESA had all the known USB issues. Once they resolved that, things have been good. But now this latest Gigabyte BIOS / AMD AGESA seems to be reintroducing some old symptoms. :(

[rehsd]

Another think that I've noticed with F35d is that it messed something up with my USB. My webcam no longer works for Windows Hello on bootup into Windows. It works after subsequent locking of Windows, but not on the initial boot. I have cleared CMOS and loaded defaults in BIOS, but it didn't help.

I can confirm mouse issues during game play are back, too. Ugghhh....

[cyberloner]

Ya', I had a ton of issues when the older AMD AGESA had all the known USB issues. Once they resolved that, things have been good. But now this latest Gigabyte BIOS / AMD AGESA seems to be reintroducing some old symptoms. :(

change other usb slot... likely they do nothing already

[Waltc]

Thanks for the response, @Waltc.The fTPM is part of the AMD (in my case) CPU, not part of the motherboard. AMD has had to patch their fTPM in the past due to security issues (e.g., 2018 Firmware TPM Updates | AMD). It seems that fTPM and dTPM both have their ups and downs, related to security. I found this article helpful: Thoughts dereferenced from the scratchpad noise. | fTPM vs dTPM (3mdeb.com). Thanks!

Enjoyed the chat...;) Thanks much for the info--I wasn't aware of TPM being in the CPU--but I do remember TPM 1.2! I kind of like the idea of a driver because, as you mentioned, it can be patched, and it can also be improved with a minimum of fuss. I'm just glad it finally made it to the standard AM4 motherboard without having to add an additional hardware module into a dedicated socket on a motherboard. As you say, it's six of one, half-dozen of the other!

[shiecldk]

stasio I found out my Z97X-UD7 TH's BIOS is corrupted by OpenCore bootloader. Unfortunately, both BIOS (main and backup) are corrupted and I forgot to backup the original BIOS. Fortunately, I am still able to backup the corrupted BIOS, which contents the MAC address, with CH341A programmer. I tried to flash the BIOS from downloaded here (Z97XUD7TH.F7a) with CH341A and found out it's in an infinitely boot loop now switching between the main and backup BIOS. Do you know how could I fix it? Also, is it possible to access Q-Flash to flash the BIOS without getting into the BIOS menu or flash it via USB automatically? I appreciate it.

[stasio]

stasio I found out my Z97X-UD7 TH's BIOS is corrupted by OpenCore bootloader. Unfortunately, both BIOS (main and backup) are corrupted and I forgot to backup the original BIOS. Fortunately, I am still able to backup the corrupted BIOS, which contents the MAC address, with CH341A programmer. I tried to flash the BIOS from downloaded here (Z97XUD7TH.F7a) with CH341A and found out it's in an infinitely boot loop now switching between the main and backup BIOS. Do you know how could I fix it? Also, is it possible to access Q-Flash to flash the BIOS without getting into the BIOS menu or flash it via USB automatically? I appreciate it.

You can flash BIOS(:s) from your PC (or in DOS) by FPT (Z97).
I think link is in OC tools sticky thread.
For latest BIOS, contact GB Technical support.

[TweakinOut!]

What's the security updates with F35d? I'm still running F35c

....Aorus Xtreme X570 Rev 1.0

[shiecldk]

You can flash BIOS(:s) from your PC (or in DOS) by FPT (Z97).
I think link is in OC tools sticky thread.
For latest BIOS, contact GB Technical support.

Thank you. However, I cannot boot into any OS or BIOS; would FPT still be assessable in this case? I think the BIOS will also be also stuck at CMOS reset even if it boots in black screen, i.e. no way to boot DOS. Currently, it's stuck in the black screen reboot loops either when I boot with the main BIOS or the backup BIOS. I've taken down both chips, backup the BIOS (in case I need the MAC address or UUID in that corrupted BIOS), and then flashed both BIOS chips (MX25L12873F) with CH341A. I was not able to flash the chips when they are soldered on the MB; I had to unsolder both chips to get CH314A recognize them. But it's stuck in the infinite reboot loop, making me unable boot any OS for use Q-FLASH.