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.
You must log in or register to comment.
I get this issue with my ram temps on my MSI PRO B650M-A, both sticks, randomly low and high temps. I have not upgraded to the new bios yet.
hopefuly MSI - moves on to 1.1.0.0 agesa ; ]
Probably read error. At that voltage ram would literally fucking explode, as others have said.
hopefuly MSI - moves on to 1.1.0.0 agesa ; ]
As for the cause, most likely interference from an another app, which does not implement the mutex to synchronize the hardware accesses. Many of the hardware accesses are indexed and an another app changing the index between HWiNFO specifying the correct index to access and actually reading the data out of it, can and will cause issues such as this.
DDR5 telemetry is read through the SMBUS from the SPDHUB. With an another app changing e.g., the SMBUS address or the index while HWiNFO is reading the data is likely to cause insane readouts such as this one. However, this can affect basically ANY of the monitoring values.
In most cases, the best place to start looking would be any other monitoring, CAM, RGB, etc. tools from third parties or the motherboard manufacturer.
I haven’t updated past 1.0.0.7 c since the later ones so far have been focused on G sku CPUs. Nothing really came to benefit at least the X3D CPUs.
AGESA 1080 included fclk improvements which increased the max stable FCLK for many users. On my 7950x3d the maximum stable FCLK went from 2133 to 2200.
I haven’t updated past 1.0.0.7 c since the later ones so far have been focused on G sku CPUs. Nothing really came to benefit at least the X3D CPUs.
As for the cause, most likely interference from an another app, which does not implement the mutex to synchronize the hardware accesses. Many of the hardware accesses are indexed and an another app changing the index between HWiNFO specifying the correct index to access and actually reading the data out of it, can and will cause issues such as this.
DDR5 telemetry is read through the SMBUS from the SPDHUB. With an another app changing e.g., the SMBUS address or the index while HWiNFO is reading the data is likely to cause insane readouts such as this one. However, this can affect basically ANY of the monitoring values.
In most cases, the best place to start looking would be any other monitoring, CAM, RGB, etc. tools from third parties or the motherboard manufacturer.
3v on ram would instaly kill your ram, even trigger PSU over current, that may just a bug on MSI agesa board.
Probably read error. At that voltage ram would literally fucking explode, as others have said.
it’s a 1.0.9 bios issue , i had the same report on hw monitor * ram temp spike at 255° and 3.285v*, soon as i upgraded to the last bios , reverted down to 1.7.x.x.c and everything went normal again . 7800x3d on a msi b650 tomahawk and corsair vengance 6000 cl30 just for reference