Thursday, August 3rd 2023
AMD Readying AGESA 1.0.0.7c for AM5 Motherboards
According to a post by @g01d3nm4ng0 on Twitter/X, we now know that AMD is readying yet another AGESA update for AM5 motherboards. The new version is, based on information from our own sources, a minor update to the current version. As such, AMD will be moving from 1.0.0.7b to 1.0.0.7c. @g01d3nm4ng0 didn't reveal any details of the new AGESA apart from the screenshot below, but we asked around and managed to find out what the new AESA addresses.
The update is specifically for those with Samsung DDR5 memory in their AM5 motherboards and it addresses multiple memory related stability issues. We weren't given the full details as to what those are, but there have been some reports about there being issues specifically with Samsung DDR5 memory in some AM5 boards and hopefully this will solve all those problems. We don't have a release time frame for the updated AGESA, but with 1.0.0.7b barely out the door, it might take a few weeks before this one makes it through all the internal testing at the motherboard makers.
Source:
@g01d3nm4ng0 on Twitter/X
The update is specifically for those with Samsung DDR5 memory in their AM5 motherboards and it addresses multiple memory related stability issues. We weren't given the full details as to what those are, but there have been some reports about there being issues specifically with Samsung DDR5 memory in some AM5 boards and hopefully this will solve all those problems. We don't have a release time frame for the updated AGESA, but with 1.0.0.7b barely out the door, it might take a few weeks before this one makes it through all the internal testing at the motherboard makers.
56 Comments on AMD Readying AGESA 1.0.0.7c for AM5 Motherboards
If you ask me, AMD shouldn't be fixing the issue. If the issue is with Samsung memory while other manufacturers aren't having issues, then the problem is Samsung's problem, and they should be forced to recall any products that have that issue.
Again, I cite standards and specifications. If AMD is adhering to the standards and specifications while Samsung isn't, then Samsung should be the one that's forced to fix things.
Right?
#1 Lower it to 5600
#2 Raise the SoC and VDDIO-MEM voltages manually.
#3 Set FLCk/MEM ratio to /2
All are easy to do.
Reports from people with issues is only with enabling XMP/EXPO. Like I said, that is where its up to AMD to have some guidance from MBs vendors. It's all speculation of course to the real issue, but I don't think Samsung is to blame. Nothing wrong with the ICs themselves.
If you really rely on data integrity a change message like this could make you not use Samsung memory at all until the new BIOS is available (and doesn't break anything else you rely on).
At one point, Microsoft had to patch Win95 because during init there was a hardcoded waiting time somewhere. As CPUs got faster, other things started up faster and that delay started to get in the way of other things.