Getting unusual readings on the HWinfo

Dear sir,

I am getting unusual readings in two datas (Power reporting deviation & CPU temp die and CCD1 sometimes).

the power reporting shows readings in red with numbers above 47% 87% etc.
and the temp die goes up to 140+ degrees.

i am unsure what is causing it and how to resolve it. is it a concern or its some fault in my system?

kindly let me know so that i can take actions on it

my Specs are
CPU - Ryzen 9 5900x (No OC)
Motherboard - ASUS X570 Proart creator Wifi
RAM - 128GB G.skill RIPJAW V
GPU - ASUS TUF 4090

i have attached the excel sheet showing the time of the data recorded if that helps.
excel link- https://drive.google.com/open?id=10CjKaXatWi7mFtDdk3H588FBtbgfnxWN&usp=drive_fs

kindly let me know about it.

Regards

Rahul
 

Attachments

  • power issues shown.png
    power issues shown.png
    250.1 KB · Views: 6
  • power issues shown2.png
    power issues shown2.png
    256.5 KB · Views: 6
  • power issues shown3.png
    power issues shown3.png
    254.1 KB · Views: 5
  • temp.png
    temp.png
    250.8 KB · Views: 6
 
Dear sir,

I am getting unusual readings in two datas (Power reporting deviation & CPU temp die and CCD1 sometimes).

the power reporting shows readings in red with numbers above 47% 87% etc.
and the temp die goes up to 140+ degrees.

i am unsure what is causing it and how to resolve it. is it a concern or its some fault in my system?

kindly let me know so that i can take actions on it

my Specs are
CPU - Ryzen 9 5900x (No OC)
Motherboard - ASUS X570 Proart creator Wifi
RAM - 128GB G.skill RIPJAW V
GPU - ASUS TUF 4090

i have attached the excel sheet showing the time of the data recorded if that helps.
excel link- https://drive.google.com/open?id=10CjKaXatWi7mFtDdk3H588FBtbgfnxWN&usp=drive_fs

kindly let me know about it.

Regards

Rahul
For temperature (100+C) its just a bug of the CPU reporting to HWiNFO as the thread posted by @Fr0stX76 describes.

For "Power Reporting Deviation" its normal for regular usage the values to be red and practically anything between 1% to 600% (I've seen).
If you read the description of the sensor it states that the reported value is usable only under 100% CPU multithreaded load. In that case PRD should be between 90~110%.
If the CPU load is 1~99% then it doesn't mean anything.

Here is mine on regular usage:

Untitled_180.png
 
For temperature (100+C) its just a bug of the CPU reporting to HWiNFO as the thread posted by @Fr0stX76 describes.

For "Power Reporting Deviation" its normal for regular usage the values to be red and practically anything between 1% to 600% (I've seen).
If you read the description of the sensor it states that the reported value is usable only under 100% CPU multithreaded load. In that case PRD should be between 90~110%.
If the CPU load is 1~99% then it doesn't mean anything.

Here is mine on regular usage:

View attachment 11674
Thanks @Zach i was worried as someone told me red on HWinfo means danger and there is something wrong in it. so wanted some clarification on it.

thanks for letting me know thats its all a bug and nothing to worry about.

just on this note i wanted another query that i had - my CPU usage goes around 40% on idle condition but when i open Task manager it goes down to 5% and keeping the Task manager open maintains it at that usage. so is this due to some setting or its normal? any idea on this?
 
for when i have checked it ranges from 86% and in other screen shots if you see its been 120% as well
1725810487535.png
what number should it be like and what number is a indication of a urgent attention thing ?
 
just checked this when the PC starts the utility goes to a 110+% and then falls down to 15% if the task manager or HWinfo is opened.
1725859012182.png
 
Hello,

my PC is restarting for some reasons. the Fans Ramp up and the display of main and secondary monitor gets affected and one of it shuts down. then the PC is non responsive and i have to restart. i felt that was the issue with the Fancontrol app but i have removed it but still its persistent.

can you suggest what can be the issue.

i have attached the debug file (hope its caught it in the report)

 
Last edited:
Back
Top