AMD's recently released AGESA 220.127.116.11 code for modern AMD Ryzen and Athlon CPUs has been plagued with issues. According to multiple reports, BIOS updates packing the new AGESA code have been prone to serious problems, including CPU performance losses, memory instability, overclocking bugs, and much more.
As a reminder, AGESA code is used to create a BIOS. According to complaints on Reddit, multiple Ryzen users have noted their CPU performance has dropped with the new AGESA code in benchmarks such as Geekbench 5 and Cinebench R20. Some also report higher CPU temperatures and possible WHEA 19 errors when compared to the previous AGESA 18.104.22.168c patch.
But the problems get worse -- according to DeskModder, AGESA 22.214.171.124 is prone to serious PBO and memory bugs as well. High-frequency memory kits such as DDR4 3600MHz are no longer running stably with a rated XMP profile for some users.
The news outlet also confirmed further Reddit reports about reduced CPU performance, with CPU frequency drops of up to 100MHz in single-core and multi-core workloads. Additionally, 5900X and 5950X users have complained about the 2nd CCD "collapsing" with the new AGEA update.
Overclocking capabilities have also been handicapped in 126.96.36.199, with certain voltage values being more limited than before. AMD's PBO menu was also trimmed down with fewer customizations, according to Deskmodder.
DeskModder notes that most of these issues have been a problem since AGESA 188.8.131.52 -- with the exception of the CPU-related performance bugs. Somehow, AGESA 184.108.40.206 inherited all the issues found in the previous version while adding bugs of its own.
Thankfully it appears some motherboard manufacturers are acting proactively. According to ComputerBase, Asus completely halted official BIOS updates to AGESA 220.127.116.11 and will be skipping it in favor of AGESA 18.104.22.168b.
However, most motherboard manufacturers, including Biostar, Gigabyte, and MSI, still have official AGESA 22.214.171.124 BIOS updates available on their respective websites.
If you are an AMD Ryzen owner, we would highly recommend staying away from both AGESA 126.96.36.199 and 188.8.131.52 BIOS updates if at all possible. For now, it appears that 184.108.40.206c is the latest stable AGESA code until AGESA 220.127.116.11b patches arrive which should hopefully fix all these problems.
Stay on the Cutting Edge
Join the experts who read Tom's Hardware for the inside track on enthusiast PC tech news — and have for over 25 years. We'll send breaking news and in-depth reviews of CPUs, GPUs, AI, maker hardware and more straight to your inbox.
Aaron Klotz is a freelance writer for Tom’s Hardware US, covering news topics related to computer hardware such as CPUs, and graphics cards.
Indeed, Asus have the 1..2.0.6b out for my mobo! No sign of 18.104.22.168 anywhere. Glad to miss it.Reply
5600X, B550 Aorus Pro V2, using the latest 22.214.171.124 BIOS (F14), no issues so far. I don't overclock, though (PBO set to Auto, whatever that means), and running a moderately fast RAM kit (3200 CL16, 64 GB worth of Samsung M-Die if that matters). Don't observe any significant differences in temps as well. In fact, I haven't observed any differences after the upgrade.Reply
Makes so much sense now. My windows has been BSOD a lot lately and I thought it was my overclock being unstable at 1.35v with vdroop on auto. But never realized its the bios I recently updated to. I'm using a X570 Auros Master boardReply
Also noticed a performance drop in Cinebench
I've noticed some issues ever since F3c BIOS from Gigabyte for my X570S Aorus Master, which has 126.96.36.199, and was about to install F3 for it which has 188.8.131.52. Now the long wait for a proper, stable BIOS...Reply
And yes, this is my first step away from ASUS since the Socket A days, and this is the first regret I have had.
I tried running a Gigabyte X570S Aero G with both a 3900X and 5950X on the F3d BIOS update and it was an unmitigated disaster. WHEA errors every few minutes, reboots with no warning. Just utter garbage. Rolled back to F2 and it's been rock solid ever since.Reply
Something else I noticed with F3c was the UEFI navigation became -really- sluggish, like you were trying to run a program with half the CPU speed you needed.Reply
Same! I also couldn't even get it to be stable with XMP disabled and no overclocking whatsoever. Bone stock, crash city.Alvar Miles Udell said:Something else I noticed with F3c was the UEFI navigation became -really- sluggish, like you were trying to run a program with half the CPU speed you needed.
It doesn’t pay to constantly be upgrading your BIOS unless you need something specific and addresses that caseReply
If it ain’t broke don’t fix it
Mandark said:It doesn’t pay to constantly be upgrading your BIOS unless you need something specific and addresses that case
If it ain’t broke don’t fix it
Well according to Gigabyte, it is “highly recommended” for all users to upgrade to the F15 (I’m on a B550I Aorus Pro AX) BIOS “ASAP” due to critical vulnerabilities that were fixed in AGESA 184.108.40.206 . Anyway, after the upgrade, first thing I noticed is that they removed the option to set PBO max override so you’re stuck with whatever profile you have saved and restoring profiles doesn’t update memory OC parameters requiring manual changes.
Benchmarks after restoring settings showed a 5-12% drop in performance even at similar clock as before not to mention that it fails to OC to the same clock as before without bumping up all the PBO limits resulting in more heat production.
System would also BSOD randomly with message alluding to a new cpu detected and then proceed to resetting the BIOS erasing all manual settings and even the saved profiles. I’m surprised there’s no communication whatsoever from Gigabyte even though there are numerous reports of similar issues popping up everywhere.
Same here, but B550 AORUS ELITE (rev. 1.0). Gigabytes wording for F14:_Shatta_AD_ said:Well according to Gigabyte, it is “highly recommended” for all users to upgrade to the F15 (I’m on a B550I Aorus Pro AX) BIOS “ASAP”
"• Major vulnerabilities updates, customers are strongly encouraged to update to this release at the earliest.
Credits to "Assaf Carlsbad and Itai Liba from SentinelOne"
• Introduce capsule BIOS support starting this version."