FanControl.Releases
FanControl.Releases copied to clipboard
Rem0o
NZXT Kraken is showing as disconnected when it's still connected, fills logs with unhandled exceptions
Describe the bug Seeing a lot of unhandled exceptions for hardware that Fan Control thinks is missing, but the hardware isn't missing and is available in Windows. There are no errors in device manager, and the hardware that's mentioned in the log is available if I restart Fan Control. It seems to get stuck in this state after the PC goes to sleep.
Is there a log.txt file next to FanControl.exe with recent date entries? log.txt zipped up (it's 275MB unzipped)
Relevant hardware specs and setup https://pcpartpicker.com/user/notthatwillsmith/saved/#view=zmMRVn is the up-to-date parts list. The short version is that it's a NZXT Kraken X53 and an Asus ROG Maximus Z790 with a 13900k. The Z53 is plugged into a powered internal USB hub, because it was not particularly stable when plugged directly into the motherboard. Haven't had any problems with it for 6+ months since I setup the hub though.
Yikes.
When Fancontrol detects the computer resumes from sleep, it will try to do a refresh (equivalent of restarting the app). If the UI is opened, you should see it do the refresh. I suspect somehow it fails to do so and then gets stuck in that "I need to refresh" state and use old handles that are no longer valid.
Your log doesn't have any trace of that behavior, but it's my best guess.
Could you experiement with a couple sleep/resume cycles with the UI opened and see if it successfully refreshes?
I've done several sleep and resume cycles with it both opened and closed and the only time the issue happened is when the window was opened. Here's that log. Is there a way to run a higher level of debug outputs for the logs? The successful runs don't generate any log files. sleep with window open.txt
Question, if you CTRL+R into the UI after sleep, does it comes back on its feet, or does it continue to fail continuously?
CTRL+R doesn't fix it when it comes back, because there are a seemingly infinite number of "An unexpected error has occured and has been added to the log file." errors.
It might be worth mentioning that the system tray indicator which shows the temperature of the water in the Kraken seems frozen too. It also takes a while to start happening. When I just sleep the machine and wake it back up, it happens infrequently, but the longer the machine is in sleep, the more likely it is to happen, with a 100% fail rate when the machine is asleep at night.
FYI, the new update yesterday doesn't seem like it's fixed this issue
@notthatwillsmith Didn't address it as I don't really have an angle on it, seems to be a problem with the HID Kraken V3 implementation in LHM, or weird sleep states, or both.
FYI, I reverted to 171 and stopped having the problem. I'll keep my eye out for updates to the LHM version and will let you know when they fix it. Thanks again for your help.