Tuesday, July 30th 2019
AMD Readies AGESA ComboAM4 1.0.0.3ABB, Addresses Several Issues Affecting 3rd Gen Ryzen
AMD today addressed multiple issues with its 3rd generation Ryzen processors through a highly-recommended update to its Chipset Driver software. To begin with, it stated that several users noticed anomalous behavior with 3rd generation Ryzen chips where the voltages and clock-speeds would be raised as the processor would misinterpret low-scale performance requests from certain software as a request to unlock higher performance states (combinations of higher clock-speeds and voltages to support them). This first came to light when users reported abnormally high voltages at idle when performance was measured by certain software that caused the Observer Effect. The new version 1.07.29 of AMD Chipset Drivers refine the AMD Ryzen Balanced Windows power scheme to be more aware of low-priority workloads and ensure the right state when the system is idling. AMD recommends Ryzen Master software. Version 2.0.0.1233 (or later), as they have fixes to the hardware monitoring module.
The AMD Chipset Drivers 1.07.29 also includes a "beta" fix for the bug that rendered "Destiny 2" unplayable on machines powered by 3rd generation Ryzen processors. The company had earlier tried to fix this bug through an update to its AGESA processor microcode, through ComboAM4 1.0.0.3ABA, although that particular version, not to be confused with the widely circulated 1.0.0.3AB, was found to be buggy and pulled. AMD said it's working on a newer version of AGESA, version ComboAM4 1.0.0.3ABB, which will include "a more comprehensive solution" to the bug affecting "Destiny 2."
AGESA ComboAM4 1.0.0.3ABB will also address a separate issue AMD chronicles as the "Event 17, WHEA-Logger" Windows Event Logger bug. Apparently, some users with M.2 PCI-Express SSDs installed on machines with 3rd generation Ryzen processors are experiencing a number of "Event 17" errors in Event Logger related to their boot drive. One user even complained of System File Checker reporting system-file inconsistencies, although AMD categorically denied accusations of "data-loss" on its platform.
AMD is currently testing and validating AGESA ComboAM4 1.0.0.3ABB and will push it to motherboard manufacturers to encapsulate into their BIOS updates in the coming weeks.
Source:
AMD
The AMD Chipset Drivers 1.07.29 also includes a "beta" fix for the bug that rendered "Destiny 2" unplayable on machines powered by 3rd generation Ryzen processors. The company had earlier tried to fix this bug through an update to its AGESA processor microcode, through ComboAM4 1.0.0.3ABA, although that particular version, not to be confused with the widely circulated 1.0.0.3AB, was found to be buggy and pulled. AMD said it's working on a newer version of AGESA, version ComboAM4 1.0.0.3ABB, which will include "a more comprehensive solution" to the bug affecting "Destiny 2."
AMD is currently testing and validating AGESA ComboAM4 1.0.0.3ABB and will push it to motherboard manufacturers to encapsulate into their BIOS updates in the coming weeks.
22 Comments on AMD Readies AGESA ComboAM4 1.0.0.3ABB, Addresses Several Issues Affecting 3rd Gen Ryzen
Not sure why they didn't put a version number into the filename..
BTW, I'm not sure whether the same issue is applicable to older Ryzen chips, but I've noticed that after upgrading to 1.0.0.3AB my 1600X became much hotter. Checked core voltages, and to my surprise it was boosting over 1.5V vCore during low-thread loads (that's with "normal" BIOS setting, not "auto"). On older version I've never seen such temps or voltages above 1.425V.
EDIT: The link is from community.amd.com/community/gaming/blog/2019/07/30/community-update-5-let-s-talk-clocks-voltages-and-destiny-2
that's the version info
Definitely seems to have addressed the fluctuations in voltage/temperature. And while I have Destiny 2 (they gave it away for free), there's no way I'm reinstalling that to test it. lol
But seriously just use numbers...:kookoo:
Summit/Pinnacle AGESA never went above 1.0.0.7, and I have a hard time imaging they effed up so hard they need to go over 1.0.9.9
Destiny 2 is a random number generator instruction which hardly anyone use.
The instruction bug, very valid and it's been a long time since an architecture haven't introduced bugs like this.
Kl, cfl are refreshes no change so not valid.
Whea bug should really have been discovered and be fixed before launch.
Idle power, voltage, frequency is just kids screaming in fear while everyone says high number, low power consumption in 95% of all cases.
It's still a bug, but blown way out of proportions and I am one affected and its a no issue really.
My own experience since launch is that they behave very different to any other cpu, may it be clocks, temps, power consumption.. You name it all!
Undervolt and it'll say same frequency but performance lowers, temps are always high jut load doesn't really increase it much.
Idle has hardly any power draw.