Ever Increasing System Memory Usage


Active Member
Using the latest Beta of HWINFO64 and the memory usage of the app keeps climbing and climbing. The other day i found it using near 4GB of system memory and it just keeps climbing and climbing. 

I have checked all my settings and to the best of my knowledge, there are no logging options enabled. I use the latest build of Rivatuner to run OSD overlays in my games.

I put my system to sleep every night and wake it the next morning. 

I have attached my DXDIAG, i would appreciate any troubleshooting suggestions you can offer. 



  • DxDiag.txt
    138.5 KB · Views: 0
Can you please try to disable sensors one by one (press Del key on the sensor heading) and see if you can catch which sensor is causing this.
Please let me know the result.
Thanks for the results, this is interesting. Now we should somehow get closer to why this happens...
Would you be able to determine if there's some particular sensor readout under those sensors that when disabled will also solve this ? So enable back the entire sensor headings and try to check particular readouts.
Can you please try another test?
If you're using Sensors-only mode, then uncheck that setting. Then run HWiNFO and you should get a summary window. Leave that window opened without opening the sensors window and watch memory usage. In the summary window you can also choose which GPU to show, so if the memory grows you should also know which GPU polling is causing it.
Just disable the "Sensors-only" check at HWiNFO startup, the rest should be easy then ;)
You might have disabled the welcome screen, or perhaps using auto-start ?
You can change these settings by right clicking on the HWiNFO tray icon.
In the process of restoring sensors and trying (unsuccessfully) to restore that welcome screen, the issue has gone away. Not sure why or how, but it looks like memory consumption is peaked at around 100mb. I'll keep testing over the next few days and let you know.
Well, that's interesting. Would be great if it would be resolved, but still wondering how that could have happened...