I’m reposting this in r/MSI_Gaming as well (link here), since I do not know if the issue is specific to MSI boards, or a general issue with AGESA ComboPI 1.0.9.0.
Relevant Hardware:
- Motherboard: MSI’s MAG B650M Mortar Wifi
- RAM Memory: Kingston Fury KF560C40BWK2-32
Upon updating my BIOS to AGESA ComboPI 1.0.9.0, I’ve observed abnormal voltage variations on HWiNFO64, which reported my RAM voltages occasionally dropping to 0 V, or spiking to 3.825 V. In a few minutes after booting, the sensors would stop at 3.825 V and no longer work until I restart my PC; closing and opening HWiNFO64 again without restarting my PC would just result in the sensors not being displayed at all, as they seem to stop reporting back.
This behavior was also saw on CPUID HWMonitor, which reported the same voltage variations and ends unable to find the RAM sensors when closed and opened back, after the above behavior happens.
This does not seem to be just a sensor issue. I’ve ran y-cruncher VST, which is a stress test that often quickly reports instability errors related to voltages, and it returned an error within 10 minutes of stress test; for context, my PC had passed a bit over 11 hours of y-cruncher VST before under the same overclock settings on AGESA 1.0.0.7c.
So far, I’m only aware of this behavior being reported once, on the HWiNFO64 forum (link here), where a new AM5 owner (MSI B650 Tomahawk) on the latest BIOS (AGESA 1.0.9.0 based on the post’s date) reports weird RAM readings, including the same 3.825 V on multiple voltages, a 17.850 V reading on VIN Voltage, as well as PMIC reporting “Yes” on “High Temperature”, “Over Voltage” and “Under Voltage”. I can’t tell yet if it’s an issue specific to MSI boards, or a general AMD issue with the new AGESA version.
For those who already updated their BIOS to AGESA 1.0.9.0 on a AM5 board, I recommend monitoring your RAM voltages and look for the above behavior, then report whether it is happening on your setup. I’ve already reverted my motherboard’s BIOS back to AGESA 1.0.0.7c to avoid potential degradation of my RAM modules, and you may find it wise to do the same if your RAM is under the same issue.