Search results

  1. C

    HWiNFO loses some sensors

    I was referring to myself as a client, or rather a paying customer. :) As for the "client" (as in software) using the data from HWiNFO, I have no control of that, or I would have just done it.
  2. C

    HWiNFO loses some sensors

    Yes I saw that, and "this client" - also a paying "subscriber", was asking for a similar change! But I get it, you won't do it.
  3. C

    HWiNFO loses some sensors

    That might very well be, but I have no control over what is being used. So it would be very helpful if you could do the mentioned change.
  4. C

    HWiNFO loses some sensors

    @Martin The issue I'm having seems related to this: https://www.hwinfo.com/forum/threads/sensor-reports-from-corsair-h115i-aio-are-glitching.7991/ I see that you added a workaround when HWiNFO momentarily lose sensors from the Corsair AiOs, except it does not seem like that workaround extends...
  5. C

    HWiNFO loses some sensors

    Great, thanks @Martin !!!
  6. C

    HWiNFO loses some sensors

    A follow-up question that will help me debug this: Exactly what happens if HWiNFO "loses" a sensor for a few seconds, and "Report value in Gadget" has been enabled for that sensor? Will HWiNFO then delete the sensor and its value from the registry the next update cycle, and will it re-order...
  7. C

    HWiNFO loses some sensors

    I'm using a registered version of HWiNFO to visualize my temperatures, fan speeds and others through a sidebar gadget. I'm also using it with FanControl (https://github.com/Rem0o/FanControl.Releases) and the HWiNFO FanControl plugin (https://github.com/Rem0o/FanControl.HWInfo). This plugin reads...
  8. C

    I rolled back to 6.42, thank you!

    The same thing goes for the "HWInfo Monitor" sidebar gadget, yes I still like my sidebars! :) It too stops working every 12 hours as it depends on Shared Memory access. I hear you when you claim that restricting the free version this way was only done to limit commercial benefit from this...
  9. C

    Wrong GPU Memory Clock Shown

    There is a really easy solution to this. In your "sensor status" window, just right-click on "GPU Memory Clock" and chose "Customize values...". In the "Custom" tab change "Multiply" from 1 to 4 and click on "Set". Now HWiNFO will show the same value as MSI Afterburner.
Back
Top