Asus has posted beta BIOS updates built on AMD's AGESA 1.3.0.1F, and the visible change is a two-digit counter on the motherboard's debug display that ticks upward while the system trains its memory. Before this, a first boot after a memory change showed a static code and a black screen for minutes, which is indistinguishable from a board that has failed. PC Gamer tested it on an Asus Crosshair X870E Hero with 64 GB of DDR5-6000 and a Ryzen 9 9950X.

What the counter does

Training is the process where the board tries combinations of voltage and timings, validates each against test patterns, and saves the profile that boots reliably at the memory kit's rated speed. It happens on a new build, after a RAM swap, after any BIOS change that touches memory, and sometimes because the board decides to do it again. On AM5 it can run for a long time, and until now the only sign of life was a fixed debug code.

The new function counts from 00 to 09 and then through 0a, 0b, 0c and so on, which at least tells you the board is working rather than hung. The monitor stays dark, because training finishes before the graphics card is initialised. On the test board the counter reached 11 before the system rebooted on its own and came up normally, which is about as much information as the feature is designed to give: a number that advances means wait, and a number that stops means start checking the modules.

Why it matters more this year

Memory is the expensive part of a build right now. A price-fixing suit filed this month describes a 500 percent surge in DRAM contract prices, and the same shortage has pushed up complete systems. Anyone buying a kit at these prices will be swapping it in and out, testing whether a second pair of modules will train at the rated speed, and each of those attempts now comes with a readout instead of a guess.

There is also a diagnostic gain that has nothing to do with patience. A counter that stops advancing at the same step points at the same failure each time, which is more useful to a support forum than a static code that could mean anything from an unstable kit to a badly seated module.

The beta caveat

These are beta releases, and the writer's own board is on the official AGESA 1.3.0.1d. Asus shipped first, posting the file on its ROG forum rather than through the usual support pages, and other vendors normally follow within weeks. Intel boards handle the same job differently, under the name memory refurbishment, and run most of it in the background where it is invisible to the user, which is why a slow first boot is mostly an AM5 complaint.

Flashing a beta to gain a progress readout is a trade most users should skip unless they are already debugging a memory problem, since a failed flash costs more time than the boot it saves. AMD's own software has been in the news for the wrong reason this month, which is a reminder that firmware and utilities deserve the same caution as any other system-level change. The feature itself is small, and it will be in the stable branch soon enough for everyone who does not need it today.