Recent content by Geek_Geekson

In case of "out of range" value readed on some iteration, I think that the best solution will be giving "NaN" value and exclude these values from min/max monitoring, instead of giving "0 RPM".

Tested continuously during 2 days. No glitch. Seems that fixed.

Still present.

Tried this build. 0 RPM glitch still present :(

No, I said that I see this glitch very often also when HWiNFO running alone, without any other tools. This example illustrates only that this glitch I see only in HWiNFO.

Catched with parallel running: [attachment=3339]

AIDA64 (stability test window) and something else (don't remember). HWiNFO running alone.

Yes, other tools that able to monitor min and max values - never show min of 0 RPM, during 2 months. But in this tool I see it very often.

Chassis fans which connected to motherboard and controlled from motherboard (BIOS settings), via PWM or DC - no matter for glitch.

Used program about 1.5 month, and seen for first time. I should to enable Debug mode in settings, and in case of bug close program and then post HWiNFO64.DBG file? And what about 0 RPM? I see it only in this program, other monitors never indicating minimum of 0 RPM.

1) Another funny glitch, huge max core powers. Seen for first time. See attachment. 2) Chassis fans RPM sometimes "drops" to 0 RPM, but they actually are rotating.

Used program for 1 month, but seen this bug for first time (after 11-hour stress-test of RAM, RAM is ok). See picture. Win7 x64, Ryzen 7 1700, no any overclocking. Standard settings in program.