HWInfo64 v8.12 doesn't show Renesas controller (v8.10 and earlier do)

JAEMzWOLF

Member
After upgrading to 8.12, the Renesas controller sections of HWInfo do not show up anywhere in the software - restarts, cold boots, and reinstallations change nothing - however, simply installing 8.10 or any previous version (that could see the Renesas controller) will go back to show Renesas controller based readouts. This is on Gigabyte z790 MASTER X - F5 bios - running the latest public build of 24H2 W11 Enterprise - the only thing to change is the version of HWInfo to make the bug show. I have no included any debug info/etc because I don't see how that would help with this since its entirely HWInfo version specific, but if that is needed, please reply back.
 
Yes. please attach the HWiNFO Debug File. Best would be from both v8.10 and 8.12.
 
Well, it appears that the issue might have been caused by installing the new version over the current version - I have don't that plenty of times with no issue, but anyways, before running the reports/etc. for each version and I did an uninstall before installed either version - and wouldn't you know, the Renesas section is there where it belongs. I don't know if the files you wanted are wroth anything anymore, but I will attach them anyway. Thank you for your time!

Attached - "v810" or "v812" appended to file names to denote which version the report and debug file come from.
 

Attachments

Installing new version over previous one should not be a problem.
Anyway, if it happens next time, try to catch that in DBG file and attach so I can analyze the details.
 
while I have your eyes, why does it sometimes show a min of 0 and a max of something outrageous (6,500 amp) for current? I can make sure nothing goes to sleep or is permitted to save power, and it still happens, and has been happening for many versions. This should be caught in both of the before attached files, I think. Attached an image to show what I mean.
 

Attachments

  • Screenshot 2024-10-22 023037.png
    Screenshot 2024-10-22 023037.png
    41.2 KB · Views: 3
That looks like a glitch in sensor readout. Can happen if you run other sensor monitoring tools in parallel.
I will try to filter this out in the next build.
 
Back
Top