Yeah, first thing I did when I built my pc, could this be a bug in sensors since the cpu wouldve been fried?You have latest BIOS for your board?
Good thing you manually set SoC voltage. Anything below 1.3V is fine for Zen4.Yeah, first thing I did when I built my pc, could this be a bug in sensors since the cpu wouldve been fried?
Also manually set the soc voltage limits to 1.1 in bios but readings were pretty similar still
Update: went back into bios and set up the manual voltages to 1.25 and disabled amd experience and now temps and voltages are fine
It's a program that's like msi afterburner and nvidia geforce experience but it also tracks your gaming fps/stuff like that. let's you record and stream, shows your display settings and all the features to turn on/off. It's like a hub for all those individual programs.Good thing you manually set SoC voltage. Anything below 1.3V is fine for Zen4.
Yeah its probably a bug, but I cant tell what kind and how deep goes... and something tells me its not just software reading error. Otherwise @Martin would've fix it by now.
You know what I mean if you read the thread from start.
Since I have a Zen3 (5900X) system and my knowledge of AM5 is limited, what exactly is AMD Experience?
Oh that from Adrenalin...It's a program that's like msi afterburner and nvidia geforce experience but it also tracks your gaming fps/stuff like that. let's you record and stream, shows your display settings and all the features to turn on/off. It's like a hub for all those individual programs.
Read somewhere that running multiple system monitoring programs bugs hwinfo readings, since the amd program also monitors that I tried disabling it and sure enough values were back to normal.
Those spikes (which seem to be exactly double of what it should be) are in fact invalid/misreporting. So no damage can happen because of this, it's just a misreporting bug that should be fixed by AMD. It should be possible to fix it a BIOS update once they locate the bug.
Oh okay. Thanks.From my understanding its not error reading by any software but error reporting by CPU (telemetry?).
Im seeing some false readings that are impossible to be true
Thats why @Martin said the quote below.
I see. You're right. Thanks.
does OCCT and HWinfo use the same information from the mobo/components to compile the temp info maybe?This is now happening in OCCT monitoring as well as HWinfo64. Earlier I posted HWinfo64 screenshots, so here are OCCT screenshots to go with it. View attachment 10731
Should I continue using my machine or should I be worried.
I have attached Images of all of the sensors OCCT was tracking if anyone wants to sift through and see if everything seems normal.
I am aware this is HWinfo forum, but the spike is now not just a HWinfo bug. HWinfo was closed out completely, while OCCT was running in the background to track temps while gaming.
does OCCT and HWinfo use the same information from the mobo/components to compile the temp info maybe?
Hi, Martin. I'm not sure if it is useful. So I was testing fclk on my 7800x3d, i found that when i rub karhu ( 24GB) and timespy extreme ( test 2, looped, window enabled) . I can reproduce the spike temp for CPU Die(average) and those three voltage SVI3 TFN also double. In the latest hwinfo, it also report IOD hotspot >90C ( normally just 40C) . Frequency Limit - Global goes above 10GHz lol.
Below is your screenshot with some highlights of all the buggy values your CPU reports.Came here to report the same, confused because the AVG was higher than the single highest DIE temp, but Ive really got no clue how any of this works.
As far as I understood this thread theres no reason for concern ?
Maybe someone can confirm this for me
MSI Pro B650-S Wifi
AMD 7800x3D
EDIT to add cpu cooler: Thermaltake Peerless Assassin (mounted literally two days ago)
Running, HWMonitor, HWinfo, AMD adrenaline
Playing different games but also just Desktop activity, second day in a row this happened.
sadly my screenshots will be in German
View attachment 10912View attachment 10913