GIGABYTE Latest Beta BIOS

[stasio]

stasio Anything new for Z590 AORUS PRO AX (rev 1)? Current release F6d seems unstable. Is the currently posted beta F6 newer? I seem to remember an F6e posted at one time. Thanks as always!

F6d=>F6e=>F6

[jwsg]

Hello !! In about 2-3 weeks from now I will buy the b550 aorus elite V2 and I have 2 questions about the bios.

What the most stable recent bios ? I know the f13g is a beta but it is good enough to give a try or better go for the f12 until they release a stable f13. And what about the f13j, it is unofficial or not, because in gigabyte's site there is only the f13g.

And secondly if I install a beta bios (f13g) can I roll back to f12 or whatever because I read that the f13g have a checksum but I'm not sure what exactly is the checksum if that makes any sense....

Thanks in advance !!

A checksum is - well what it says - its a way of adding up all the values of the bytes in a file to give a final "sum" which you then "check" against the checksum value provided. If they dont match then the file is corrupt. This is done during the BIOS flash process to avoid loading a corrupt file - they are just giving you that value that's normally hidden inside every BIOS file.

I'm still on F12 on my B550i as it works with XMP and rBAR and I learnt to avoid USB probs by being careful about which ports I'm using.

With a new PC its best not to jump ahead too far - I enabled more and more settings over time when I was happy with the PC - so I would start with either F12 or latest Beta from the GB site only.

[bep1995]

A checksum is - well what it says - its a way of adding up all the values of the bytes in a file to give a final "sum" which you then "check" against the checksum value provided. If they dont match then the file is corrupt. This is done during the BIOS flash process to avoid loading a corrupt file - they are just giving you that value that's normally hidden inside every BIOS file.

I'm still on F12 on my B550i as it works with XMP and rBAR and I learnt to avoid USB probs by being careful about which ports I'm using.

With a new PC its best not to jump ahead too far - I enabled more and more settings over time when I was happy with the PC - so I would start with either F12 or latest Beta from the GB site only.

Thanks for the answer !! I think I will go for the f12 and i will install the f13 only if I have problems with the f12. But if the f12 have different checkusm than the f13g it will possibly then to downgrade from f13g to f12 for example ??

[Pacomen]

Posted...2 pages back.

Yeah, but ask for F release, already i have a f61e.

Thanks in advance. :)

[Nanochip]

stasio Question for Z590: I notice Gigabyte hasn't yet posted the final Z590 bioses on its website... the beta bioses are still posted.

Yet here, the final BIOSes have been posted since 2 weeks ago (e.g., F5 for Z590 Vision D). Is Gigabyte still testing the final releases?? Shall we expect additional updates beyond what you've so graciously posted?

[jwsg]

Thanks for the answer !! I think I will go for the f12 and i will install the f13 only if I have problems with the f12. But if the f12 have different checkusm than the f13g it will possibly then to downgrade from f13g to f12 for example ??

No checksums dont work like that - they are just a signature and different for each file and nothing at all to do with downgrading - you're overthinking checksums!

[DonDude32]

stasio I have a b550 aorus elite v2 and a 5700g. What bios should I use for this processor?

[bep1995]

No checksums dont work like that - they are just a signature and different for each file and nothing at all to do with downgrading - you're overthinking checksums!

Yeah, I'm overthinking everything since I've decided to upgrade my pc (3-4 months ago), every little detail !! But I'm done, I've checked everything (I think) haha

[MyJules]

No checksums dont work like that - they are just a signature and different for each file and nothing at all to do with downgrading - you're overthinking checksums!

well, technically, a signature is different from a checksum. typically, checksum is hash value of the file.

[Zeeflyboy]

I've had this same problem on both f34a and f34b on my X570 Aorus Master with 5800X, wouldn't have noticed it previously so no idea if it is related to this new firmware... just wondering if I'm alone out there.

Since W11 news I've enabled fTPM in bios in anticipation of testing it out once it leaves the dev channel and moves to beta. Fairly frequently (but not every boot up, maybe one in 4) I get the below message:

"New CPU installed, fTPM/PSP NV corrupted or fTPM/PSP NV structure changed.

Press Y to reset fTPM, if you have bitlocker or encryption enabled, the system will not boot without a recovery key.

Press N to keep previous fTPM record and continue system boot, fTPM will NOT enable in new CPU, you can swap back to the old CPU to recover TPM related keys and data"

Anyone else getting this? Any ideas why? Obvious answer is turn of fTPM but that of course isn't so much of a sustainable option with the W11 requirements and I'd like to be able to use W11's now exclusive features like direct storage and autoHDR in future.

[ne85]

I've had this same problem on both f34a and f34b on my X570 Aorus Master with 5800X, wouldn't have noticed it previously so no idea if it is related to this new firmware... just wondering if I'm alone out there.

Since W11 news I've enabled fTPM in bios in anticipation of testing it out once it leaves the dev channel and moves to beta. Fairly frequently (but not every boot up, maybe one in 4) I get the below message:

"New CPU installed, fTPM/PSP NV corrupted or fTPM/PSP NV structure changed.

Press Y to reset fTPM, if you have bitlocker or encryption enabled, the system will not boot without a recovery key.

Press N to keep previous fTPM record and continue system boot, fTPM will NOT enable in new CPU, you can swap back to the old CPU to recover TPM related keys and data"

Anyone else getting this? Any ideas why? Obvious answer is turn of fTPM but that of course isn't so much of a sustainable option with the W11 requirements and I'd like to be able to use W11's now exclusive features like direct storage and autoHDR in future.

I was getting this (maybe once ever 10th boot?), I figured it was just unstable settings that caused it to corrupt... I ended up getting the TPM adding chip from for like 20 quid in the end as it was more hassle that it was worth trying to figure out why the cause was... as everything seemed stable.

[MyJules]

I've had this same problem on both f34a and f34b on my X570 Aorus Master with 5800X, wouldn't have noticed it previously so no idea if it is related to this new firmware... just wondering if I'm alone out there.

Since W11 news I've enabled fTPM in bios in anticipation of testing it out once it leaves the dev channel and moves to beta. Fairly frequently (but not every boot up, maybe one in 4) I get the below message:

"New CPU installed, fTPM/PSP NV corrupted or fTPM/PSP NV structure changed.

Press Y to reset fTPM, if you have bitlocker or encryption enabled, the system will not boot without a recovery key.

Press N to keep previous fTPM record and continue system boot, fTPM will NOT enable in new CPU, you can swap back to the old CPU to recover TPM related keys and data"

Anyone else getting this? Any ideas why? Obvious answer is turn of fTPM but that of course isn't so much of a sustainable option with the W11 requirements and I'd like to be able to use W11's now exclusive features like direct storage and autoHDR in future.

if you were not using the TPM before and no bitlocker, there's no harm in resetting the device. If you get that message again after resetting it, you have some issues. Personally, i have had fTPM enabled from the day 1 and never seen that message on my x570 elite (and 5950).

[Zeeflyboy]

I was getting this (maybe once ever 10th boot?), I figured it was just unstable settings that caused it to corrupt... I ended up getting the TPM adding chip from for like 20 quid in the end as it was more hassle that it was worth trying to figure out why the cause was... as everything seemed stable.

Yeah I figured that was the route I'd go if I couldn't figure it out. Unfortunately the specific one needed for the board are being scalped at the moment, not in stock anywhere at remotely normal prices...

It shouldn't be anything unstable settings, no problems with the system at all. I do have a ram overclock but it's conservative (only c16 3600mhz on B-die) and totally stable in use throughout all testing and gaming, no WHEA errors etc.

MyJules yeah I have just been resetting it, as I'm not using bitlocker so no big whoop currently, but obviously something isn't right if I keep getting it. The million dollar question (roughly what these TP chips are going for now lol) is what!

[ne85]

Yeah I figured that was the route I'd go if I couldn't figure it out. Unfortunately the specific one needed for the board are being scalped at the moment, not in stock anywhere at remotely normal prices...

It shouldn't be anything unstable settings, no problems with the system at all. I do have a ram overclock but it's conservative (only c16 3600mhz on B-die) and totally stable in use throughout all testing and gaming, no WHEA errors etc.

MyJules yeah I have just been resetting it, as I'm not using bitlocker so no big whoop currently, but obviously something isn't right if I keep getting it. The million dollar question (roughly what these TP chips are going for now lol) is what!

OMG are these guys for real? 200$ for something I paid under 20$ for... proper taking the piss.

The fTPM corruption was an odd one tbh, I had it do it on a ASRock board as well so maybe its an AMD/CPU issue instead of a board issue?

[MyJules]

Yeah I figured that was the route I'd go if I couldn't figure it out. Unfortunately the specific one needed for the board are being scalped at the moment, not in stock anywhere at remotely normal prices...

It shouldn't be anything unstable settings, no problems with the system at all. I do have a ram overclock but it's conservative (only c16 3600mhz on B-die) and totally stable in use throughout all testing and gaming, no WHEA errors etc.

MyJules yeah I have just been resetting it, as I'm not using bitlocker so no big whoop currently, but obviously something isn't right if I keep getting it. The million dollar question (roughly what these TP chips are going for now lol) is what!

@Zeeflyboy, try running "tpm.msc" and see if it says anything.