HWiNFO64 CPU Die (Average) Spike?
- Thread starter Venoxium
- Start date
Hard to believe 134°C+, but 114 is closer. I also set manually thermal limit to 95 in the bios.
JasonVoorhees
New Member
Hey there,
from as far as i can tell i seem to have the same issue but a little bit different from others. Currently on an ASUS Rog Strix b650a board and a 7800x3d and my readings dont necessarily always double but sometimes only rise by 16,7% or around 25% for vsoc,vdd, average die temps and some other things i dont really know the name in english for. I randomly checked the metrics diagram on the adrenaline software and it regiostered a spike in voltage the same time hwinfo gave me the warning. Could it be that Adrenaline is interfering with Hwinfo or is that something to actually worry about? I know, i know, i ve been the one millionth person here to ask this question but this time its beeing recorded not only by hwinfo but also by AMD's own software.
from as far as i can tell i seem to have the same issue but a little bit different from others. Currently on an ASUS Rog Strix b650a board and a 7800x3d and my readings dont necessarily always double but sometimes only rise by 16,7% or around 25% for vsoc,vdd, average die temps and some other things i dont really know the name in english for. I randomly checked the metrics diagram on the adrenaline software and it regiostered a spike in voltage the same time hwinfo gave me the warning. Could it be that Adrenaline is interfering with Hwinfo or is that something to actually worry about? I know, i know, i ve been the one millionth person here to ask this question but this time its beeing recorded not only by hwinfo but also by AMD's own software.
Attachments
Last edited:
I see only a slight difference, no 2x values anymore.
Is this without FanControl ?
Yes (witch sounds interestingly good to me) and by the way, if my cpu global max frequency remains @ 6Ghz that doesn't bother me :-D
sehnsucht1999
New Member
Temperatures are all over the place, I was playing Helldivers 2 and the game was smooth as butter, but suddenly I got an alert sound from Hwinfo64, and I saw those Insane temps, so it's really just a bios issue? This temperature also appeared for a split of a second on adrenaline's metrics too
Last edited:
Hi there, I've reported that for me the V8.00-5400 solved the issue, no more double reading in:
- CPU DIE (average)
- CPU EDC
And in:
CPU PPT Limit before 163.7% now 8.5%
CPU EDC Limit before 148.6% now stays within 100%, after 2h gaming it only reached 54.6%
Thermal Limit before because of CPU DIE (average) would go above 100%, like last print with v7.72-5355 that reached 118.2% now reached 65.8%.
I did upgrade the GPU drivers a few days ago, so new driver and new Adrenalin install, I used DDU, and the chipset drivers are the latest.
Do you want me to try the beta 8.01-5424 so I can see if in my end the issue remains solved?
ASRock B550m pro4, Ryzen 5 5600x.
Yes, please.
Ok I'll get back to you here in a couple days if the issue remains solved, sooner if it gives me wrong readings.
I remembered one issue I had that can be something to investigate to everybody that is having this problem, so you can tell me if you have the same issue I found by chance, and if maybe it can be the reason of the double readings.
Long story short, I decided to PBO and AutoOC my CPU last month, and set the negative curve to -20 all cores, and because of that I was having random hard shutdowns/reboots.
Also because of that, and until I settled it at -15 stable, I found in event viewer I was getting an error ID 7000 when it would hard reboot, and although it is not completely related, I discovered that error still persisted after fixing the instability caused by the negative curve.
So it was failing to load the AMDRyzenMasterDriverV22.
I don't have RyzenMaster installed, but still that driver loads up because it comes with the B550 Chipset driver install I think.
So with this I found that it is a common error, where we get two AMDRyzenMasterDriverVxx entries in registry. In my case I had the AMDRyzenMasterDriverV20 and the AMDRyzenMasterDriverV22 entries in registry. And one gives the error in the event viewer pretty much constantly although usually it doesn't impact the system itself, it might be causing something.
There are various solutions, since deleting one in registry, running sfc /scannow, etc, but for me when I deleted it would come back, sfc did nothing, windows is updated, and what solved it was to uninstall both chipset drivers and gpu drivers using the AMDCleanupUtility in safe mode. After that doing a clean install of both chipset drivers and GPU drivers. It was by that time that came out the update to V8.00-5400 so I really can't tell if it was because of fixing that error or because of the version of HWiNFO.
You can check if you have 2 diferent entries in registry in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
Scroll through services folder until you find the AMDRyzenMasterDriver.
In my case it removed the V22 and after the clean install only the V20 is in registry now, so no more V22 failing to load errors.
Might be nothing, but still it might be something that could cause the double readings so maybe it is worth investigating.
EDIT: the v8.01-5424 link doesn't work, should I try with the v8.01-5425?
Last edited:
I've been using 5424 for a week or so. haven't seen a repeat of the 130s kinda numbers but I have seen this on a couple of occasions and to my untrained eye it doesn't look right.
