Hello, I'm new here.
I have a MSI B650 Tomahawk (motherboard) with BIOS 7D75v1F and updated to 7D75v1G + Ryzen 7800X3D (cpu) Curve Optmizer -12,Temp max 78ºC, asmedia sata disabled + XPG LANCER DDR5 @6000 MHz CL40 32 GB (2x16 GB) (ram) stock and EXPO enabled + XPG Levante 240 (cpu cooler) + XPG Core Reactor 850W (psu) + Kingston A400 SATA SSD for System and apps/programs + Seagate Barracuda Green 2 TB HDD (old/replaced) for games and documents + Crucial P3 Plus 4 TB SSD (CT4000P3PSSD8 - new, to replace the Seagate HDD).
I'm using the apu (or igpu or wathever the integrated graphics name is), 8 GB dedicated memory, because I'm waiting until new gpu launch.
My system and HWINFO v8.02 are on the Kingston A400 SATA SSD - SA400S37/480G (if I remember the model correctly) and I set an alarm to trigger if the VDDCR_SOC (SVI3 TFN) sensor (or in my case, CPU_NB/SOC, because I renamed it) voltage reaches or exceeds 1.320 V (because I don't want to fry my 7800X3D), even though I adjusted the voltage, in the UEFI BIOS, to be as close to 1.290 V (CPU_NB/SOC Override to 1.290 V value - these adjustments have been made for about 6 or 7 months -).
Recently, about 1 day or 2 days ago, I bought a Crucial P3 Plus 4 TB SSD (CT4000P3PSSD8) to replace the 2TB HDD Seagate Barracuda Green. After I copy all the data from the Seagate HDD to the Crucial SSD and reinstall everything that was on the Seagate HDD, on the Crucial SSD (Steam, other gaming platforms, games and documents), the CPU_NB/SOC alert is being triggered after a while playing a game, indicating that it reached 1.382 V (the alert message says like Warning: The value of the CPU sensor VDDCR_SOC (SVI3 TFN) has reached the threshold (1.382 V).
However, when I look at the HWINFO CPU_NB/SOC sensor (it was renamed from VDDCR_SOC (SVI3 TFN) to CPU_NB/SOC), this value does not appear as maximum (it does not appear in the maximum values column).
For some reason, either this value is not being registered (presents values lower than 1.303 V), despite the alert having been triggered, or the alert is triggering based on wrong values, even though the alert should only be triggered when the value is equal to or greater than 1.320 V.
I was on the 7D75v1F UEFI BIOS when this problem appeared and I even updated to the most recent UEFI BIOS (so far), which is the 7D75v1G, but it continues to happen that the alert is triggered and the value indicated in the alert is not registered in the maximum values column.
I would like, if possible, this possible bug to be directed to the moderators and HWINFO team, to check if it is a bug, or if the time interval in which the peak occurs is not long enough for the registration to occur of this voltage spike.
Thank you very much
PS: In the images (screenshots), as I do not use the United States of America decimal punctuation system, the decimal values are being separated by ","
I have a MSI B650 Tomahawk (motherboard) with BIOS 7D75v1F and updated to 7D75v1G + Ryzen 7800X3D (cpu) Curve Optmizer -12,Temp max 78ºC, asmedia sata disabled + XPG LANCER DDR5 @6000 MHz CL40 32 GB (2x16 GB) (ram) stock and EXPO enabled + XPG Levante 240 (cpu cooler) + XPG Core Reactor 850W (psu) + Kingston A400 SATA SSD for System and apps/programs + Seagate Barracuda Green 2 TB HDD (old/replaced) for games and documents + Crucial P3 Plus 4 TB SSD (CT4000P3PSSD8 - new, to replace the Seagate HDD).
I'm using the apu (or igpu or wathever the integrated graphics name is), 8 GB dedicated memory, because I'm waiting until new gpu launch.
My system and HWINFO v8.02 are on the Kingston A400 SATA SSD - SA400S37/480G (if I remember the model correctly) and I set an alarm to trigger if the VDDCR_SOC (SVI3 TFN) sensor (or in my case, CPU_NB/SOC, because I renamed it) voltage reaches or exceeds 1.320 V (because I don't want to fry my 7800X3D), even though I adjusted the voltage, in the UEFI BIOS, to be as close to 1.290 V (CPU_NB/SOC Override to 1.290 V value - these adjustments have been made for about 6 or 7 months -).
Recently, about 1 day or 2 days ago, I bought a Crucial P3 Plus 4 TB SSD (CT4000P3PSSD8) to replace the 2TB HDD Seagate Barracuda Green. After I copy all the data from the Seagate HDD to the Crucial SSD and reinstall everything that was on the Seagate HDD, on the Crucial SSD (Steam, other gaming platforms, games and documents), the CPU_NB/SOC alert is being triggered after a while playing a game, indicating that it reached 1.382 V (the alert message says like Warning: The value of the CPU sensor VDDCR_SOC (SVI3 TFN) has reached the threshold (1.382 V).
However, when I look at the HWINFO CPU_NB/SOC sensor (it was renamed from VDDCR_SOC (SVI3 TFN) to CPU_NB/SOC), this value does not appear as maximum (it does not appear in the maximum values column).
For some reason, either this value is not being registered (presents values lower than 1.303 V), despite the alert having been triggered, or the alert is triggering based on wrong values, even though the alert should only be triggered when the value is equal to or greater than 1.320 V.
I was on the 7D75v1F UEFI BIOS when this problem appeared and I even updated to the most recent UEFI BIOS (so far), which is the 7D75v1G, but it continues to happen that the alert is triggered and the value indicated in the alert is not registered in the maximum values column.
I would like, if possible, this possible bug to be directed to the moderators and HWINFO team, to check if it is a bug, or if the time interval in which the peak occurs is not long enough for the registration to occur of this voltage spike.
Thank you very much
PS: In the images (screenshots), as I do not use the United States of America decimal punctuation system, the decimal values are being separated by ","
