Should I BIOS update?

OK but you still have REVISION OF THE MOTHERBOARD.

It'll like 1.0 on the 1.1 on the motherboard itself, I know I've had Gigabytes. once you have revision of that board

That BIOS is from 2019, latest one 2024
Download the files.



Besides version, date, filename, use something like Winrar or checksum generator and you will see they are same.

Use HxD, compare the UEFI files, they are identical to the hex, byte, etc.....

aCcSezr.jpg
 
@bitfenix find your board revision number here.

Esxxfff.jpeg

Also, looks like you need at least bios version F36 just for this. (same on both revisions)

Major vulnerabilities updates, customers are strongly
encouraged to update to this release at the earliest.
Credits to "Assaf Carlsbad and Itai Liba from SentinelOne"
 
Would you flash 40d though, they're BETA. F39 would be the better bet wouldn't it?
F40d doesn't say beta, where have you seen beta?

*** edit ***

Ahh the end letter, d. If it had a big issue would have been withdrawn by now IMO, that was released back in Sept 24.

Personally I use a lot of beta UEFIs, I have seen beta become release byte for byte.
 
Last edited:
@bitfenix find your board revision number here.

Esxxfff.jpeg

Also, looks like you need at least bios version F36 just for this. (same on both revisions)

Again, It's only vulnerable to users who already have admin rights. So, in a personal system only used by yourself the risk is limited.

Not saying don't update, but the risk is low
 
Last edited:
General rule of thumb is only upgrade if it fixes something that's a problem for you, adds something you need, or there's a performance increase.

If you do upgrade, reset everything to default (note your settings first), reboot, flash from the bios menu (never from Windows), reboot, reset everything again, then configure it the way you want. Done if the screens can take a long time so you're better off just letting it run even if you think it's hung.

I've had a bad flash recently, so I'd recommend preparing for the worst - download a copy of the manual to your phone and make sure you use a flash drive that will work with flashback. It usually needs something formatted in fat32 but you should give going with something 8gb or 16gb on your tat bazaar of choice.
 
True.

But, actors must have "kernel-level" access to attack your system properly. No one's likely to get that level of access to the PC.

I'm not saying don't update, but the reality of it being exploited I would say is low.
Again, It's only vulnerable to users who already have admin rights. So, in a personal system only used by yourself the risk is limited.

Not saying don't update, but the risk is low
I understand what you are saying, but i always err on the side of caution when it comes to vulnerabilities.
 
True.

But, actors must have "kernel-level" access to attack your system properly. No one's likely to get that level of access to the PC.

I'm not saying don't update, but the reality of it being exploited I would say is low.
Agree some what, but as posted before there are fixes and changes that never make the logs.
General rule of thumb is only upgrade if it fixes something that's a problem for you, adds something you need, or there's a performance increase.

If you do upgrade, reset everything to default (note your settings first), reboot, flash from the bios menu (never from Windows), reboot, reset everything again, then configure it the way you want. Done if the screens can take a long time so you're better off just letting it run even if you think it's hung.

I've had a bad flash recently, so I'd recommend preparing for the worst - download a copy of the manual to your phone and make sure you use a flash drive that will work with flashback. It usually needs something formatted in fat32 but you should give going with something 8gb or 16gb on your tat bazaar of choice.

Your probably aware most BIOS/UEFI updates won't give massive performance uplifts. But these days CPU SMU FW can have behavior change of CPU.

As an example I flashed an early UEFI to my TUF X670E, was using a R5 9600X at the time. All I used was a basic application that loads CPU per thread/per core that I want. The temperature difference between that UEFI and the other was large. See this and this, and I'm at stock for CPU/RAM, etc. Check if the UEFI change logs state that as a "fix".

Back when 3000 series was launched on AM4 again AMD tweaked boost behavior via CPU SMU FW, I modded older CPU FW into newer UEFI to get same boost behavior.

These days besides what code is loading a CPU determining boost behavior there's more hidden temperature limits then before, see this , there's even a medium temperature frequency limit.

A board with flashback is "unbrickable", you have a hardware flash tool on the board. You may be aware doesn't even need any HW installed on board except power.

OP is on UEFI F11, dated about 6 months after first release UEFI F3.
 
Last edited:
Agree some what, but as posted before there are fixes and changes that never make the logs.


Your probably aware most BIOS/UEFI updates won't give massive performance uplifts. But these days CPU SMU FW can have behavior change of CPU.

As an example I flashed an early UEFI to my TUF X670E, was using a R5 9600X at the time. All I used was a basic application that loads CPU per thread/per core that I want. The temperature difference between that UEFI and the other was large. See this and this, and I'm at stock for CPU/RAM, etc. Check if the UEFI change logs state that as a "fix".

Back when 3000 series was launched on AM4 again AMD tweaked boost behavior via CPU SMU FW, I modded older CPU FW into newer UEFI to get same boost behavior.

These days besides what code is loading a CPU determining boost behavior there's more hidden temperature limits then before, see this , there's even a medium temperature frequency limit.

A board with flashback is "unbrickable", you have a hardware flash tool on the board. You may be aware doesn't even need any HW installed on board except power.

OP is on UEFI F11, dated about 6 months after first release UEFI F3.

They also seem to introduce more issues too. I've seen endless reports of people using the Aorus X570 elite with older CPUs 3000 series and newer bioses after a set date causing issues, BSODS, issues with memory etc
 
No worries :) , I don't doubt some can have issues with certain combinations of SW, HW and FW settings. The other factor is happy users are never gonna be posting about no issues, we never know how many users there are of x board.

I don't think public gain access to true alpha/betas. So even the betas are some what tested. Then also how I see it is, a stable release when a bug is found, was in fact a beta, as a newer version is then gonna roll out and replace it. I think bug free doesn't really exist.

I'll be honest I don't hold manufacturers at fault completely. There is only so much testing and so many configurations they can test. They rely on users to test and report back issues. What I do believe in is manufacturers need to have more easy access for owners to state x isn't working, then them to investigate and fix.
 
Last edited:
No worries :) , I don't doubt some can have issues with certain combinations of SW, HW and FW settings. The other factor is happy users are never gonna be posting about no issues, we never know how many users there are of x board.

I don't think public gain access to true alpha/betas. So even the betas are some what tested. Then also how I see it is, a stable release when a bug is found, was in fact a beta, as a newer version is then gonna roll out and replace it. I think bug free doesn't really exist.

I'll be honest I don't hold manufacturers at fault completely. There is only so much testing and so many configurations they can test. They rely on users to test and report back issues. What I do believe in is manufacturers need to have more easy access for owners to state x isn't working, then them to investigate and fix.

Yeah, I know gigabyte did introduce some issues with the latest bioses affecting secure boot too, they did it on multiple bios revisions too. So repeating the same.mistake more than once seems a tad odd!
 
Hello

I have a GIGABYTE motherboard system.

X570 GAMING X (AM4)

Is it worth checking how to update my BIOS version and what changes from current version?

Never flashed a bios to update before can anyone give instructions.

Thanks.
So after looking at the replies, there are good points raised by everyone.

I’m going to suggest you don’t update the BIOS unless you’re having issues with BSOD in Windows or you’re upgrading to a newer CPU that isn’t supported by your current BIOS or there’s a big security issue with your current BIOS version.

Otherwise, enjoy your stable system and don’t mess with it.
 
I've always regularly updated my BIOS, most have a back up now a days, so it's pretty unlikely to brick them now a days. At the end of the day, they don't generally spend the time to make them worse. The only bad thing is they reset all your BIOS settings, overclock, fan profile etc.
 
Personally I always keep my boards bios up to date and that includes beta versions. It's been well over 10 years since I last had a bios update fail and that was easily fixed. It is practically impossible to brick a board these days if you have bios flashback so by keeping the bios up to date you will have the latest security patches, the latest fixes and in the case of AMD boards maybe even a performance boost with the latest Agesa update which can sometimes give a impressive boost. Also keep the motherboard chipset drivers up to date as they are often required by Agesa updates to achieve any boost.
 
Back
Top Bottom