Jump to content
Corsair Community

iCUE 4.33.138 crashes shortly after startup


Go to solution Solved by Corsair Notepad,

Recommended Posts

After updating from 4.32.129, it crashes as soon as it starts up. The app is visible for maybe 10 seconds and then disappears.

It's filed with errors like this:

Quote

2023-02-02 01:02:49.089 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "3090")("usb-vid", "6940"))
2023-02-02 01:02:49.173 C cue.hw_profile.bragi.occupied_files: Cannot get cached file bragiprotocol::FileId(FreeFile#28008)
2023-02-02 01:02:49.180 W QObject: Cannot create children for a parent that is in a different thread.
(Parent is QNetworkAccessManager(0x26836b4d870), parent's thread is QThread(0x26824fa9ef0), current thread is QThread(0x90ded4fae8)
2023-02-02 01:02:49.180 W QObject: Cannot create children for a parent that is in a different thread.
(Parent is QNetworkAccessManager(0x26836b4d870), parent's thread is QThread(0x26824fa9ef0), current thread is QThread(0x90ded4fae8)
2023-02-02 01:02:49.203 I cue.devices: Device insertion processing complete for H150i PRO (vid=1b1c, pid=c12)
2023-02-02 01:02:49.203 I cue.dev.enum.adapter: Inserted proto: "vid<1b1c>pid<000c12>serial<4660;7289_2.0>index<0>"
2023-02-02 01:02:49.203 W cue.devices.enum.demo: Registration of device with unsupported DemoUsbId:  "(vid=0, pid=0)"
2023-02-02 01:02:49.204 W failed converting DeviceType to string in method:  devicelistwatcher::DeviceListKeeper::removedDevicesAtStart
2023-02-02 01:02:49.204 W failed converting DeviceType to string in method:  devicelistwatcher::DeviceListKeeper::removedDevicesAtStart
2023-02-02 01:02:49.204 I cue.sdk.device_watcher: Start prepare WorkingStateState
2023-02-02 01:02:49.204 I cue.lightings.direct_player: Started lighting worker in 0x5368
2023-02-02 01:02:49.204 I cue.sdk.device_watcher: Finish prepare WorkingStateState
2023-02-02 01:02:49.205 W cue.touchscreens.crossdevice: Attached LightingLinkEffectSwitchingAction(0x2684ce1c560) to the device "K95 RGB PLATINUM XT"
2023-02-02 01:02:49.247 I cue.sys_info.win: Info: prop=Manufacturer class=Win32_PnpEntity returned=false
2023-02-02 01:02:49.278 I cue.sys_info.win: Info: prop=Service class=Win32_PnpEntity returned=false
2023-02-02 01:02:49.283 I cue.firmware.package_index_parser_old: Package content is empty "combined-image"
2023-02-02 01:02:55.936 C cue.devices: Write hunk failed. Device: "K95 RGB PLATINUM XT"
2023-02-02 01:02:55.937 C cue.devices: Exception:  Timeout (100ms) while sending command.

2023-02-02 01:02:55.937 C cue.devices: Exception while runCommand on device  K95 RGB PLATINUM XT : 
  Timeout (100ms) while sending command.

2023-02-02 01:02:55.938 I cue.sys_info.win: Info: prop=MACAddress class=Win32_NetworkAdapter returned=false

or this:

Quote

2023-02-02 01:02:48.737 C cue.hw_profile.bragi.occupied_files: Cannot get cached file bragiprotocol::FileId(StoredProfile3)
2023-02-02 01:02:48.798 W cue.hw_profile.bragi: Read file bragiprotocol::FileId(FreeFile#28025) failed for CorsairDevice("DARK CORE PRO SE"; 0x2684ba90760)
2023-02-02 01:02:48.798 W cue.hw_profile.bragi:  Open file with id bragiprotocol::FileId(FreeFile#28025) failed.
  Command processing error: InvalidState.

2023-02-02 01:02:48.798 W cue.hw_profile.bragi: Read layout from bragiprotocol::FileId(FreeFile#28025) failed
2023-02-02 01:02:48.841 W cue.hw_profile.bragi: Read file bragiprotocol::FileId(FreeFile#28018) failed for CorsairDevice("DARK CORE PRO SE"; 0x2684ba90760)
2023-02-02 01:02:48.841 W cue.hw_profile.bragi:  Open file with id bragiprotocol::FileId(FreeFile#28018) failed.
  Command processing error: InvalidState.

 

Link to comment
Share on other sites

  • Corsair Employee
  • Solution
Link to comment
Share on other sites

I followed these steps, reinstalled and it seemed to work initially. But I already had two crashes as I switched between sections on devices, for example on Virtuoso SE I switched to equalizer or wanted to open Lighting Node PRO settings. This hasn't happened before.

Edited by Ingvarr100th
Link to comment
Share on other sites

  • Corsair Employee

Make sure that your chipset drivers and motherboard BIOS is fully up to date. And any other third party software that you have installed and running also make sure they are updated, especially things like your motherboard software.

 

Link to comment
Share on other sites

I am having an issue where any spinning lighting option in the lighting link has a random studder every five or six rotations like it skips or starts over. I didn't have this issue before the new update, so I am not sure what's really happening.

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...