HWiNFO64 CPU Die (Average) Spike?

[Martin]

The Debug File might show me some more details in this case but it's unable to tell what other software might be causing this.
AMD Adrenalin is not using LHM but several other software (e.g. FanControl) are using it.

 

[cbk9]

I see. I'm not using FanControl or any other software like it (afterburner, rivaturner, etc...). Do you still recommend I uninstall Adrenalin to see if high temp spikes reporting continues?

 

[Martin]

It would be interesting to know if the problem happens also without Adrenalin but if that would cause any troubles to you, then better don't do that.

 

[cbk9]

Well, I guess if there aren't any other ways to troubleshoot the problem I'll have to try one of these days running it without Adrenalin. It's just worrying that the temps peak up like that

 

[Zach]

Well, I guess if there aren't any other ways to troubleshoot the problem I'll have to try one of these days running it without Adrenalin. It's just worrying that the temps peak up like that

Nothing to worry about... its just false CPU reporting. These are not actual high temps. The CPU will shut down by itself long before it reached 120+C. They have safeties you know...
In your adrenalin drivers, do you have AMD metrics on?
If yes try to disabled them all before you uninstall them.



EDIT:
typo

 

[cbk9]

Thanks, I'll try that. I did have them on and they are tracking a lot of CPU stuff

 

[Ahmad998]

The CPU Die 157 degrees Celsius ??



is this bug or another reason? i use stock cooler and never saw CPU die beyond 101 degree Celsius.

 

[artlck]

The CPU Die 157 degrees Celsius ??

View attachment 11603

is this bug or another reason? i use stock cooler and never saw CPU die beyond 101 degree Celsius.

Well, mate, it looks like the stock cooler can't cool your 5600.

Jokes aside, that's a reading bug.

 

[Martin]

Try to upgrade HWiNFO to the latest version, it might help to mitigate that bug.

 

[Blue Panadol]

Thanks for your feedback.
This small increase might be different from those double readings discussed mostly in this thread. I can reproduce such smaller peaks when running HWiNFO along with LibreHardwareMonitor, which is also used by some other tools like FanControl. If you experience such issues, try to run HWiNFO without any other such tool.
We need more testing and reports.

Hello Martin, I don't use any additional software like you mentioned yet I am also observing these small peaks, I'm using the lates HWINFO version as well.

 

[Loki]

Hi Martin, I don't use any additional software and disabled AMD Adrenalin metrics as well. I am seeing spikes with the SoC, MISC, FCLK, UCLK. I am using the latest Gigabyte b650 eagle ax F32e beta bios and the latest beta hwinfo64. I have updated to the latest AMD chipset drivers (AMD 9600x cpu). The voltage spikes aren't double values, MISC would spike from 1v to 1.179v, SoC spikes from 1.194v to 1.277v.

 

[Blue Panadol]

Hi Martin, I don't use any additional software and disabled AMD Adrenalin metrics as well. I am seeing spikes with the SoC, MISC, FCLK, UCLK. I am using the latest Gigabyte b650 eagle ax F32e beta bios and the latest beta hwinfo64. I have updated to the latest AMD chipset drivers (AMD 9600x cpu). The voltage spikes aren't double values, MISC would spike from 1v to 1.179v, SoC spikes from 1.194v to 1.277v.

Same exact case as me, except i'm using F4 for my Eagle AX, it's definitely not a bios issue, it has to be a sensor issue? since there are other persons with this ~6% increase I believe this isn't something to be too concerned with.

 

[Loki]

Same exact case as me, except i'm using F4 for my Eagle AX, it's definitely not a bios issue, it has to be a sensor issue? since there are other persons with this ~6% increase I believe this isn't something to be too concerned with.

I have no idea if it is a sensor readout bug or not. I have logged the hwinfo64 data to a csv file, and while viewing the data, I noticed that all the spikes happen at the exact same time (I used the logvisualizer web app to view the logs).

 

[Marcus_john]

Do I have the sun in my PC? 460 wtf

This is with a MSI x870e tomahawk mb.

 

[Zach]

Some more and you got yourself a fusion reactor… lol

I wouldn’t worry, its an obvious report or reading bug
CPU cores look like they are peaking at 88-90C and IOD at 64C.

 

[Martin]

I have tried several workarounds over the time but none seems to have solved this. When the internal CPU telemetry delivers wrong data, it's hard to "fix" this on my side.
Another issue might be if you're running another monitoring/tweaking or fan/RGB control application that might be colliding with HWiNFO and resulting in wrong data.

 

[Marcus_john]

I have tried several workarounds over the time but none seems to have solved this. When the internal CPU telemetry delivers wrong data, it's hard to "fix" this on my side.
Another issue might be if you're running another monitoring/tweaking or fan/RGB control application that might be colliding with HWiNFO and resulting in wrong data.

I tried with HWmonitor and it gave me the same high numbers. With zero other programs on and not at the same time as HWinfo.

 

[Martin]

That means the problem is in internal CPU telemetry (SMU).

 

[opti931]

View attachment 12425
Do I have the sun in my PC? 460 wtf

This is with a MSI x870e tomahawk mb.

I got the same issue, and some 1.8-2.1v VDDCR_SOC voltage, this is with a MSI B850 EDGE TI WIFI mb
I used same like MSI Center and Deepcool Creative to control my case fans and rgb light , because Fancontrol couldn't control my fans with this mb