Corsair K100 freezes after latest firmware update

[Copper001]

Ok, update. I have not frozen up tonight. Though, while playing minecraft for a bit the keyboard stuttered, went dark and rebooted. I dumped the iCue logs and saw this at the exact time it crashed:

2023-01-12 03:28:36.296 W cue.devices.enum.subdevice: Fail counter for "K100 RGB" reached zero, removing subdevice
2023-01-12 03:28:36.296 I cue.devices.bragi.command_queue: Command cancelled bragiprotocol::CommandId::WriteBufferBegin
2023-01-12 03:28:36.296 C cue.devices.bragi.physical_hid: Main subdevice disconnected! "K100 RGB"
2023-01-12 03:28:36.296 C cue.devices: Write hunk failed. Device: "K100 RGB"
2023-01-12 03:28:36.296 C cue.devices: Exception:  Timeout (1000ms) while receiving reply.

2023-01-12 03:28:36.296 C cue.devices: Exception while runCommand on device  K100 RGB : 
  Timeout (1000ms) while receiving reply.

2023-01-12 03:28:36.296 I cue.devices.bragi.command_queue: Command not send. Subdevice disabled. bragiprotocol::CommandId::WriteBufferBegin
2023-01-12 03:28:36.296 W cue.devices.enum.subdevice: Fail counter for "K100 RGB" reached zero, removing subdevice
2023-01-12 03:28:36.296 C cue.devices.bragi.physical_hid: Main subdevice disconnected! "K100 RGB"
2023-01-12 03:28:36.297 C cue.devices: Write hunk failed. Device: "K100 RGB"
2023-01-12 03:28:36.297 C cue.devices: Exception:  IO operation was cancelled.

2023-01-12 03:28:36.297 C cue.devices: Exception while runCommand on device  K100 RGB : 
  IO operation was cancelled.

2023-01-12 03:28:36.447 I cue.canvas.render: Stopped lighting worker in 0x1044
2023-01-12 03:28:36.450 W QCoreApplication::postEvent: Unexpected null receiver
2023-01-12 03:28:36.450 W QCoreApplication::postEvent: Unexpected null receiver
2023-01-12 03:28:36.450 W QCoreApplication::postEvent: Unexpected null receiver
2023-01-12 03:28:36.458 I cue.lightings.indication_player: Stopped lighting worker in 0x6718
2023-01-12 03:28:36.499 I cue.lightings.direct_player: Stopped lighting worker in 0x31bc
2023-01-12 03:28:37.300 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (1000ms) while receiving reply.

2023-01-12 03:28:37.300 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2023-01-12 03:28:37.301 C cue.devices: Cannot create subdevice for: "K100 RGB"
2023-01-12 03:28:37.301 C cue.devices:  Failed to get vid, pid from subdevice id: 0

2023-01-12 03:28:37.301 W QObject::connect(AbstractProtocol, bragi::LogicalSubdevice): invalid nullptr parameter
2023-01-12 03:28:37.302 C cue.devices: Trying to remove main subdevice for "K100 RGB"
2023-01-12 03:28:42.289 W cue.devices.bragi.command_queue: Got command duplicate bragiprotocol::CommandId::GetProperty Lifetime: 5991 ms. "K100 RGB"
2023-01-12 03:28:43.290 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (1000ms) while receiving reply.

2023-01-12 03:28:43.290 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2023-01-12 03:28:43.292 C cue.devices: Cannot create subdevice for: "K100 RGB"
2023-01-12 03:28:43.292 C cue.devices:  Failed to get vid, pid from subdevice id: 0

2023-01-12 03:28:48.292 W cue.devices.bragi.command_queue: Got command duplicate bragiprotocol::CommandId::GetProperty Lifetime: 6002 ms. "K100 RGB"
2023-01-12 03:28:49.293 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (1000ms) while receiving reply.

2023-01-12 03:28:49.293 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2023-01-12 03:28:49.294 C cue.devices: Cannot create subdevice for: "K100 RGB"
2023-01-12 03:28:49.294 C cue.devices:  Failed to get vid, pid from subdevice id: 0

2023-01-12 03:28:54.290 W cue.devices.bragi.command_queue: Got command duplicate bragiprotocol::CommandId::GetProperty Lifetime: 5997 ms. "K100 RGB"
2023-01-12 03:28:55.293 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (1000ms) while receiving reply.

2023-01-12 03:28:55.293 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2023-01-12 03:28:55.294 C cue.devices: Cannot create subdevice for: "K100 RGB"
2023-01-12 03:28:55.294 C cue.devices:  Failed to get vid, pid from subdevice id: 0

2023-01-12 03:29:00.289 W cue.devices.bragi.command_queue: Got command duplicate bragiprotocol::CommandId::GetProperty Lifetime: 5998 ms. "K100 RGB"
2023-01-12 03:29:01.291 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (1000ms) while receiving reply.

2023-01-12 03:29:01.291 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2023-01-12 03:29:01.292 C cue.devices: Cannot create subdevice for: "K100 RGB"
2023-01-12 03:29:01.292 C cue.devices:  Failed to get vid, pid from subdevice id: 0

2023-01-12 03:29:06.289 W cue.devices.bragi.command_queue: Got command duplicate bragiprotocol::CommandId::GetProperty Lifetime: 6000 ms. "K100 RGB"
2023-01-12 03:29:07.290 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (1000ms) while receiving reply.

2023-01-12 03:29:07.290 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2023-01-12 03:29:07.291 C cue.devices: Cannot create subdevice for: "K100 RGB"
2023-01-12 03:29:07.291 C cue.devices:  Failed to get vid, pid from subdevice id: 0

2023-01-12 03:29:12.291 W cue.devices.bragi.command_queue: Got command duplicate bragiprotocol::CommandId::GetProperty Lifetime: 6001 ms. "K100 RGB"
2023-01-12 03:29:13.292 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (1000ms) while receiving reply.

2023-01-12 03:29:13.292 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2023-01-12 03:29:13.293 C cue.devices: Cannot create subdevice for: "K100 RGB"
2023-01-12 03:29:13.293 C cue.devices:  Failed to get vid, pid from subdevice id: 0

2023-01-12 03:29:18.290 W cue.devices.bragi.command_queue: Got command duplicate bragiprotocol::CommandId::GetProperty Lifetime: 5998 ms. "K100 RGB"
2023-01-12 03:29:19.291 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (1000ms) while receiving reply.

2023-01-12 03:29:19.291 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2023-01-12 03:29:19.292 C cue.devices: Cannot create subdevice for: "K100 RGB"
2023-01-12 03:29:19.292 C cue.devices:  Failed to get vid, pid from subdevice id: 0

2023-01-12 03:29:24.291 W cue.devices.bragi.command_queue: Got command duplicate bragiprotocol::CommandId::GetProperty Lifetime: 6001 ms. "K100 RGB"
2023-01-12 03:29:25.293 W cue.devices.enum.subdevice:  Get property UsbVid failed.
  Timeout (1000ms) while receiving reply.

2023-01-12 03:29:25.293 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2023-01-12 03:29:25.294 C cue.devices: Cannot create subdevice for: "K100 RGB"
2023-01-12 03:29:25.294 C cue.devices:  Failed to get vid, pid from subdevice id: 0

2023-01-12 03:29:25.308 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_02#7&210605b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" removed.
2023-01-12 03:29:25.308 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_01#7&274803ce&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2023-01-12 03:29:25.310 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_00&col02#7&370c60c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2023-01-12 03:29:25.310 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_01#7&274803ce&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2023-01-12 03:29:25.310 I cue.hid_device_detector: Add close task: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_02#7&210605b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2023-01-12 03:29:25.310 I cue.hid_report_worker: Waiting for report worker stop "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_01#7&274803ce&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2023-01-12 03:29:25.312 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_00&col02#7&370c60c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.
2023-01-12 03:29:25.314 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_01#7&274803ce&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.
2023-01-12 03:29:25.316 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_02#7&210605b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" closed.
2023-01-12 03:29:25.316 I cue.hid_device_detector: Mark all tasks as finished.
2023-01-12 03:29:25.318 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_02#7&210605b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2023-01-12 03:29:25.318 I cue.hid_report_worker: Waiting for report worker stop "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_02#7&210605b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2023-01-12 03:29:32.165 I cue.dev.hidenumerator: Found device VID 6940 PID 7109 Usage Page 12 Usage 1
2023-01-12 03:29:32.167 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col02\\7&370c60c&0&0001")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "12")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.199 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col02\\7&370c60c&0&0001")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "12")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.199 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col02\\7&370c60c&0&0001")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "12")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.200 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col02\\7&370c60c&0&0001")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "12")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.202 I cue.dev.hidenumerator: Found device VID 6940 PID 7109 Usage Page 65346 Usage 1
2023-01-12 03:29:32.202 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_01\\7&274803ce&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.203 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_01\\7&274803ce&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.203 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_01\\7&274803ce&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.203 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_01\\7&274803ce&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.203 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_01\\7&274803ce&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.203 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_01\\7&274803ce&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.203 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_01\\7&274803ce&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.203 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_01\\7&274803ce&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.205 I cue.dev.hidenumerator: Found device VID 6940 PID 7109 Usage Page 65346 Usage 2
2023-01-12 03:29:32.206 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_02\\7&210605b&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.206 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_02\\7&210605b&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.206 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_02\\7&210605b&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.206 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_02\\7&210605b&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65346")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.208 I cue.dev.hidenumerator: Found device VID 6940 PID 7109 Usage Page 1 Usage 6
2023-01-12 03:29:32.208 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col01\\7&370c60c&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.208 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col01\\7&370c60c&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.209 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col01\\7&370c60c&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.209 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col01\\7&370c60c&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.209 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col01\\7&370c60c&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.209 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col01\\7&370c60c&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.209 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col01\\7&370c60c&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.209 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_00&col01\\7&370c60c&0&0000")("hid-direction", "output")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.210 I cue.dev.hidenumerator: Found device VID 6940 PID 7109 Usage Page 1 Usage 2
2023-01-12 03:29:32.211 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_03\\7&19d3eca0&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.212 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_03\\7&19d3eca0&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.212 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_03\\7&19d3eca0&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))  not found.
2023-01-12 03:29:32.212 I cue.dev.mgr: No manifest for QMap(("bus", "hid")("devInstanceId", "hid\\vid_1b1c&pid_1bc5&mi_03\\7&19d3eca0&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "1")("model-name", "CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard")("usb-pid", "7109")("usb-vid", "6940")("vendor", "Corsair"))
2023-01-12 03:29:32.215 I cue.mod.legacy.enum: Device vid=1b1c pid=1bc5 ignored by cue::dev::legacy::LegacyEnumeratorImpl
2023-01-12 03:29:32.215 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_00&col02#7&370c60c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1bc5&mi_00&col02\\7&370c60c&0&0001", ParentInstanceId: "USB\\VID_1B1C&PID_1BC5\\493469D24AAA7CC6\u0000") inserted.
2023-01-12 03:29:32.215 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_00&col02#7&370c60c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 1000 ms.
2023-01-12 03:29:32.215 I cue.mod.legacy.enum: Device vid=1b1c pid=1bc5 ignored by cue::dev::legacy::LegacyEnumeratorImpl
2023-01-12 03:29:32.215 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_01#7&274803ce&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1bc5&mi_01\\7&274803ce&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_1BC5\\493469D24AAA7CC6\u0000") inserted.
2023-01-12 03:29:32.215 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_01#7&274803ce&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 1000 ms.
2023-01-12 03:29:32.215 I cue.mod.legacy.enum: Device vid=1b1c pid=1bc5 ignored by cue::dev::legacy::LegacyEnumeratorImpl
2023-01-12 03:29:32.215 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_02#7&210605b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1bc5&mi_02\\7&210605b&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_1BC5\\493469D24AAA7CC6\u0000") inserted.
2023-01-12 03:29:32.216 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_02#7&210605b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 1000 ms.
2023-01-12 03:29:32.216 I cue.mod.legacy.enum: Device vid=1b1c pid=1bc5 ignored by cue::dev::legacy::LegacyEnumeratorImpl
2023-01-12 03:29:32.216 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_00&col01#7&370c60c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd", InstanceId: "hid\\vid_1b1c&pid_1bc5&mi_00&col01\\7&370c60c&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_1BC5\\493469D24AAA7CC6\u0000") inserted.
2023-01-12 03:29:32.216 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_00&col01#7&370c60c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd" with delay 1000 ms.
2023-01-12 03:29:32.216 I cue.mod.legacy.enum: Device vid=1b1c pid=1bc5 ignored by cue::dev::legacy::LegacyEnumeratorImpl
2023-01-12 03:29:32.216 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_03#7&19d3eca0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1bc5&mi_03\\7&19d3eca0&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_1BC5\\493469D24AAA7CC6\u0000") inserted.
2023-01-12 03:29:32.216 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_03#7&19d3eca0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 1000 ms.
2023-01-12 03:29:33.213 C cue.hid_device_detector: Failed to open: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_03#7&19d3eca0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2023-01-12 03:29:33.214 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_00&col02#7&370c60c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened.
2023-01-12 03:29:33.214 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_01#7&274803ce&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened.
2023-01-12 03:29:33.214 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_02#7&210605b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened.
2023-01-12 03:29:33.214 I cue.devices: Begin attaching to "K100 RGB" "(vid=1b1c, pid=1bc5)" "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_00&col02#7&370c60c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2023-01-12 03:29:33.214 I cue.devices: End attaching to "K100 RGB" "(vid=1b1c, pid=1bc5)" "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_00&col02#7&370c60c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0
2023-01-12 03:29:33.214 C cue.hid_device_detector: Failed to open: "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_00&col01#7&370c60c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd"
2023-01-12 03:29:33.214 I cue.hid_device_detector: Mark all tasks as finished.
2023-01-12 03:29:33.214 I cue.devices: Created new device"K100 RGB" "(vid=1b1c, pid=1bc5)"; ready:false
2023-01-12 03:29:33.214 I cue.devices: Begin attaching to "K100 RGB" "(vid=1b1c, pid=1bc5)" "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_01#7&274803ce&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2023-01-12 03:29:33.215 I cue.devices: End attaching to "K100 RGB" "(vid=1b1c, pid=1bc5)" "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_01#7&274803ce&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1
2023-01-12 03:29:33.215 I cue.devices: Begin attaching to "K100 RGB" "(vid=1b1c, pid=1bc5)" "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_02#7&210605b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 1
2023-01-12 03:29:33.215 I cue.devices: End attaching to "K100 RGB" "(vid=1b1c, pid=1bc5)" "\\\\?\\hid#vid_1b1c&pid_1bc5&mi_02#7&210605b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1
2023-01-12 03:29:33.217 I cue.devices: Initializing "K100 RGB" "(vid=1b1c, pid=1bc5)"
2023-01-12 03:29:33.218 I cue.devices: Initialized true "K100 RGB" "(vid=1b1c, pid=1bc5)"
2023-01-12 03:29:33.218 I cue.devices.enum.subdevice: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed.
2023-01-12 03:29:33.343 C cue.devices: "Failed to get property LedModuleProductLineId for K100 RGB using GetMultipleProperties"
2023-01-12 03:29:33.343 C cue.devices:  Get property LedModuleProductLineId failed.
  Command processing error: PropertyNotSupported.

2023-01-12 03:29:33.386 C cue.devices: "Failed to get property LedModuleVendorId for K100 RGB using GetMultipleProperties"
2023-01-12 03:29:33.386 C cue.devices:  Get property LedModuleVendorId failed.
  Command processing error: PropertyNotSupported.

2023-01-12 03:29:33.427 C cue.devices: "Failed to get property LedModuleVersionId for K100 RGB using GetMultipleProperties"
2023-01-12 03:29:33.427 C cue.devices:  Get property LedModuleVersionId failed.
  Command processing error: PropertyNotSupported.

2023-01-12 03:29:33.427 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2023-01-12 03:29:33.780 W cue.devices: Failed to read device error log. Device "K100 RGB"
2023-01-12 03:29:33.780 W cue.devices:  Open file with id bragiprotocol::FileId(ErrorLog) failed.
  Command processing error: InvalidDeviceAddress.

2023-01-12 03:29:33.789 I cue.dev.mgr: Candidate device for QMap(("bus", "legacy")("usb-pid", "7109")("usb-vid", "6940"))  not found.
2023-01-12 03:29:33.794 W Unimplemented conversion for command:  30
2023-01-12 03:29:33.794 W Unimplemented conversion for command:  91
2023-01-12 03:29:33.794 W Unimplemented conversion for command:  160
2023-01-12 03:29:33.794 W Unimplemented conversion for command:  161
2023-01-12 03:29:33.794 W Unimplemented conversion for command:  162
2023-01-12 03:29:33.794 W Unimplemented conversion for command:  163
2023-01-12 03:29:33.794 W Unimplemented conversion for command:  164
2023-01-12 03:29:33.794 W Unimplemented conversion for command:  165
2023-01-12 03:29:33.794 W Unimplemented conversion for command:  157
2023-01-12 03:29:33.794 W cue.profiles.mappings_actualizer: HW layouts are not ready! "K100 RGB"
2023-01-12 03:29:33.794 I cue.profiles.mappings_actualizer: Device doesn't need volume wheel workaround: "K100 RGB"
2023-01-12 03:29:33.794 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "7109")("usb-vid", "6940"))
2023-01-12 03:29:33.833 I cue.canvas.render: Started worker in 0x2564
2023-01-12 03:29:33.839 C cue.devices: Exception while runCommand on device  K100 RGB : 
  Get property HostOperatingSystem failed.
  Command processing error: PropertyNotSupported.

2023-01-12 03:29:33.856 I cue.devices: Device insertion processing complete for K100 RGB (vid=1b1c, pid=1bc5)
2023-01-12 03:29:33.857 I cue.lightings.indication_player: Started lighting worker in 0x1d38
2023-01-12 03:29:33.858 I cue.lightings.direct_player: Started lighting worker in 0x6e30
2023-01-12 03:29:33.904 W Transaction failed:  (2)
2023-01-12 03:29:33.904 W Transaction failed:  (2)
2023-01-12 03:29:33.904 W Transaction failed:  (2)
2023-01-12 03:29:33.904 W Transaction failed:  (2)
2023-01-12 03:29:33.904 W Transaction failed:  (2)
2023-01-12 03:29:34.004 C cue.hw_profile.bragi.occupied_files: Cannot get cached file bragiprotocol::FileId(FreeFile#28000)
2023-01-12 03:29:34.379 C cue.devices: Exception while runCommand on device  K100 RGB : 
  Get property HostOperatingSystem failed.
  Command processing error: PropertyNotSupported.

2023-01-12 03:29:34.379 C cue.devices.host_os_controller: Read failed "K100 RGB"
2023-01-12 03:29:35.549 I cue.dev.hidenumerator: Found device VID 1133 PID 49277 Usage Page 12 Usage 1
2023-01-12 03:29:35.551 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col02\\7&f7e7dff&0&0001")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "12")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.552 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col02\\7&f7e7dff&0&0001")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "12")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.567 I cue.dev.hidenumerator: Found device VID 1133 PID 49277 Usage Page 1 Usage 128
2023-01-12 03:29:35.570 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col03\\7&f7e7dff&0&0002")("hid-direction", "input")("hid-type", "report")("hid-usage", "128")("hid-usagepage", "1")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.571 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col03\\7&f7e7dff&0&0002")("hid-direction", "input")("hid-type", "report")("hid-usage", "128")("hid-usagepage", "1")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.574 I cue.dev.hidenumerator: Found device VID 1133 PID 49277 Usage Page 65280 Usage 1
2023-01-12 03:29:35.575 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col04\\7&f7e7dff&0&0003")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65280")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.576 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col04\\7&f7e7dff&0&0003")("hid-direction", "input")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65280")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.576 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col04\\7&f7e7dff&0&0003")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65280")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.577 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col04\\7&f7e7dff&0&0003")("hid-direction", "output")("hid-type", "report")("hid-usage", "1")("hid-usagepage", "65280")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.587 I cue.dev.hidenumerator: Found device VID 1133 PID 49277 Usage Page 65280 Usage 2
2023-01-12 03:29:35.588 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col05\\7&f7e7dff&0&0004")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65280")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.589 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col05\\7&f7e7dff&0&0004")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65280")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.589 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col05\\7&f7e7dff&0&0004")("hid-direction", "output")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65280")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.589 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col05\\7&f7e7dff&0&0004")("hid-direction", "output")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "65280")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.590 I cue.dev.hidenumerator: Found device VID 1133 PID 49277 Usage Page 1 Usage 2
2023-01-12 03:29:35.591 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_00\\7&22ae9a3d&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "1")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.592 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_00\\7&22ae9a3d&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "2")("hid-usagepage", "1")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.594 I cue.dev.hidenumerator: Found device VID 1133 PID 49277 Usage Page 1 Usage 6
2023-01-12 03:29:35.595 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col01\\7&f7e7dff&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
2023-01-12 03:29:35.595 I cue.dev.mgr: Candidate device for QMap(("bus", "hid")("devInstanceId", "hid\\vid_046d&pid_c07d&mi_01&col01\\7&f7e7dff&0&0000")("hid-direction", "input")("hid-type", "report")("hid-usage", "6")("hid-usagepage", "1")("model-name", "Gaming Mouse G502")("usb-pid", "49277")("usb-vid", "1133")("vendor", "Logitech"))  not found.
 

The same error occurred in the log last night @03:30 when it froze up while typing in discord.

Do you want me to attach the whole log.zip? And if so, should I post that to this forum, or to you directly, since it does contain system info.

[FWWS13_Benni]

Where do i find these log files
I could provide mine to (if i find them)

[Copper001]

19 minutes ago, FWWS13_Benni said:

Where do i find these log files
I could provide mine to (if i find them)

Open iCUE and then the settings wheel in the upper right.

Then click on Export System Info and Logs. It'll show a file dialog, it is actually wanting a filename and it will make a zip file in that location.

You can open that zip to view the individual logs (there are lots!) The log in question that I looked at is the CUELogs ones, they have a non-ascii dot followed by a Timestamp

I'm not sure how useful the logs will be, as they may only be showing the fallout of the crash. But, it is *definitely* the fingerprint of the event occurring. I have that same error every single time. Since I have the Stream Deck unplugged, it didn't freeze all I/O up, so maybe some hints there. It did go dark, reboot and act a little sluggish for a few seconds. I've typed several thousand words tonight and only had that one hang during minecraft. The hangs do occur in all applications though. As I think back, I have had those little reset dropouts several times over the last month, but never a real hang until the Stream Deck was plugged in.

Edited January 13, 2023 by Copper001
rewording that these may only be showing fallout and not the event itself

[Gracey]

Also getting this issue, have just logged a ticket.

Out of interest, does everyone getting this issue have something plugged into the USB on the back of the keyboard? I personally have my Virtuoso SE wireless dongle in there, and I wonder if that's contributing to the issue at all.

[Takkero]

same problem here. just bought it. i will wait till 30 JEN then i will get refound from Amazon. i alreary placed a 1 star review on amazon for this failure product.. incredible that a 300 euro keyboard is s**t. support is totally no existent. after 8 days they asnwer me asking me to do the soft reset... i wrote in the ticket "I ALREADY DID THE SOFT RESET". are u even reading the tickets or just answe with "pre made" stupid message?

disappointed at max level!

Edited January 13, 2023 by Takkero

[FWWS13_Benni]

2 hours ago, Gracey said:

Also getting this issue, have just logged a ticket.

Out of interest, does everyone getting this issue have something plugged into the USB on the back of the keyboard? I personally have my Virtuoso SE wireless dongle in there, and I wonder if that's contributing to the issue at all.

no

[xPETEZx]

I have had my K100 do this twice in the last week.

I am on the latest firmware version: 1.11.39

Product number: CN-912A01A-UK

Using Windows 11 22H2,

iCUE 4.32.129

Keyboard attached via USB switcher hub.

 

Had my K70 Vengenace for over 8 years never had a single issue. 'Upgraded' to this K100 just before Xmas.... and its already having problems??

[Corsair Nick]

@Copper001 - Thanks for the log info.  Believe we have Zip uploads disabled on the forums, but the details you sent should be fine. Your remarks about it potentially being in a Macro Recording state are interesting.  Can you check your "Hardware Key Assignments" tab for the K100 in iCUE, and verify if there are any unintended macros populating the area?

[GhostRider1s1]

On 1/11/2023 at 8:38 PM, Corsair Nick said:

• Part Number from the back of the keyboard (CH-9XXXXXX)
• CH-912A01A-DE
• What version of iCUE do you have installed?
• 4.32.129
• Windows 10 or 11? And current update version?
• Currently Windows 11 Pro 22H2 Build 22621.1105, but before Christmas on my old PC i had Windows 10 and the same problem with freezing occured also there. Both my systems are always up to date. 
• Polling Rate?
• 1000Hz
• Is the keyboard plugged directly to the motherboard?
• Yes
• Does the freezing occur even with iCUE completely closed and exited out of?
• Yes

Hi, thank you for responding. I have added the requested data about my system above. 

Since yesterday I am also having the same problem as BusPilot explained a few posts above me. When i try to update my K100 firmware it says in red letters that the update failed. 

I have no StreamDeck or Software for that product installed.

[FWWS13_Benni]

So i haven´t frozen up today and yesterday but it went dark and rebooted

I am on Icue 4.32.129 now

The "Update Failed" Issue persists

 

Log_13_01_23.pdf

Edited January 13, 2023 by FWWS13_Benni

[Corsair Nick]

@GhostRider1s1@FWWS13_Benni - I confirmed that the FW update to v1.11.39 has been pulled temporarily as a precaution based on the initial feedback from the community, which is why you will receive the error.  Can both of you confirm if there are any unintended macros in the "Hardware Key Assignments" tab for your keyboard in iCUE?

[FWWS13_Benni]

There are no makros in this sektion

in neighter of the profiles

Edited January 13, 2023 by FWWS13_Benni

[FWWS13_Benni]

I just had it freez on me and 2 min later icue crashed

I hope these can somewhat help

 

If those are the wrong ones just tell me i´m still trying to figure out what is what

Freez-log.pdf crash_log.pdf

[Corsair Nick]

For the Hardware Key Assignment, you will need to check the hardware profile on the keyboard itself.  If you don't have the profile saved to iCUE, you can perform the following to save it from the keyboard to iCUE:

• Select the Keyboard
• Select Device Settings
• Select 3dot option next to profiles slots on the keyboard
• Select "Copy to iCUE"
• Select the Hardware Profile just coppied in the upper left corner of iCUE
• Select the Hardware Key Assignments tab for the keyboard

[Copper001]

No macros are recorded in the Hardware Key Assignments on my system either.

I have been able to record a macro with the macro wheel (goes to Hardware Key Assignments), and via the iCUE software (Goes to Key Assigments). I can play the software assignment back, but not the hardware one. I am assuming that is only accessible when the KB is in hardware more, so I think everything is operating correctly with record/playback. I also can delete assignments and the key is unmapped successfully.

[FWWS13_Benni]

I played around with the profiles and none of them have unwanted makros

Kreating and deleting works

[GhostRider1s1]

14 hours ago, Corsair Nick said:

@GhostRider1s1@FWWS13_Benni - I confirmed that the FW update to v1.11.39 has been pulled temporarily as a precaution based on the initial feedback from the community, which is why you will receive the error.  Can both of you confirm if there are any unintended macros in the "Hardware Key Assignments" tab for your keyboard in iCUE?

 

Thank you @Corsair Nick for clearing up that matter!

I have also saved the only hardware profile on my K100, which was the default one in my case, to iCue and looked at the Hardware Key Assignments. In my case there are also no stored makros in there. 

[GhostRider1s1]

I just had a look at my logs which I dumped last night when I had two crashes which were around an hour apart from each other. Every crash I get the same ones as @Copper001posted at the beginning of this page. Just for reference I also attached a pdf with my log beginning at the crash. Hope this helps.

K100 Crash Log.pdf

Edited January 14, 2023 by GhostRider1s1

[Tiucaner]

On 1/11/2023 at 7:38 PM, Corsair Nick said:

Thanks for bringing this to our attention, and the behavior you all are describing can be frustrating.  I'll need some additional information so we can investigate further and have a better understanding of what is causing the freezing after the update.  Can all of you provide the following:

• Part Number from the back of the keyboard (CH-9XXXXXX)
• What version of iCUE do you have installed?
• Windows 10 or 11? And current update version?
• Upload your system specs to your forum profile
• Polling Rate?
• Is the keyboard plugged directly to the motherboard?
• Does the freezing occur even with iCUE completely closed and exited out of?

Most of you haven't submitted tickets for this issue yet.  Please visit the support page and submit a ticket so that the Technical Support team can properly field your inquiry and assist you with an appropriate resolution if needed.

Part Number from the back of the keyboard:  CH-912A01A-ES

What version of iCUE do you have installed: v. 4.32.129

Windows 10 or 11? And current update version?: Windows 10 22H2

Polling Rate?: 1000 hz/1 ms

Is the keyboard plugged directly to the motherboard?: Yes

Does the freezing occur even with iCUE completely closed and exited out of?: Pretty much.

[rghong]

Just wanted to add a few more behavior of this.  

If you have multiple corsair device, it causes iCue to behave abnormally too, would randomly crash, your other devices will randomly disconnects and will report an error to windows.  This is my 5th day using a different keyboard (Corsair K95 XT), I have never been so happy downgrading and not experiencing issues at all. 

I have 3 friends that have K100 and all of them having the same issues, with 1 identical to mine, due to having 3+ corsair devices.

for people that have multiple Corsair devices and still have the K100 plugged in, the moment icue crashes, you just cant restart the service it will cause it to crash again.  you have to disconnect the K100 first, then re launch icue, and you will able to get icue stabilize again, for a short period of time (rinse and repeat until corsair fixes this).

for Icue employees:  if you have Q/A personels, have them use this keyboard for 2-3 days, same firmware, heck, get from a retailer.  they will experience an IDENTICAL behavior.

firmware and icue version is on the screenshot below

- I cue will no longer detect K100

- RGB frozen

- will completely lock and the only way to reconnect again is to DISCONNECT from the PC as restarting will not work.

Hope this helps you guys.

[Copper001]

On 1/13/2023 at 11:36 AM, Corsair Nick said:

@Copper001 - Your remarks about it potentially being in a Macro Recording state are interesting. 

I mention that because reports that the keyboard is repeat typing things EXACTLY, at original speed, including corrections. From what I can tell, when you software record a macro, it's simply the text. In hardware more, it includes the exact millisecond typing of keydown/keyup for each stroke. Hence, I believe it to be in the firmware functions. And, assuming it fills up and causes a buffer overrun somewhere, I would completely see that the firmware would crash/freeze when a byte is written where it shouldn't be. Software would probably just fault/crash and give us a nasty message in the OS, or if written somewhere innocuous, simply keep going. 

Also, with my Stream Deck unplugged, I've had no more freezes, though it has blackout/rebooted the keyboard a few times. It might not be a issue with the SD, it might simply be that the software might be able to recover with just the KB hanging/rebooting, but not with the SD still responding and in a normal state. Thanks for pulling the firmware until we hopefully get a handle on this. I hope you have a good weekend.

[Copper001]

Ok, I just had another lockup/freeze. Stream Deck Mk2 is unplugged (and has been since your request) and finally had a lockup, with the last key hit, 'S' being stuck. I tested with my other keyboard and I could type, no total IO lockup this time, though the mouse left click was still captured and inoperative. After unplug/replug all IO function is restored. Note that during this time, iCUE does not crash and seems to work normally. I don't have to restart it either. 

The current logs of the crash started with:

2023-01-14 23:32:28.725 W cue.devices.enum.subdevice: Fail counter for "K100 RGB" reached zero, removing subdevice
2023-01-14 23:32:28.725 I cue.devices.bragi.command_queue: Command cancelled bragiprotocol::CommandId::WriteBufferBegin
2023-01-14 23:32:28.726 C cue.devices.bragi.physical_hid: Main subdevice disconnected! "K100 RGB"
2023-01-14 23:32:28.726 C cue.devices: Write hunk failed. Device: "K100 RGB"
2023-01-14 23:32:28.726 C cue.devices: Exception:  Timeout (1000ms) while receiving reply.

2023-01-14 23:32:28.726 C cue.devices: Exception while runCommand on device  K100 RGB : 
  Timeout (1000ms) while receiving reply.

2023-01-14 23:32:28.726 I cue.devices.bragi.command_queue: Command not send. Subdevice disabled. bragiprotocol::CommandId::WriteBufferBegin
2023-01-14 23:32:28.726 W cue.devices.enum.subdevice: Fail counter for "K100 RGB" reached zero, removing subdevice
2023-01-14 23:32:28.726 C cue.devices.bragi.physical_hid: Main subdevice disconnected! "K100 RGB"
2023-01-14 23:32:28.726 C cue.devices: Write hunk failed. Device: "K100 RGB"
2023-01-14 23:32:28.726 C cue.devices: Exception:  IO operation was cancelled.

Just staring at the 2nd line there... the writebufferbegin. The crashes don't happen often with low KB input (lasts 12+ hours with me just talking in Discord, w/ occasional keypresses), but they do within an hour with me typing scripts or playing minecraft. Hopefully, the devs can take the FW code apart and see if it's a buffer running out. Just feels like one. I don't know the code, so it's just a guess.

 

[Takkero]

@Corsair Nick is not possible to have u post here the previous firmware so we can all rollback and fix the situation while we wait corsair release a new (and fixed we hope) one?.

icue does have the "SEARCH FIRMWARE" feature that allow us to browse the pc for a firmware.

i have opened the ticked with support and now with ticket #2005848181 and "Thomas S." gave me that the only solution is ... the RMA... but to be honest i just bought this keyboard less than 10 days ago on amazon and i dont know if doing an RMA will void my 30 days in which i can give it back and get full refound.

i noticed that corsair does not have an ARCHIVE with all older versions of his product's firmwares.

anyway isn't faster to provide us all the FIRMWARE PREVIUS THE LATEST?

[FWWS13_Benni]

@Corsair Nick I think that would be a good idea 

[BusPilot]

@Corsair Nickplease, post the older firmware! This keyboard is a amazing piece of art, but with this freezing is making us crazy! I don’t have any macros running, latest icue software, windows 10, nothing connected on k100 and now a icue nexus, same issue. I tried the lower spooling rate and didn’t change a thing. The only thing that help was the complete removal of icue from windows registry as a post here on support page. But it just increased the time between freezes. But it keeps happening. Please, send us the older firmware.