Jump to content
Corsair Community

Corsair Commander Core (H150i Elite Capellix) frequently disconnecting (USB-Sound audible and RGB flashing)


Haensele
 Share

Recommended Posts

Dear Corsair Community,

you are my last chance!! Before i even start with further explanation of my problem here are my system specs: 

Lian Li  PC-O11 Dynamix
AMD Ryzen 7 5800X (8x 3.8GHz / 4.7GHz Turbo)
Corsair H150i Elite Capellix black (connected with Commancer Core) 
MSI MPG X570 Gaming Pro Carbon WiFi (inkl Wlan + BT)
32GB (2x16GB) GSkill DDR4 3600MHz Trident Z NEO
1TB Corsair MP400 M.2 PCIe 3.0 x4 NVME (L 3480MB/s ; S1880MB/s)
3TB SATA 6GB/s 5400rpm WD Blue WD30EZAZ
8GB Gigabyte RTX3070 AORUS MASTER
750W be quiet! Straight Power 11 Platinum
3x Corsair ML Series ML120 RGB, 120mm (connected with Lightning Node Pro)

It all started November this year, at that time the wasnt even a month old. And then the nightmare started. 

USB Disconnect Sound, H150i Elite Capellix disconnecting from ICUE, RGB flashing, then USB reconnect Sound, H150i showing up in ICUE again. To give u a example of how often this happens, here are 4 lines of CueLog Code from today: 

09:20:07.828 C cue.devices: Read report error 1167 -1 "Commander CORE"

09:21:13.512 C cue.devices: Read report error 1167 -1 "Commander CORE"

09:23:33.481 C cue.devices: Read report error 1167 -1 "Commander CORE"

09:29:28.400 C cue.devices: Read report error 1167 -1 "Commander CORE"

between those lines there is a lot of going on, which i dont really understand, but as you can see, Error Code 1167 ._.

This nightmare haunts me for 3-4 weeks already and im tired, im sick of it and i just want it to go away, i literally sleep bad, due to this issue. Some might wonder why im so obsessed with my system. Well if u spent 3k+ on your system, recently got it and it does not work the way you want it to, you feel bothered. And due to the problem that i work and game on that system, it makes me go crazy. 

So when the problem occurred i tried following steps already: 

I opened the case and looked it up for not-connected wires, which was not the case
I de- and reinstalled ICUE
I tried to not use ICUE 
I de- and reinstalled every RGB program
I looked up for any Monitoring software (HWINFO) which may causes the problems, but i dont use any of them listed. I have HWINFO but its not in daily use
I deactivated the selective USB energie saving in the Device Manager
I deactivated the Energy saving for every USB Device in Human Interface Devices 
I switched the PCI Gen from auto to Gen3 
I updated the BIOS and tried the PCI switch again 
I updated the AMD Chipset driver
I went into all RGB programs and forced them to not overwrite any other RGB program like ICUE. Then i went into ICUE and blocked the application LED Keeper. Then i removed every other RGB program from autostart except for ICUE. Because i actually only want to use ICUE and updated ICUE today. 
And yes i installed ALL the latest driver, for chipsets and so on. Also updated BIOS to the latest NON-Beta version. I did it all

And yes i thought about installing a NZXT Hub, but my case does not give me the room to actual install it. Sadly... so i have to get a workaround somehow...

After those tries i contacted the Corsair Support. Which they replied me with a large number of software, which could conflict with ICUE. So i deinstalled ALL of them and reinstalled ICUE. As you can imagine the problem was still there. Then i replied them again and they wanted to see my log files and systeminfo, which i provided towards them. After waiting approximately a week they replied me with another software which i have to deinstall. Deinstalled it and problem is still there. They also wanted me to update a software which i did not even have on my PC, because i deinstalled it already due to their list, so ye.. idk bout that. 

I replied them with new Logs and a new system info.. and now im waiting again 

The only thing that kinda worked for me, for atleast 3-4 days without perma disconnects, was to switch the USB 2.0 Header on my Mainboard. This helped for some time but now it came back and im freaking out once again. 

I can also deinstall Roccat SWARM for my peripherals. Aswell as Riot Vanguard for Valorant. But come on, do i really have to use nothing except for Windows Solitair game and use this system.. 

Long story short, does anyone have a solution for me. I can provide u with any sort of information u need and if u can help me ill promise u will get something from me, because i cant do this anymore. Im feeling lost due to the fact that even Corsair cant really help me.. 

Thank You for your attention and maybe u can help me.

Cheers...

Link to comment
Share on other sites

I'm having the exact same issues I build my system back in August which cost me around £3000 plus and round about October when playing games it makes a disconnect sound and the lights flash off then back on randomly and I'm not sure what the issue is

Edited by R6Liam
Link to comment
Share on other sites

26 minutes ago, R6Liam said:

I'm having the exact same issues I build my system back in August which cost me around £3000 plus and round about October when playing games it makes a disconnect sound and the lights flash off then back on randomly and I'm not sure what the issue is

Well, i still found no solution to my problem but setting PCIe from Auto or 4.0 to 3.0 does minimize the disconnects (1-2 daily). But they are still there. It is a common issue on X570 and equal Mainboards and AMD systems. 

Im looking forward to an answer from Corsair, since its pretty annoying and does not stop. 

Did you try everything i've listed on my previous post? 

Cheers

Link to comment
Share on other sites

On 12/15/2021 at 9:14 PM, Haensele said:

Well, i still found no solution to my problem but setting PCIe from Auto or 4.0 to 3.0 does minimize the disconnects (1-2 daily). But they are still there. It is a common issue on X570 and equal Mainboards and AMD systems. 

Im looking forward to an answer from Corsair, since its pretty annoying and does not stop. 

Did you try everything i've listed on my previous post? 

Cheers

So my disconnects have minimized significantly since I changed the PCIe setting from 4.0 to 3.0. However, they are still there. Does anyone have an idea what this could be? The starting point for these disconnects are the following log entries (I got these via the ICUE export):

2021-12-17 14:56:05.774 C cue.devices: Read report error 1167 -1 "Commander CORE"
2021-12-17 14:56:05.774 W cue.devices: Failed to free subdevice "Commander CORE"
2021-12-17 14:56:05.774 W cue.devices:  Set property OperatingMode failed.
  Error while sending command. Platform error code: 1167. Bytes transmitted: 0.

2021-12-17 14:56:05.774 W QObject::connect(AbstractProtocol, bragi::LogicalSubdevice): invalid nullptr parameter

 

Then a new log file is created and starts as following: 

2021-12-17 14:56:05.775 W QObject::connect(AbstractProtocol, bragi::LogicalSubdevice): invalid nullptr parameter
2021-12-17 14:56:05.775 C cue.devices: Trying to remove main subdevice for "Commander CORE"

And then there are a bunch of other Log entries...

 

Is there any Corsair Employee @Corsair Notepad that may have dealt with a similar issue already. Im LOST

Cheers

Edited by Haensele
Link to comment
Share on other sites

Im having the same sort of issues with my H150i Elite Capellix.

 

- Random windows disconnect sounds

- RGB turning on and off

- Error messages in CueLogs (see attachment)

 

Not sure what to do here, tried lots of things already including the things noted above by other people.

 

---------------------------------------------------------------------

 

2021-12-19 17:54:21.336 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:31.340 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:31.340 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:31.340 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:33.336 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:33.336 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:33.336 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 18:24:13.303 C cue.devices: Read report error 1167 -1 "Commander CORE"
2021-12-19 18:24:13.303 W cue.devices: Failed to free subdevice "Commander CORE"
2021-12-19 18:24:13.304 W cue.devices:  Set property OperatingMode failed.
  Error while sending command. Platform error code: 1167. Bytes transmitted: 0.

2021-12-19 18:24:13.304 W QObject::connect(AbstractProtocol, bragi::LogicalSubdevice): invalid nullptr parameter
2021-12-19 18:24:13.304 W QObject::connect(AbstractProtocol, bragi::LogicalSubdevice): invalid nullptr parameter
2021-12-19 18:24:13.304 C cue.devices: Trying to remove main subdevice for "Commander CORE"
2021-12-19 18:24:13.305 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.306 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.306 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.307 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.
2021-12-19 18:24:13.307 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.
2021-12-19 18:24:13.307 I cue.hid_device_detector: Mark all tasks as finished.
2021-12-19 18:24:13.344 I cue.lightings.direct_player: Stopped lighting worker in 0xb4c
2021-12-19 18:24:13.346 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.346 I cue.hid_report_worker: Waiting for report worker stop "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.346 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "Commander CORE"
2021-12-19 18:24:13.347 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.347 I cue.hid_report_worker: Waiting for report worker stop "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:14.079 I cue.dev.hidenumerator: Found device VID 3314 PID 41216 Usage Page 65394 Usage 161
2021-12-19 18:24:14.080 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_0cf2&pid_a100&mi_01\\b&15cbc72d&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "161")("hid-usagepage", "65394")("model-name", "LianLi-UNI FAN-SL-v1.1 \xCC\x96")("usb-pid", "41216")("usb-vid", "3314")("vendor", "ENE"))  not found.
2021-12-19 18:24:14.081 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_0cf2&pid_a100&mi_01\\b&15cbc72d&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "161")("hid-usagepage", "65394")("model-name", "LianLi-UNI FAN-SL-v1.1 \xCC\x96")("usb-pid", "41216")("usb-vid", "3314")("vendor", "ENE"))  not found.
2021-12-19 18:24:14.081 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_0cf2&pid_a100&mi_01\\b&15cbc72d&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "161")("hid-usagepage", "65394")("model-name", "LianLi-UNI FAN-SL-v1.1 \xCC\x96")("usb-pid", "41216")("usb-vid", "3314")("vendor", "ENE"))  not found.
2021-12-19 18:24:14.081 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_0cf2&pid_a100&mi_01\\b&15cbc72d&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "161")("hid-usagepage", "65394")("model-name", "LianLi-UNI FAN-SL-v1.1 \xCC\x96")("usb-pid", "41216")("usb-vid", "3314")("vendor", "ENE"))  not found.
2021-12-19 18:24:14.081 I cue.devices: Manifest for device "(vid=cf2, pid=a100)" not found.
2021-12-19 18:24:14.090 I cue.dev.hidenumerator: Found device VID 6940 PID 3100 Usage Page 65346 Usage 1
2021-12-19 18:24:14.090 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.091 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.091 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.091 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.091 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.091 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.091 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.091 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.092 I cue.dev.hidenumerator: Found device VID 6940 PID 3100 Usage Page 65346 Usage 2
2021-12-19 18:24:14.093 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_01\\b&3826d331&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.093 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_01\\b&3826d331&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.093 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_01\\b&3826d331&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.093 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_01\\b&3826d331&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.093 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_0C1C\\B00210603C4E26BA80C120E55091005F\u0000") inserted.
2021-12-19 18:24:14.093 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms.
2021-12-19 18:24:14.093 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_0c1c&mi_01\\b&3826d331&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_0C1C\\B00210603C4E26BA80C120E55091005F\u0000") inserted.
2021-12-19 18:24:14.093 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms.
2021-12-19 18:24:14.094 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened.
2021-12-19 18:24:14.094 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened.
2021-12-19 18:24:14.094 I cue.hid_device_detector: Mark all tasks as finished.
2021-12-19 18:24:14.094 I cue.devices: Begin attaching to "Commander CORE" "(vid=1b1c, pid=c1c)" "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2021-12-19 18:24:14.094 I cue.devices: End attaching to "Commander CORE" "(vid=1b1c, pid=c1c)" "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1
2021-12-19 18:24:14.094 I cue.devices: Created new device"Commander CORE" "(vid=1b1c, pid=c1c)"; ready:true
2021-12-19 18:24:14.094 I cue.devices: Begin attaching to "Commander CORE" "(vid=1b1c, pid=c1c)" "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 1
2021-12-19 18:24:14.094 I cue.devices: End attaching to "Commander CORE" "(vid=1b1c, pid=c1c)" "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1
2021-12-19 18:24:14.095 I cue.devices: Initializing "Commander CORE" "(vid=1b1c, pid=c1c)"
2021-12-19 18:24:14.096 I cue.devices: Initialized true "Commander CORE" "(vid=1b1c, pid=c1c)"
2021-12-19 18:24:14.096 I cue.devices.enum.subdevice: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed.
2021-12-19 18:24:14.099 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "Commander CORE"
2021-12-19 18:24:14.110 W cue.bragi.command: Cannot get `MaximumPollingRate` from "Commander CORE"
2021-12-19 18:24:14.128 I cue.devices: "Commander CORE" initial exceptional state - "Normal"
2021-12-19 18:24:14.130 I cue.devices: "Commander CORE" Cooler Component:
 product line id - 1 
 product vendor id - 1 
 pump version id - 1 
 radiator size - 360
2021-12-19 18:24:14.130 I cue.devices: "Commander CORE" cooler component - "h150iPro"
2021-12-19 18:24:14.131 I cue.devices: "Commander CORE" Led Module:
 product line id - 1 
 vendor id - 1 
 version id - 1
2021-12-19 18:24:14.131 I cue.devices: "Commander CORE" led module - "CoolerPump21Leds"
2021-12-19 18:24:15.132 C cue.devices: Read chunk failed. Device: "Commander CORE"
2021-12-19 18:24:15.132 C cue.devices: Exception:  Command processing error: HardwareError.

2021-12-19 18:24:15.132 W cue.devices: Failed to LedModule SerialNumber "Commander CORE"
2021-12-19 18:24:15.132 W cue.devices:  Invalid report buffer. Read failed.

2021-12-19 18:24:15.132 I cue.devices: "Commander CORE" led module SN - ""
2021-12-19 18:24:15.135 I cue.devices.enum.router: Router created "Commander CORE"
2021-12-19 18:24:15.147 I cue.dev.mgr: Candidate device for QMap(("bus", "legacy")("usb-mid", "16842753")("usb-pid", "3100")("usb-vid", "6940"))  not found.
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  61
2021-12-19 18:24:15.147 W cue.dev.control.brightness_value: Get dpi brightness level failure
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  73
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  170
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  223
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  224
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  225
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  226
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  227
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  228
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  220
2021-12-19 18:24:15.147 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-mid", "16842753")("usb-pid", "3100")("usb-vid", "6940"))
2021-12-19 18:24:15.148 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "3100")("usb-vid", "6940"))
2021-12-19 18:24:15.148 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "3100")("usb-vid", "6940"))
2021-12-19 18:24:15.148 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "3101")("usb-vid", "6940"))
2021-12-19 18:24:15.148 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "3101")("usb-vid", "6940"))

 

Edited by Kwiepz
Link to comment
Share on other sites

6 minutes ago, Kwiepz said:

Im having the same sort of issues with my H150i Elite Capellix.

 

- Random windows disconnect sounds

- RGB turning on and off

- Error messages in CueLogs (see attachment)

 

Not sure what to do here, tried lots of things already including the things noted above by other people.

 

---------------------------------------------------------------------

 

2021-12-19 17:54:21.336 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:31.340 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:31.340 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:31.340 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:33.336 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:33.336 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 17:54:33.336 W cue.dev.bragi.feature.sensors: Failed to get sensor controller
2021-12-19 18:24:13.303 C cue.devices: Read report error 1167 -1 "Commander CORE"
2021-12-19 18:24:13.303 W cue.devices: Failed to free subdevice "Commander CORE"
2021-12-19 18:24:13.304 W cue.devices:  Set property OperatingMode failed.
  Error while sending command. Platform error code: 1167. Bytes transmitted: 0.

2021-12-19 18:24:13.304 W QObject::connect(AbstractProtocol, bragi::LogicalSubdevice): invalid nullptr parameter
2021-12-19 18:24:13.304 W QObject::connect(AbstractProtocol, bragi::LogicalSubdevice): invalid nullptr parameter
2021-12-19 18:24:13.304 C cue.devices: Trying to remove main subdevice for "Commander CORE"
2021-12-19 18:24:13.305 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.306 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.306 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.307 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.
2021-12-19 18:24:13.307 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.
2021-12-19 18:24:13.307 I cue.hid_device_detector: Mark all tasks as finished.
2021-12-19 18:24:13.344 I cue.lightings.direct_player: Stopped lighting worker in 0xb4c
2021-12-19 18:24:13.346 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.346 I cue.hid_report_worker: Waiting for report worker stop "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.346 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "Commander CORE"
2021-12-19 18:24:13.347 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:13.347 I cue.hid_report_worker: Waiting for report worker stop "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 18:24:14.079 I cue.dev.hidenumerator: Found device VID 3314 PID 41216 Usage Page 65394 Usage 161
2021-12-19 18:24:14.080 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_0cf2&pid_a100&mi_01\\b&15cbc72d&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "161")("hid-usagepage", "65394")("model-name", "LianLi-UNI FAN-SL-v1.1 \xCC\x96")("usb-pid", "41216")("usb-vid", "3314")("vendor", "ENE"))  not found.
2021-12-19 18:24:14.081 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_0cf2&pid_a100&mi_01\\b&15cbc72d&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "161")("hid-usagepage", "65394")("model-name", "LianLi-UNI FAN-SL-v1.1 \xCC\x96")("usb-pid", "41216")("usb-vid", "3314")("vendor", "ENE"))  not found.
2021-12-19 18:24:14.081 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_0cf2&pid_a100&mi_01\\b&15cbc72d&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "161")("hid-usagepage", "65394")("model-name", "LianLi-UNI FAN-SL-v1.1 \xCC\x96")("usb-pid", "41216")("usb-vid", "3314")("vendor", "ENE"))  not found.
2021-12-19 18:24:14.081 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_0cf2&pid_a100&mi_01\\b&15cbc72d&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "161")("hid-usagepage", "65394")("model-name", "LianLi-UNI FAN-SL-v1.1 \xCC\x96")("usb-pid", "41216")("usb-vid", "3314")("vendor", "ENE"))  not found.
2021-12-19 18:24:14.081 I cue.devices: Manifest for device "(vid=cf2, pid=a100)" not found.
2021-12-19 18:24:14.090 I cue.dev.hidenumerator: Found device VID 6940 PID 3100 Usage Page 65346 Usage 1
2021-12-19 18:24:14.090 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.091 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.091 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.091 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.091 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.091 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.091 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.091 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.092 I cue.dev.hidenumerator: Found device VID 6940 PID 3100 Usage Page 65346 Usage 2
2021-12-19 18:24:14.093 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_01\\b&3826d331&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.093 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_01\\b&3826d331&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.093 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_01\\b&3826d331&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2021-12-19 18:24:14.093 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_0c1c&mi_01\\b&3826d331&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR iCUE Commander CORE")("usb-pid", "3100")("usb-vid", "6940")("vendor", "Corsair"))
2021-12-19 18:24:14.093 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_0c1c&mi_00\\b&24f6b6f3&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_0C1C\\B00210603C4E26BA80C120E55091005F\u0000") inserted.
2021-12-19 18:24:14.093 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms.
2021-12-19 18:24:14.093 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_0c1c&mi_01\\b&3826d331&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_0C1C\\B00210603C4E26BA80C120E55091005F\u0000") inserted.
2021-12-19 18:24:14.093 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms.
2021-12-19 18:24:14.094 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened.
2021-12-19 18:24:14.094 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened.
2021-12-19 18:24:14.094 I cue.hid_device_detector: Mark all tasks as finished.
2021-12-19 18:24:14.094 I cue.devices: Begin attaching to "Commander CORE" "(vid=1b1c, pid=c1c)" "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2021-12-19 18:24:14.094 I cue.devices: End attaching to "Commander CORE" "(vid=1b1c, pid=c1c)" "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&24f6b6f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1
2021-12-19 18:24:14.094 I cue.devices: Created new device"Commander CORE" "(vid=1b1c, pid=c1c)"; ready:true
2021-12-19 18:24:14.094 I cue.devices: Begin attaching to "Commander CORE" "(vid=1b1c, pid=c1c)" "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 1
2021-12-19 18:24:14.094 I cue.devices: End attaching to "Commander CORE" "(vid=1b1c, pid=c1c)" "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&3826d331&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1
2021-12-19 18:24:14.095 I cue.devices: Initializing "Commander CORE" "(vid=1b1c, pid=c1c)"
2021-12-19 18:24:14.096 I cue.devices: Initialized true "Commander CORE" "(vid=1b1c, pid=c1c)"
2021-12-19 18:24:14.096 I cue.devices.enum.subdevice: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed.
2021-12-19 18:24:14.099 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "Commander CORE"
2021-12-19 18:24:14.110 W cue.bragi.command: Cannot get `MaximumPollingRate` from "Commander CORE"
2021-12-19 18:24:14.128 I cue.devices: "Commander CORE" initial exceptional state - "Normal"
2021-12-19 18:24:14.130 I cue.devices: "Commander CORE" Cooler Component:
 product line id - 1 
 product vendor id - 1 
 pump version id - 1 
 radiator size - 360
2021-12-19 18:24:14.130 I cue.devices: "Commander CORE" cooler component - "h150iPro"
2021-12-19 18:24:14.131 I cue.devices: "Commander CORE" Led Module:
 product line id - 1 
 vendor id - 1 
 version id - 1
2021-12-19 18:24:14.131 I cue.devices: "Commander CORE" led module - "CoolerPump21Leds"
2021-12-19 18:24:15.132 C cue.devices: Read chunk failed. Device: "Commander CORE"
2021-12-19 18:24:15.132 C cue.devices: Exception:  Command processing error: HardwareError.

2021-12-19 18:24:15.132 W cue.devices: Failed to LedModule SerialNumber "Commander CORE"
2021-12-19 18:24:15.132 W cue.devices:  Invalid report buffer. Read failed.

2021-12-19 18:24:15.132 I cue.devices: "Commander CORE" led module SN - ""
2021-12-19 18:24:15.135 I cue.devices.enum.router: Router created "Commander CORE"
2021-12-19 18:24:15.147 I cue.dev.mgr: Candidate device for QMap(("bus", "legacy")("usb-mid", "16842753")("usb-pid", "3100")("usb-vid", "6940"))  not found.
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  61
2021-12-19 18:24:15.147 W cue.dev.control.brightness_value: Get dpi brightness level failure
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  73
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  170
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  223
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  224
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  225
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  226
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  227
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  228
2021-12-19 18:24:15.147 W Unimplemented conversion for command:  220
2021-12-19 18:24:15.147 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-mid", "16842753")("usb-pid", "3100")("usb-vid", "6940"))
2021-12-19 18:24:15.148 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "3100")("usb-vid", "6940"))
2021-12-19 18:24:15.148 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "3100")("usb-vid", "6940"))
2021-12-19 18:24:15.148 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "3101")("usb-vid", "6940"))
2021-12-19 18:24:15.148 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "3101")("usb-vid", "6940"))

 

I have almost the same ICue logs as well. There are a few differences. But it all starts with the ErrorCode 1167

2021-12-19 20:07:52.635 C cue.devices: Read report error 1167 -1 "Commander CORE"
2021-12-19 20:07:52.635 W cue.devices: Failed to free subdevice "Commander CORE"
2021-12-19 20:07:52.635 W cue.devices:  Set property OperatingMode failed.
  Error while sending command. Platform error code: 1167. Bytes transmitted: 0.

2021-12-19 20:07:52.635 W QObject::connect(AbstractProtocol, bragi::LogicalSubdevice): invalid nullptr parameter
2021-12-19 20:07:52.636 W QObject::connect(AbstractProtocol, bragi::LogicalSubdevice): invalid nullptr parameter
2021-12-19 20:07:52.636 C cue.devices: Trying to remove main subdevice for "Commander CORE"
2021-12-19 20:07:52.637 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&41f8cf6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 20:07:52.638 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&41f8cf6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 20:07:52.638 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&35dff8b7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2021-12-19 20:07:52.639 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_00#b&41f8cf6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.
2021-12-19 20:07:52.640 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0c1c&mi_01#b&35dff8b7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.
2021-12-19 20:07:52.640 I cue.hid_device_detector: Mark all tasks as finished.

And so on... 

2021-12-19 20:07:54.246 I cue.firmware.index: "Commander CORE" no newer FW version was found, selecting package with maximal verion

It also cant be the firmware for the Commander Core, because as the Logs say, there is no newer firmware

And so it goes on and on: 

2021-12-19 20:10:13.931 C cue.devices: Read report error 1167 -1 "Commander CORE"
2021-12-19 20:10:13.932 W cue.devices: Failed to free subdevice "Commander CORE"
2021-12-19 20:10:13.932 W cue.devices:  Set property OperatingMode failed.
  Error while sending command. Platform error code: 1167. Bytes transmitted: 0.

and on 

2021-12-19 20:11:13.220 C cue.devices: Read report error 1167 -1 "Commander CORE"
2021-12-19 20:11:13.220 W cue.devices: Failed to free subdevice "Commander CORE"
2021-12-19 20:11:13.220 W cue.devices:  Set property OperatingMode failed.
  Error while sending command. Platform error code: 1167. Bytes transmitted: 0.

and on 

2021-12-19 20:12:23.512 C cue.devices: Read report error 1167 -1 "Commander CORE"
2021-12-19 20:12:23.512 W cue.devices: Failed to free subdevice "Commander CORE"
2021-12-19 20:12:23.512 W cue.devices:  Set property OperatingMode failed.
  Error while sending command. Platform error code: 1167. Bytes transmitted: 0.

 

So as you can see, it happened 4 TIMES in 5 MIN. 

This makes using the computer exhausting and by now I just don't enjoy it anymore. Neither the attempt to fix the bug, nor to use the PC. I've been struggling with this problem for 1.5 months now and I simply don't have the space for a NZXT hub. There has to be another solution, by now. Because the problem exists for now more than a year or maybe even 2. 

 

Im still waiting, hoping for some good news. But atleast I know that im not alone with this case. 

 

Cheers 

Link to comment
Share on other sites

@Corsair Notepad I am about to give up, I already wrote to your support 3 weeks ago asking for help. After several days of email traffic they sent me a few suggested solutions. However, all without success. Today I receive the email that even in the logs no further problems are to be recognized and even the support cannot help me. What the hell should I do to finally be able to use my computer in peace? 

Link to comment
Share on other sites

Its pretty pathetic that corsair is not even responding to their own forum page..

 

Ive already changed 9 QL corsair fans this week for another brand which doesnt have issue with the LED..

im almost at a point to get rid of the h150 capellix and never go corsair again..

Link to comment
Share on other sites

On 12/22/2021 at 6:55 PM, Kwiepz said:

Its pretty pathetic that corsair is not even responding to their own forum page..

 

Ive already changed 9 QL corsair fans this week for another brand which doesnt have issue with the LED..

im almost at a point to get rid of the h150 capellix and never go corsair again..

So I finally solved the problem, at least I hope so. After I installed the internal USB 2.0 hub, I haven't had any problems with disconnects. 
I have opened several other posts besides this one and I was helped by Corsair Support from Germany, who themselves had the same problem with several AMD systems. 

I will now summarize the whole thing again and try to help the others who suffer from this problem. 

The problem with the constant disconnects of the water cooling under AMD systems exists for quite a while, but this is always in connection with the following boards (X570 / X470). The problem is much broader than Corsair alone could solve, because Corsair, as well as the motherboard manufacturers, as well as the chip manufacturers (AMD) would have to cooperate. 
Because the problem is caused by the "too weak" connection strength of the USB 2.0 headers to which the hubs are connected. 

Thus, there are the following workarounds: 
- Install an internal USB 2.0 hub. I can warmly recommend the NZXT hub (NZXT Hub), the installation is super easy and for me it has eliminated the problem.

If the hub does not solve the problem, you can still resort to a more unsightly and impractical solution. However, this requires a cable outside the computer into the computer. Here you could buy such an adapter Adapter .

 

I hope i can help someone with this solution. And actually, I have to take Corsair's side a bit in this case, since the effort to fix the error is more far-reaching than I would like to imagine.

Cheers 

Link to comment
Share on other sites

On 12/27/2021 at 12:54 AM, Haensele said:

So I finally solved the problem, at least I hope so. After I installed the internal USB 2.0 hub, I haven't had any problems with disconnects. 
I have opened several other posts besides this one and I was helped by Corsair Support from Germany, who themselves had the same problem with several AMD systems. 

I will now summarize the whole thing again and try to help the others who suffer from this problem. 

The problem with the constant disconnects of the water cooling under AMD systems exists for quite a while, but this is always in connection with the following boards (X570 / X470). The problem is much broader than Corsair alone could solve, because Corsair, as well as the motherboard manufacturers, as well as the chip manufacturers (AMD) would have to cooperate. 
Because the problem is caused by the "too weak" connection strength of the USB 2.0 headers to which the hubs are connected. 

Thus, there are the following workarounds: 
- Install an internal USB 2.0 hub. I can warmly recommend the NZXT hub (NZXT Hub), the installation is super easy and for me it has eliminated the problem.

If the hub does not solve the problem, you can still resort to a more unsightly and impractical solution. However, this requires a cable outside the computer into the computer. Here you could buy such an adapter Adapter .

 

I hope i can help someone with this solution. And actually, I have to take Corsair's side a bit in this case, since the effort to fix the error is more far-reaching than I would like to imagine.

Cheers 

Well, it worked fine for 1 week and some days and guess what, it came back. 

So that wasnt the solution to fix the nightmare and im lost once again. Now the disconnects use to happen 5 times every min, so the system is not usable for me. 

 

PLEASE provide us with any help

Link to comment
Share on other sites

I might just try that, i have an NZXT hub somewere hidden in a box 😄

Maybe it helps me.. ill check in a couple of days.

 

Or i might just buy another brand of cooling.. 

So done with corsair.. even my brand new fans broke down twice now.. so switches to lian li 🙂

Edited by Kwiepz
Link to comment
Share on other sites

On 1/1/2022 at 9:40 AM, Kwiepz said:

I might just try that, i have an NZXT hub somewere hidden in a box 😄

Maybe it helps me.. ill check in a couple of days.

 

Or i might just buy another brand of cooling.. 

So done with corsair.. even my brand new fans broke down twice now.. so switches to lian li 🙂

Im still having disconnects. It only helped for a couple of days, now they are coming back, i have no clue what the problem could be. Maybe my Commander Core just has loose contact or so. 

I also updated my BIOS to the recent version, 

Link to comment
Share on other sites

  • 3 weeks later...

hi everyone, i also have the same problem, the commander of the aio keeps disconnecting, it has been fine for about 2 weeks and now it starts to give problems. I have an intel i5 12600 and an asus z690. i tried to unmount the commander clean it, look at the links on the mobo, but nothing. I am waiting for a response from corsair support

Link to comment
Share on other sites

1 hour ago, JACOPOTTE said:

hi everyone, i also have the same problem, the commander of the aio keeps disconnecting, it has been fine for about 2 weeks and now it starts to give problems. I have an intel i5 12600 and an asus z690. i tried to unmount the commander clean it, look at the links on the mobo, but nothing. I am waiting for a response from corsair support

As far as i know is that the Corsair Support cant really help you in this case. This problem is a ongoing thing for quite some time now and it is an interaction of the USB controller of the motherboards, the installed chipset and the Commander Core. Most likely, the Commander Core needs a higher bandwidth via the USB bus, which it doesn't get permanently and then frequently disconnects. 
There are several methods to work around this power problem, these solutions do not guarantee anything. Also for me so far 2 of the 3 solutions did not work. The third one will be tested this weekend. 

The first workaround would be an internal NZXT hub. This involves running a cable from this hub to the motherboard internal USB 2.0 header and connecting the Commander Core to the NZXT hub. Power is supplied via a SATA cable to the power supply. This worked for some people but in my case it didnt. 

The second workaround is to buy this Adapter from amazon. You have to plug it into the Back IO of your computer and lay the cable from the outside of your case to the inside. Then u plug the Commander Core into one of the remaining USB 2.0 Headers of the Adapter and the second USB 2.0 Header will be connected to your motherboard. This solution worked fine for 2 weeks or so. But now its not working for me again. 

I also looked up my whole USB Tree via USBTreeView, with this Tool u can check if any controller of your System is constantly under high load and could cause the USB Bus to be overloaded and shutting down some USB devices. Maybe you could try that tool and see if any USB Controller has too many USB devices plugged into it. 

The third solution that will be tested this weekend is to buy this PCI Express USB card and one of those cables. Then you just plug the PCIE card into your mainboard, plug the commander core with the cable into the card and Windows gets every driver and also ICUE and other devices should detect the Commander Core. This workaround was provided by @Corsair Marcus lets see how this will work. He also had various problems and is testing a lot of workarounds until the solution will be fixed. Corsair is aware of this problem and is propably already reaching out to the Mainboard and CPU distributor, but this process may take up some time. 

 

If your interesting in trying one or two of these solutions, let me know if any of those worked for you

Cheers Hänsele

Link to comment
Share on other sites

Forse ho risolto, l'assistenza corsair mi ha fatto scollegare e ricollegare i cavi dell'hub , poi ho disinstallato tramite una disinstallazione pulita (consigliata dall'assistenza) icue4 e da quando l'ho rinstallato non ho più disconnessioni, sono passati circa 4 giorni. Vi aggiorno se cambia qualcosa

Link to comment
Share on other sites

  • 1 month later...

FYI to all.  This is caused by the iCue software.  Uninstall it and it stops having problems.  Apparently Corsair made a mistake with an update and have not yet fixed it.  However, according to previous posts this has been happening since version 2.6 and we are on version 4.21.173.  I guess we need to stop buying Corsair products to send a message.  Food for thought.  Good luck.

Link to comment
Share on other sites

8 hours ago, CPAGamer said:

FYI to all.  This is caused by the iCue software.  Uninstall it and it stops having problems.  Apparently Corsair made a mistake with an update and have not yet fixed it.  However, according to previous posts this has been happening since version 2.6 and we are on version 4.21.173.  I guess we need to stop buying Corsair products to send a message.  Food for thought.  Good luck.

Thats not true, i fixed it with the PCIe card. Its caused by the USB Controller like I mentioned above 

On 1/28/2022 at 12:18 PM, Haensele said:

As far as i know is that the Corsair Support cant really help you in this case. This problem is a ongoing thing for quite some time now and it is an interaction of the USB controller of the motherboards, the installed chipset and the Commander Core. Most likely, the Commander Core needs a higher bandwidth via the USB bus, which it doesn't get permanently and then frequently disconnects. 
There are several methods to work around this power problem, these solutions do not guarantee anything. Also for me so far 2 of the 3 solutions did not work. The third one will be tested this weekend. 

The first workaround would be an internal NZXT hub. This involves running a cable from this hub to the motherboard internal USB 2.0 header and connecting the Commander Core to the NZXT hub. Power is supplied via a SATA cable to the power supply. This worked for some people but in my case it didnt. 

The second workaround is to buy this Adapter from amazon. You have to plug it into the Back IO of your computer and lay the cable from the outside of your case to the inside. Then u plug the Commander Core into one of the remaining USB 2.0 Headers of the Adapter and the second USB 2.0 Header will be connected to your motherboard. This solution worked fine for 2 weeks or so. But now its not working for me again. 

I also looked up my whole USB Tree via USBTreeView, with this Tool u can check if any controller of your System is constantly under high load and could cause the USB Bus to be overloaded and shutting down some USB devices. Maybe you could try that tool and see if any USB Controller has too many USB devices plugged into it. 

The third solution that will be tested this weekend is to buy this PCI Express USB card and one of those cables. Then you just plug the PCIE card into your mainboard, plug the commander core with the cable into the card and Windows gets every driver and also ICUE and other devices should detect the Commander Core. This workaround was provided by @Corsair Marcus lets see how this will work. He also had various problems and is testing a lot of workarounds until the solution will be fixed. Corsair is aware of this problem and is propably already reaching out to the Mainboard and CPU distributor, but this process may take up some time. 

 

If your interesting in trying one or two of these solutions, let me know if any of those worked for you

Cheers Hänsele

Because if this would be a software issue, then everyone would have the same problems. But for some with an Intel CPU this problem does not occur. For some others with AMD it does, so ye. I rather think its caused by the chipset drivers, BIOS and so on.

 

Cheers

Link to comment
Share on other sites

  • 5 weeks later...

Hello I found the problem, for the guy who said a usb hub would be enough, you're wrong! I have a loose contact, it's the cable from the SATA cable to the Commander Pro directly on the Commander! I have now fixed the cable a bit because in my opinion it moves slightly due to the temperature differences and thus causes a short power failure which of course also de-energizes the USB cable on the Commander and produces the disconnect sound.I have already informed Corsair about this as I fear it could be a manufacturing error

Link to comment
Share on other sites

  • 1 month later...

I Think I found the solution well atleast it's worked for me anyway so normally I would play with a xbox one elite controller and it would make the usb disconnect sound and my pump would flash off then back on again but I changed to a ps5 controller and it got worse my ps5 controller would suddenly stop working in games then start working again so I what I did was I went into my bios settings and restore to optimised factory settings and I also undervolt the cpu (depending which cpu you have go on YouTube and someone might have the settings for yours) and iv been playing games for a week now and not one single usb disconnect it's fixed the problem I'm not sure if just restoring to optimised settings in your bios fixes this or if you need to undervolt the cpu as well but I would try with just restoring to optimised settings first then if that doesn't work try undervolting your cpu and i when I first built my pc I did all these settings to start with and never had any problems but the problems came after I updated my bios at a later date and I never went back into the bios to re do the undervolt or restore to optimised settings so it kind of makes sense to why it started doing it.

Link to comment
Share on other sites

Amoury Crate and icue have a difficult relationship. To avoid conflicts, try going into services.msc, find the Amoury Crate entry, and set it to delay start. This allows icue to load first and grab the icue hardware first.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...