Spikes on VSOC Voltage (MSI B850/9800X3D)

Hi, i recently turned EXPO on on my pc, i see 1.2v is the default vsoc. But i noted vsoc spikes especially in the cpu sensor (VDDCR SOC).
Ppl told me that it must be a sensor bad reading, because vsoc its supposed to be static.
I saw spikes up to 1.287v from 1.2v on the ps3 emulator (very heavy) on the cpu sensor, and on the motherboard (CPU NB/SOC) is normal i think, from 1.21 to 1.23v max.

I also saw patch notes on the upcoming versions that say improved sensor reading on b850 mobos, it could be a bug on hwinfo?

I'll leave some screenshots below. (VDD MISC also spikes a bit)

Gaming - EXPO.png
CPU heavy game, tlou part 1 (a lot of shader compilation)

Cinebench - EXPO.png
5m cinebench r23 loop

GOW - PS3 Emulation.png
GoW on PS3 emulator, very cpu heavy
 
Last edited:
The same "issue" is discussed extensively below

 
The same "issue" is discussed extensively below

Yeah i saw them yesterday, so it's supposed to be a sensor error? not a real problem?
Maybe some program interfiering with the readings...
In my case i only have adrenaline (cus amd gpu), and afterburner (every metric disabled, i only use it for gpu fan control)
 
Yeah i saw them yesterday, so it's supposed to be a sensor error? not a real problem?
Maybe some program interfiering with the readings...
In my case i only have adrenaline (cus amd gpu), and afterburner (every metric disabled, i only use it for gpu fan control)
Its somewhat confirmed that these are CPU reporting to software errors because some users are getting totally absurd values that cant be true like 2+Volts on SoC, 3000~4000MHz on FCLK or 120~130C CPU temp for example.
As for the source of these error values, nothing is certain. Could be some software/driver conflict, some CPU SMU bug or whatever else.
 
Its somewhat confirmed that these are CPU reporting to software errors because some users are getting totally absurd values that cant be true like 2+Volts on SoC, 3000~4000MHz on FCLK or 120~130C CPU temp for example.
As for the source of these error values, nothing is certain. Could be some software/driver conflict, some CPU SMU bug or whatever else.
Okay, so if it's a bug, I'm fine, it doesn't matter haha. Thanks a lot!
 
Back
Top