Jump to content
Corsair Community

iCUE constantly crashing


Recommended Posts

Hello,

This seems to be a common issue with the Command Core, so I am hoping there are some solutions.

I have already tried resetting my Command Core, as per this page: https://help.corsair.com/hc/en-us/articles/360057712532-Commander-Pro-How-to-Perform-a-factory-reset-on-the-Commander-Pro?_ga=2.93408474.672843042.1710461391-1128162814.1705018010&_gl=1*hescp3*_gcl_au*OTQwMDkxMzMxLjE3MDUwMTgwMDk.

Corsair Products (all 6 fans are connected to one Command Core):

  • Corsair iCUE H100i Elite CAPELLIX XT Liquid CPU Cooler - Two AF120 RGB Elite Fans - 240mm Radiator - Intel® LGA 1700, 1200, 115X, 2066, AMD® AM5, AM4 - Included iCUE Commander CORE - Black
  • Corsair iCUE AF120 RGB Elite 120mm PWM Fan - Eight RGB LEDs - AirGuide Technology - Fluid Dynamic Bearing - Zero RPM Fan Mode - CORSAIR iCUE Software Compatible - Black For Desktop
  • Corsair iCUE 4000D RGB Mid-Tower Case - 3X AF120 RGB Elite Fans - Lighting Node PRO Controller - High-Airflow Design - RapidRoute Cable Management System - Black
  • Corsair M75 AIR Wireless Ultra Lightweight Gaming Mouse - 2.4GHz & Bluetooth - 26,000 DPI - Up to 100hrs Battery - iCUE Compatible - Black

 

Some of Err log...

2024-03-14 19:37:47.144 W cue.plugin: 19:37:47.144 [ 44 ] Failed initialization of MysticLight_SDK "MSI/CueMsiPlugin.dll"
2024-03-14 19:37:50.153 C cue.mod.bragi.subdevice: Write hunk failed. Device: "Commander CORE(id:0)"
2024-03-14 19:37:50.153 C cue.mod.bragi.subdevice: Exception:  Timeout (100ms) while sending command.

2024-03-14 19:37:50.153 C cue.mod.bragi.protocol: Exception while runCommand on device Commander CORE: 
  Timeout (100ms) while sending command.

2024-03-14 19:37:50.180 C cue.mod.bragi.subdevice: Write hunk failed. Device: "Commander CORE(id:0)"
2024-03-14 19:37:50.180 C cue.mod.bragi.subdevice: Exception:  Command processing error: InvalidState.

2024-03-14 19:37:50.180 W cue.devices: Write lighting frame buffer failed. InvalidState or InvalidDeviceAddress.  Trying to reopen file. "Commander CORE(id:0)"
2024-03-14 19:37:50.180 I cue.mod.bragi.backlight: Write lighting frame buffer failed. Device: "Commander CORE(id:0)"
2024-03-14 19:37:50.180 I cue.mod.bragi.backlight:  Command processing error: InvalidState.

2024-03-14 19:37:53.336 C cue.mod.bragi.subdevice: Write hunk failed. Device: "Commander CORE(id:0)"
2024-03-14 19:37:53.336 C cue.mod.bragi.subdevice: Exception:  Timeout (100ms) while sending command.

2024-03-14 19:37:53.336 C cue.mod.bragi.protocol: Exception while runCommand on device Commander CORE: 
  Timeout (100ms) while sending command.

2024-03-14 19:37:53.549 C cue.mod.bragi.subdevice: Write hunk failed. Device: "Commander CORE(id:0)"
2024-03-14 19:37:53.549 C cue.mod.bragi.subdevice: Exception:  Timeout (100ms) while sending command.

2024-03-14 19:37:53.549 C cue.mod.bragi.protocol: Exception while runCommand on device Commander CORE: 
  Timeout (100ms) while sending command.

 

--------

 

2024-03-14 19:44:14.065 I cue.mod.bragi.hid_report_dispatcher: Command not send. Subdevice disabled. bragiprotocol::CommandId::OpenFile
2024-03-14 19:44:14.065 W cue.mod.bragi.enum.subdevice: Fail counter for "Commander CORE" reached zero, removing subdevice
2024-03-14 19:44:14.065 C cue.mod.bragi.protocol: Main subdevice disconnected! "Commander CORE"
2024-03-14 19:44:14.065 I cue.mod.bragi.channel_temperature_controller: "Get temperature measurements status failed. Device Commander CORE(id:0)"
2024-03-14 19:44:14.065 I cue.mod.bragi.channel_temperature_controller:  Open file with id bragiprotocol::FileId(TemperatureMeasurementsStatus) failed.
  IO operation was cancelled.

2024-03-14 19:44:14.065 I cue.mod.bragi.hid_report_dispatcher: Command not send. Subdevice disabled. bragiprotocol::CommandId::OpenFile
2024-03-14 19:44:14.065 W cue.mod.bragi.enum.subdevice: Fail counter for "Commander CORE" reached zero, removing subdevice
2024-03-14 19:44:14.065 C cue.mod.bragi.protocol: Main subdevice disconnected! "Commander CORE"
2024-03-14 19:44:14.065 I cue.mod.bragi.channel_rotation_controller: "Get coolers actual RPMs failed. Device Commander CORE(id:0)"
2024-03-14 19:44:14.065 I cue.mod.bragi.channel_rotation_controller:  Open file with id bragiprotocol::FileId(CoolersActualRPMs) failed.
  IO operation was cancelled.

2024-03-14 19:44:14.065 C cue.devices.tr_res: Result added after end of transaction
2024-03-14 19:44:14.065 W cue.devices.tr_worker: Trying to send signal to removed TransactionResult
2024-03-14 19:44:14.065 C cue.mod.bragi.protocol: Trying to remove main subdevice for "Commander CORE"

 

Thank you,

- Travis

 

Link to comment
Share on other sites

Contact Corsair Support. Are there any physical issues with the Commander Core?  Lights off, fans don’t run, pump error (!)?  Typically when it’s device specific, CUE will reveal it with an error mark on the device or it alone drops from CUE. A full CUE crash is usually something else. If you haven’t done it already, do a full clean install. Corrupt registry files and/or entanglements with other monitoring/control programs is the number one reason for most crashes on CUE 5. Support is also likely to respond with this as a line 1 step, so might as well head them off. This will erase all profiles and settings. 
 

https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE
 

I would not pinhole reset the Commander as a troubleshooting measure. It has a limited use in specific hardware misbehavior circumstances, none of which appear to be in evidence. It also tends to create a mess with your profiles and CUE will think you added a second Commander Core. 

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
×
×
  • Create New...