When double clicking HWiNFO system tray icon, the icon is removed from tray, and the next app (e.g. geforce experience) open as it had received the double click
Not all other tray apps will open if placed after HWiNFO, e.g. Logitech gaming software
No no no, it is you that have multiple lists :)
The way I see it there is only one list that is divided across tabs, I think most users will agree.
The customization window actually take values from all "lists" as it should IMO, but selection is invisible.
So the solution can be, either use...
Right clock a sensor and select customize value..., click ok or cancel, right click another sensor and select customize value..., now the new sensr and the one before will be selected.
Sometimes even more than two sensor get selected.
In bios i can disable SATA interface, yes hardware configuration changed but the samsung device is NVMe device , not SATA.
If I change the SATA device from AHCI to RAID this does not happen even that hardware configuration was changed.
My guess it is due the S.M.A.R.T implementation and sensors...
Recently I noticed that if I disable SATA interface, I lose customization of the NVMe drive, as well as "Drive temperature 2" sensor in try.
The sensors are split to 2 tables, with many of various sensors disabled and hidden.
Only the NVMe sensors are effected, the GPU sensors after...
So finally after quite some time I have noticed HWiNFO is not running today.
I han't say the machine is 100% (under clocked/volted) so it may have something to do with it.
The forum didn't make it easy to attach a file this size...
Three threads of Prime95 and other programs like IE, same as always.
It did happen after a while, can't say exactly when, no notification, I just noticed the one sensor I have (CPU Package temperature) is gone.
Been a while and it haven't happened again, I set debug mode and will send it if it...
I am trying to help a guy with i5-3570K that cannot set ratio above x38.
BIOS reports Ratio Status unlocked, though Max cannot be seen (thank you MSI)
In HWiBFO CPU report:
Can it be that Intel somehow "forgot"...