A post on Gigabyte’s own US forums claims a new update will fix the current flaky memory compatibility blighting some AM4 boards and some Ryzen CPUs. When? Well, it should appear in the next round of beta BIOS updates.
This year has seen a seismic shift in gaming processors, so here’s our pick of the best CPUs around today.
Currently it can be a bit of a lottery as to which boards play nicely with which memory, and the same can be said for the processors themselves. When I was testing the Ryzen 5 1600X against the R5 1500X the excellent hex-core chip easily managed to operate with its DDR4 memory running at 3,000MHz while the quad-core chip could only reach 2,667MHz with the same Crucial DIMM kit. Yeah, awkward.
The post by one of Gigabyte’s US technical marketeers though claims the AGESA 1.0.0.6 microcode update will beef up Ryzen’s memory compatibility with over twenty new memory kits registered with automatic support out-of-the-box. There are other fixes in the upcoming code, but at least for us the memory compatibility is the most interesting.
Just to recap these are the other issues reportedly also being worked on:
*For those looking for IOMMU fixes we are hopefully going to have an option to force boot off a specific PCIe slot. Its not the grouping fix, but a work around for now.
*Disable LAN (Per request)
Disable Audio (Per request)
“ROM Image update” (Being worked on with AMI, no ETA)
Cold boot / Wont boot. Have to re-flash BIOS. (people have referred to this as “soft brick”)
*AGESA 1006 – improve memory (Got high hopes for this one. Going to enable 20+ memory register)
(Edit) P-State overclocking / downclocking while overclocked.
* Should be included in next round of BETA BIOS – but no promises, just the latest I heard from our BIOS guys.
The latest microcode update from April was the AGESA 1.0.0.4a release, so if the post is accurate then this update is what the engineers are working on for the release after next (which I would expect to be 1.0.0.5). Quite when the next round of beta BIOS releases is going to be though is still up for debate, so we may be waiting a while for 1.0.0.6 to surface.
Thanks Hardware.Info