AMD confirms: There is a bug in the drivers that overclocks the CPU by mistake

AMD ha confirmed the existence of a bugs in graphics drivers that triggers theoverclockarbitrary and unaware, of CPU Ryzen. The company has given the presence of the problem underlining that he is already investigating in order to resolve the inconvenience as soon as possible, even if at the moment he has not provided any other information on the matter.

“We are aware of an issue within our software suite that changes some AMD processor settings for some users. We are investigating the issue and will share more information as soon as possible,” said an AMD spokesperson.

Yesterday we had you reported the reports on the problem in question, introduced by the drivers AMD Software Adrenalin from version 22.3.1. Basically, by activating one of the profiles available for the GPU, the software automatically applies an overclock to the CPU as well. This behavior appears to be related to the integration of the module Ryzen Master inside the Radeon drivers which, according to the company, aims to simplify the overclocking procedure for users in possession of a configuration totally composed of AMD hardware.

The biggest problem, however, arises from Ryzen Master’s inevitable intervention on the BIOS parameters that come overwritten, activating the Precision Boost Overdrive (PBO) without the user being informed. For expert users who had manually intervened on these values, the only way is to overwrite them again by restoring the previous profile. As for the less accustomed to such practices, the best option seems to be to revert to the previous drivers in case of instability.

Ryzen CPUs have all the mechanisms necessary to avoid physical damage to the component, which is why from a safety point of view, concerns are minimal. However, as the same utility remembers (or rather, it remembered, before doing it arbitrarily) the application of a profile that alters the values ​​set by the manufacturer invalidates the warranty on the hardware. At the moment the manufacturer has not expressed itself in this regard, most likely because it is still not clear how the software intervenes on its own accord on the CPU. Of course, we will update you in case of further developments.