Header Ads Widget

ASUS and Gigabyte unexpectedly add support for Ryzen 5000 chips on their AMD A320 chipset

ASUS and Gigabyte unexpectedly add support for Ryzen 5000 chips on their AMD A320 chipset

Some motherboard manufacturers released new versions of BIOS, which add support for AMD Ryzen 5000-series processors to their motherboards equipped with AMD 300-series chipset. According to Tom’s Hardware, ASUS and Gigabyte have done just that.

Ever since the release of Ryzen 5000 (Vermeer) processors, it has been known that they are not supported by older motherboards. To get around this limitation, some owners of AMD X370 chipset based models, at their own risk, started to use modified versions of BIOS, which provided support for new chips. However, using this firmware does not guarantee the stability of the system. Modified versions of BIOS have not become widespread, as they were released only for certain PC models. The official support for Zen 3 on A320 chipset allows us to use the latest AMD processors.

New version of ASUS Prime A320M-K motherboard BIOS.

We would like to believe, that when ASUS and Gigabyte make official flash files available, other manufacturers will follow suit in the near future. Tom’s Hardware reporters approached AMD to see if the company has changed its attitude towards Zen 3 compatibility with 300-series boards. At the time of publication, the company has not responded to the request. Socket AM4 processor socket is one of the longest-lived on the market at the moment & ; it has seen four generations of AMD Ryzen processors. Motherboards with A320 chipset usually have BIOS chips with very limited capacity, so ASUS and Gigabyte had to make some sacrifices to make them work with Ryzen 5000 processors. In particular, the companies removed support for 7th generation AMD A-series processors and Athlon X4 (Bristol Ridge) series chips from the new firmware. However, this is a minor compromise for those who would like to be able to use the new AMD processor without significant costs.

Post a Comment

0 Comments