BIOS Update AMD AGESA 1.1.7.0 Patch A (2024)

Kminek said:

Everything seems run ok w/o any problem.

Click to expand...

"It if ain't broke, don't fix it."

That said, according to this page, there is no F22. It goes from F21 to F23, then F24a, and finally F30.

Regardless, my advice stands. Since your system is working fine without any problems, and you are not planning on upgrading your CPU, (and the description of the newer updates make no mention of bug "fixes" or "security" patches, then no need to update the BIOS and risk introducing new problems.

I'm running 1.1.7.0 A with no additional issues over the previous version.

AGESA takes time to mature so it's generally a good idea to be on the newer versions, they improve RAM compatibility and fix bugs that typically stick around for ~1-2 years from release of a new AMx platform.

Kminek said:

Don't want argue with you, but they probably gave away F22 for any reason.

Click to expand...

Its not arguing with me so no worries. I merely showed you what the website for your board showed so you could double check to see what you have. CPU-z showing F22 could mean one of several things. The BIOS firmware has a typo and has the wrong number. The site has a typo and the wrong number. Or the site pulled F22 for some reason.

Kminek said:

But back to the topic. While there is no security patch or bug fix and pc is running just fine, I'll keep it as it is. CPU upgrade makes no sense for me, CPU is good enough for purpose I bought it for. (gaming) And it will last couple more years I guess.

Click to expand...

And that makes sound sense to me. It is common for motherboard makers to release new BIOS updates that only add support for new CPUs that came out after the board left the factory. If not upgrading to one of those new CPUs, why add support for it when the current BIOS version is supporting your current CPU just fine?

TheLostSwede said:

Not all fixes are spelled out
There's really no reason to use an older UEFI.

Click to expand...

Sure there is. The system currently works just fine. So again, why fix something if not broken?

Now for sure, if this was a brand new build and indications were the motherboard sat on the store warehouse shelf, still sealed in its unopened box for many months or even longer, then sure, I would update the BIOS. But the OP has been using this computer "w/o any problem" for some time and has expressed he has no desire to upgrade to a newer CPU. There is just no need to upgrade the BIOS at this time.

TheLostSwede said:

There's really no reason to use an older UEFI.

Click to expand...

Hard disagree with AMD. If it's working, and there's nothing you know you specifically need, leave it alone. Not worth the PITA if it goes wrong.

chrcoluk said:

It probably fixes something

Click to expand...

If you follow the link I provided above and scroll down under the Description column, you will see several BIOS updates that describe various fixes, improvements and addressing vulnerabilities. But there are not such indications of fixes, improvements or addressing vulnerabilities on the latest updates. Only the standard Checksum value (to ensure the download is valid and not corrupt) and the note about the applicable AMD AGESA update.

So, with no fixes indicated, I think it safe to assume the latest BIOS does not "fix something" - it just adds support for new CPUs.

Super Firm Tofu said:

Hard disagree with AMD. If it's working, and there's nothing you know you specifically need, leave it alone. Not worth the PITA if it goes wrong.

Click to expand...

Never had an issue updating the UEFI, if anything, it has always solved problems I've had.
Maybe that's just Gigabyte though. But the Asus X370 board I had was the same.

TheLostSwede said:

Never had an issue updating the UEFI

Click to expand...

And my GB X670 failed to reboot during the flash process and required using USB flashback to get it functional again.

TheLostSwede said:

if anything, it has always solved problems I've had.

Click to expand...

I specifically said if you had no issues. Obviously, if you've got a problem you don't really have a choice but to roll the dice hoping the new AGESA is finally the one that gets it right.

*edit - spelling*

TheLostSwede said:

if anything, it has always solved problems I've had.

Click to expand...

But once again, the OP is reporting there are no problems.

When a system is, and has been working fine, I see no reason to update drivers and especially a BIOS just because a new one is out there. If the update addresses a new problem (or newly discovered security issue), then sure.

While it is very rare for a BIOS update to fail catastrophically turning the motherboard into a brick, it can happen. Typically, a simple reboot resolves any hang-up but a power outage in the middle of the flash, for example, could irreparably corrupt the BIOS preventing a rollback or an update. I have personally seen this twice over the years and it is why I always recommend putting the computer on a good UPS with AVR before attempting the update - and to make sure a good backup of important files have been done too - just in case.

Sadly, the Level 1 tech support people at most motherboard support centers are poorly trained, woefully underpaid, and must strictly adhere to a checklist (or risk termination) when attempting to provide technical support. And right at the top of that checklist is "Update the BIOS" regardless if the caller's problem has anything to do with the BIOS or not. I feel this has led to the false impression that updating the BIOS typically fixes everything. It does not.

Reminds me of the old days when way too often the first repair action suggested by wannabe technicians was always "format and reinstall".

Super Firm Tofu said:

And my GB X670 failed to reboot during the flash process and required using USB flashback to get it functional again.

Click to expand...

That seems like more of a you problem. At least there was an easy way to recover it. Back in the days, some boards could be recovered if you renamed the BIOS file to something specific and put it on a floppy disk. It didn't always work.
I haven't had any issues flashing motherboards since something like 1999... And that was on a Compaq Pentium Pro that decided to misbehave when I worked in a computer shop.

Super Firm Tofu said:

I specifically said if you had no issues. Obviously, if you've got a problem you don't really have a choice but to roll the dice hoping the new AGESA is finally the one that gets it right.

Click to expand...

You're aware that there are a lot more fixes than what are put in the release notes, right? And it might not even be issues you're aware of.
Also, what is a problem on an immature platform? The updates are often fixing and removing limitations that were put in to start with, to make sure the platform was stable.
I suggest reading up a bit on the AMD AGESA development, what little public information there is about it, as there have been some quite big changes over the years.
Then again, you're using Intel, so why are you even here complaining?

TheLostSwede said:

That seems like more of a you problem.
I haven't had any issues flashing motherboards since something like 1999...

You're aware that there are a lot more fixes than what are put in the release notes, right? And it might not even be issues you're aware of.
Also, what is a problem on an immature platform? The updates are often fixing and removing limitations that were put in to start with, to make sure the platform was stable.
I suggest reading up a bit on the AMD AGESA development, what little public information there is about it, as there have been some quite big changes over the years.
Then again, you're using Intel, so why are you even here complaining?

Click to expand...

Yes, AMD consistently has very undetailed "changelogs".

If you're lucky you might get a "bugs fixed".

Yet, people who overclock notice notably difference performance potential from different BIOS versions.

JrRacinFan said:

So my .02, AsRock tends to give you a "validated since" bios revision. I stay on that bios until they give an update that includes the newest AGESA prior to upcoming release of the new parts. In other words, I basically lumped all my ram compatibility and security fixes all at one go.

Click to expand...

I wish the other three big board makers would do the same, but alas...
Obviously with Gigabyte, if it has a letter after the digits, it's not a final release, but that's the only thing that might be worth avoiding.

TheLostSwede said:

That seems like more of a you problem. At least there was an easy way to recover it.

Click to expand...

Sure, but I don't think I'm anything special, so it's possible somebody else could experience the same problem. Possibly the OP who was asking for advice about upgrading a BIOS.

TheLostSwede said:

Back in the days, some boards could be recovered if you renamed the BIOS file to something specific and put it on a floppy disk. It didn't always work.
I haven't had any issues flashing motherboards since something like 1999... And that was on a Compaq Pentium Pro that decided to misbehave when I worked in a computer shop.

Click to expand...

Cool story, bro.

TheLostSwede said:

You're aware that there are a lot more fixes than what are put in the release notes, right? And it might not even be issues you're aware of.
Also, what is a problem on an immature platform? The updates are often fixing and removing limitations that were put in to start with, to make sure the platform was stable.

Click to expand...

I'm aware of that, that's why I said hopefully they'll get it right this time.

TheLostSwede said:

I suggest reading up a bit on the AMD AGESA development, what little public information there is about it, as there have been some quite big changes over the years.

Click to expand...

What makes you think I haven't? I've been using the Ryzen platform for quite awhile now, but thanks for the suggestion.

TheLostSwede said:

Then again, you're using Intel, so why are you even here complaining?

Click to expand...

I am using Intel as my primary machine. There's a reason for that. I also have that GB X670 board that had the issues running 24/7 at full load in the other room. Who's complaining? I offered my advice to the OP about no pressing need to flash an upgrade and offered a possible first hand problem that I encountered. You felt the need to personally attack me. No hard feelings. I still like your weekly gaming posts.

TheLostSwede said:

Obviously with Gigabyte, if it has a letter after the digits, it's not a final release, but that's the only thing that might be worth avoiding.

Click to expand...

They have always followed this version numbering as far back as i can remember, all the way back to my Socket A Palemino days (had an Athlon XP 1700+ on a Gigabyte board). I knew to avoid them as those may have "gremlins", but I also know some users may not.

Kminek said:

Should I apply this update, even I will don't upgrade CPU to ZEN5 or keep current version (F22)?
What this update solves except support of new ZEN5 CPUs?
My MoBo: Gigabyte B650 Gaming X AX ver. 1.1
CPU: R7 7800X3D
Everything seems run ok w/o any problem.

Click to expand...

The latest BIOS versions patch some MAJOR security holes! Not updating your BIOS to close those security holes would be very foolish indeed! Get the BIOS versions without letters on the end as they are BETA Bios versions. F30 looks like the latest version for your PC. I'd update to that.