![]() So, it's not that one program reports something completely different than another program All ways to read the voltages (CPU-Z, HWiNFO64, IPMI) report (almost) the same values.I tried disabling as many sensor types as possible (see INI values below) to see if that changes anything - it doesn't. ![]() The VIDs also don't come down when closing HWiNFO64, they stay high until CPU-Z is (re)started. If I restart CPU-Z while HWiNFO64 is running the Core #0/#1 VIDs come down again - until I restart HWiNFO64. The issue: As soon as I start HWiNFO64 the Core #0 and Core #1 VID don't come down after HWiNFO is done initializing its stuff which is causing higher power draw and temperatures. I wanted to use HWiNFO64 to monitor sensors on a server, but as long as this issue is there, I can't and won't. Before reporting this as a bug I want to investigate further to check if I'm doing something wrong or missed anything. Long time HWiNFO user here, but first time to post in the forum (obviously). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |