DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropert圜hanged Session allowed. T19:59:24 I : Dropping server starting due to disabled SDK T19:59:24 I : User session about to be unlocked. T19:59:24 I _lightings: Working state about to change, lock hw lights preview. T19:59:24 I _watcher: Finish prepare RestoreDeviceOrderState T19:59:24 I _watcher: Start prepare RestoreDeviceOrderState T19:59:24 I cue.sdk: Entering working state, session connected. T19:59:24 I cue.session: Connected changed to true T19:59:24 I cue.hw_profile.manager: Start worker thread. T19:59:23 I cue.session: Local changed to true T19:59:23 I : Will notify 'connected changed to' with delay T19:59:23 I cue.session: Locked changed to false T19:59:23 W QObject::disconnect: Unexpected null parameter T19:59:23 W cue.llaccess: "dramWriteByte failed" "" cmd: 37 data: 66 T19:59:23 I cue.llaccess: Northbridge: Intel Coffee Lake T19:59:23 I : Profile order deserialization finished: "C:\\Users\\\AppData\\Roaming\\Corsair\\CUE/profiles/tree.cueprofileorder" T19:59:23 I : Profile order deserialization started: "C:\\Users\\\AppData\\Roaming\\Corsair\\CUE/profiles/tree.cueprofileorder" T19:59:23 W cue.plugin: Processing already finished T19:59:23 I cue.plugin: Library is loading, will check if it's plugin: "CUEPlugin.dll" T19:59:23 I cue.plugin: Trying to load library: "C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/plugins/CUEPlugin.dll" DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropert圜hanged Session disallowed. T19:59:23 I cue.hid_device_detector: Start worker thread. T19:59:23 I : Using Title text font family: "Gotham Bold" T19:59:23 I : Using Regular text font family: "Open Sans" T19:59:23 W cue.locale: Cannot find dir for qt *.qm files T19:59:22 I cue.init: Build type: Public Release Anyone have any idea what is causing this? If you look at 20:34 time you'll notice a bunch of errors. After reconnecting it, the error occurred again at 20:34.
When I finally got back to my computer around 20:30, I disabled/renabled the "USB Composite Device" associated with this Commander Pro in device manager to get it reconnected to iCue. Didn't get back to my computer for about a half hour, but by the time I started using it the problem had already occurred, I believe right at the beginning 19:59:22. Am using the latest version of iCUE (3.22.74) and Commander Pros are all updated to latest firmware (0.9.212), and this same problem has occurred with all previous versions of iCue and firmware I have used.ġ5 x Corsair ML RGB Fans Edited Decemby techfiend
#COMMANDER ONE PRO ACTIVATION CODE INSTALL#
I've tried clean install of iCue and removing all folders and registry entries, no monitoring software like HWInfo is running (persistent driver is NOT enabled), even clean reinstall of Windows. The only way I can get iCue to regain control of this Commander Pro is by rebooting the computer or going to device manager and disabling then re-enabling the "USB Composite Device" associated with this Commander Pro. Was previously using LINK and never had this issue. Been having this problem ever since I started using iCue. If I check with USBDeview it shows all three Commander Pros as connected despite this one disappearing from iCue. Restarting iCue service gets rid of icon for the Commander Pro that loses connection and only the two remaining are shown. When this "disconnect" occurs and I go into iCue, the Commander Pro icon associated with the one that disconnects shows but all the fan speeds are frozen and I can't adjust any lighting settings. It seems to happen randomly where this one Commander Pro disconnects and reverts to the hardware lighting settings. One of the Commander Pros will occasionally disappear from iCue as if iCue has lost the ability to communicate with it. I have 3 Commander Pros, each with 5 Corsair ML RGB fans.
0 kommentar(er)
