When my PC comes out of sleep mode, after it's been a sleep for awhile, the CAM software shows that it's running in the taskbar, but opening CAM results in a blank window.
Also, the GIF I have applied to my Kraken Elite does not show up. Only the default liquid temp is displayed. I have to exit CAM from the taskbar and reopen it to get things working again.
If I put my PC to sleep and then wake it only a moment later, this doesn't seem to happen.
Some system info:
Windows 11 Pro (all latest updates)
Kraken Elite 280 RGB (Firmware version 2.0.1.1)
RGB Controller (Firmware version 1.5)
CAM version 4.61.6
A year on and still no response from support?
same issue here :(
Here's the fix....... Device Manager > USB Controllers > intel USB 3.20 eXetensible Host Controller > right click > properties > power management > uncheck allow this pc to turn off this device.
I'm also having the same issue with an Elite 360. After wake from sleep the screen goes to default temp reading. I have to X out and restart the program, I'm kinda pissed, my Z73 never had this problem.
Yes. Same here using Kraken 360 firmware 2.0.3. I'm not using any RGB and don't care about the GIF/display. I just want my fan settings to work so my CPU doesn't throttle. That's why I bought the Kraken!
Win 11 Pro 23H2. Intel i9-14900K. 2x32GB Corsair Vengeance 5600MHz DDR5. Asus Tuf Gaming RTX 4070Ti. MSI Z790 Gaming Plus WiFi mobo.
Same issue here on my Elite 360, very annoying to have to x out the program and restart it in order to fix the display.
Same issue, screen stays on default (liquid temp) image after sleep.
same issue. My CPU overheats because of this. WHY NZXT not reacting ?
Same here. Very dissapointing, just bought the Kraken 280 and never seen it work.
It's been happening for me as well ever since last update, been asking around forums and no one from support answers :(
Same issue ever since the last update, pls help
Identical issue here. Any solution?
+1 same exact thing
Windows 11 pro latest release
Kraken 360 Elite Firmware 2.0.11
CAM version 4.61.7
Having the same issue. Any fix/guidance would be greatly appreciated!