Jump to content
Corsair Community

Keyboard profile freezing when prompted to switch profiles by iCUE


Zammin
 Share

Recommended Posts

This is something that has actually been occurring on my K95 platinum since last year, before iCUE existed. However I am using iCUE now so I feel it is relevant to post the issue and log entries here.

 

If you want to see my full thread over in the keyboard and mouse forum, the link is here: http://forum.corsair.com/v3/showthread.php?p=955647#post955647

 

However it seems every time I post in that forum I get a few replies after my initial post and then nothing after that. Makes it hard to get help.

 

The issue in question is that my K95 platinum sometimes freezes on the default profile when prompted to switch to another profile that is tied to the launch of an application. In this case games. This usually happens after the PC and keyboard have been on for most of the day or overnight. My other Corsair peripherals and Commander Pro will switch profiles every time without fail, it's just the K95P that freezes. The only way to remedy it is to unplug the keyboard and plug it back in. (power cycle)

 

When it started happening to my first K95P I lodged a support ticket with Corsair which turned out to be a long and painful endeavor, which resulted in me having to RMA the keyboard. The replacement I received didn't have this issue for a few months until just recently. I have been on iCUE for a couple weeks but this issue only started showing again in the last few days.

 

These log entries are found at the time that the keyboard freezes:

 

Example 1:

2018-05-17T17:35:21 I cue.lightings.player: Stopped lighting worker in 0x2b78

2018-05-17T17:35:21 W cue.dev: Device "K95 RGB PLATINUM" worker thread has stopped

 

Example 2:

2018-05-20T17:28:57 I cue.dev: Buffer write, 1. failed. request timed out for K95 RGB PLATINUM

2018-05-20T17:51:55 I cue.lightings.player: Stopped lighting worker in 0x327c

2018-05-20T17:51:55 W cue.dev: Device "K95 RGB PLATINUM" worker thread has stopped

 

I believe this to be an issue with CUE/iCUE, as I have tested the 2 keyboards I've had on 3 separate PC's and it has occurred on all of them.

 

I really need assistance from Corsair or an iCUE dev on this issue, I have (regretfully) lodged another support ticket however I doubt I will get any further than "use CCleaner" and "Reset the keyboard or manually reinstall the firmware" again.

 

I will post the full log file from "Example 1" below. The freeze occurred at 17:35:

 

2018-05-16T12:23:35 I cue.dev: Opened device: "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col04#7&37ba9901&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-16T12:23:35 I cue.dev: Begin attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col04#7&37ba9901&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0

2018-05-16T12:23:35 I cue.dev: End attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col04#7&37ba9901&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0

2018-05-16T12:23:35 C dev.manifest: Cannot find path for manifest key (vid=1532, pid=5c)

2018-05-16T12:23:35 I cue.dev: Manifest for device (vid=1532, pid=5c) not found.

2018-05-16T12:23:35 I cue.dev: Failed to open device: (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col05#7&37ba9901&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-16T12:23:35 C dev.manifest: Cannot find path for manifest key (vid=b05, pid=1872)

2018-05-16T12:23:35 I cue.dev: Manifest for device (vid=b05, pid=1872) not found.

2018-05-16T12:23:35 C dev.manifest: Cannot find path for manifest key (vid=1038, pid=1724)

2018-05-16T12:23:35 I cue.dev: Manifest for device (vid=1038, pid=1724) not found.

2018-05-16T12:23:35 I cue.dev: Opened device: "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_02#7&13e35b3f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-16T12:23:35 I cue.dev: Begin attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_02#7&13e35b3f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0

2018-05-16T12:23:35 I cue.dev: End attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_02#7&13e35b3f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1

2018-05-16T12:23:35 I cue.dev: Initializing "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d)

2018-05-16T12:23:35 C dev.manifest: Cannot find path for manifest key (vid=46d, pid=c52b)

2018-05-16T12:23:35 I cue.dev: Manifest for device (vid=46d, pid=c52b) not found.

2018-05-16T12:23:35 C dev.manifest: Cannot find path for manifest key (vid=1038, pid=1724)

2018-05-16T12:23:35 I cue.dev: Manifest for device (vid=1038, pid=1724) not found.

2018-05-16T12:23:35 C dev.manifest: Cannot find path for manifest key (vid=1038, pid=1724)

2018-05-16T12:23:35 I cue.dev: Manifest for device (vid=1038, pid=1724) not found.

2018-05-16T12:23:35 I cue.dev: Initialized true "MM800RGB" (vid=1b1c, pid=1b3b)

2018-05-16T12:23:35 I cue.lightings.player: Started lighting worker in 0x2b74

2018-05-16T12:23:35 I cue.dev: Device insertion processing complete for MM800RGB.

2018-05-16T12:23:35 I cue.dev: Initialized true "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d)

2018-05-16T12:23:35 I cue.lightings.player: Started lighting worker in 0x2b78

2018-05-16T12:23:35 I cue.dev: Device insertion processing complete for K95 RGB PLATINUM.

2018-05-16T12:23:36 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=7)

2018-05-16T12:23:36 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=1)

2018-05-16T12:23:36 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=400)

2018-05-16T12:23:36 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=2)

2018-05-16T12:23:36 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=400)

2018-05-16T12:23:37 C cue.download.fw: Incorrect index contents: fw obj is empty "combined-image"

2018-05-16T12:23:37 I cue.download.fw: Incorrect index contents: condition for "image-priority" is empty

2018-05-16T12:23:37 C cue.download.fw: Incorrect index contents: fw obj is empty "combined-image"

2018-05-16T12:23:37 I cue.download.fw: Incorrect index contents: condition for "image-priority" is empty

2018-05-16T13:58:21 I cue.dev: Buffer write, 1. failed. request timed out for K95 RGB PLATINUM

2018-05-16T17:17:32 C dev.manifest: Cannot find path for manifest key (vid=9886, pid=1)

2018-05-16T17:17:32 I cue.dev: Manifest for device (vid=9886, pid=1) not found.

2018-05-17T07:53:15 I cue.dev: MouseMat LED colors change failed. request timed out for MM800RGB

2018-05-17T17:27:02 I cue.init.ui: Starting UI.

2018-05-17T17:27:02 W QObject::connect: invalid null parameter

2018-05-17T17:27:02 I cue.dev: Get profiles list failed. request timed out for K95 RGB PLATINUM

2018-05-17T17:27:02 I cue.dev: Get profiles list failed. Device: K95 RGB PLATINUM, Execution result = 0, result = 0, platform error code = 995.

2018-05-17T17:27:03 W MainWindow_QMLTYPE_463(0x1a925030) must be a top level window.

2018-05-17T17:27:03 W MainWindow_QMLTYPE_463(0x1a925030) must be a top level window.

2018-05-17T17:27:03 W file:///C:/Program Files (x86)/Corsair/Corsair Utility Engine/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"

2018-05-17T17:27:03 W qrc:/qml/ui/DevicesPanel.qml:87:4: QML Binding: Binding loop detected for property "value"

2018-05-17T17:27:03 W <Unknown File>: QML DelegateModel: Error creating delegate

2018-05-17T17:27:15 W file:///C:/Program Files (x86)/Corsair/Corsair Utility Engine/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"

2018-05-17T17:27:15 W file:///C:/Program Files (x86)/Corsair/Corsair Utility Engine/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"

2018-05-17T17:27:15 W file:///C:/Program Files (x86)/Corsair/Corsair Utility Engine/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"

2018-05-17T17:27:15 W file:///C:/Program Files (x86)/Corsair/Corsair Utility Engine/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"

2018-05-17T17:27:15 W file:///C:/Program Files (x86)/Corsair/Corsair Utility Engine/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"

2018-05-17T17:27:15 W DirectWrite: CreateFontFaceFromHDC() failed (Indicates an error in an input file such as a font file.) for QFontDef(Family="", pointsize=9, pixelsize=12, styleHint=5, weight=50, stretch=100, hintingPreference=0) LOGFONT("MS Sans Serif", lfWidth=0, lfHeight=-12) dpi=96

2018-05-17T17:27:15 W file:///C:/Program Files (x86)/Corsair/Corsair Utility Engine/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"

2018-05-17T17:27:15 W qml: Role 'decoration' is undefined

2018-05-17T17:27:15 W file:///C:/Program Files (x86)/Corsair/Corsair Utility Engine/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"

2018-05-17T17:27:15 W qml: Role 'decoration' is undefined

2018-05-17T17:27:15 W qrc:/qml/delegate/DeviceSettingsProperties.qml:510:18: Unable to assign null to QUrl

2018-05-17T17:27:15 W qrc:/qml/delegate/DeviceSettingsProperties.qml:510:18: Unable to assign null to QUrl

2018-05-17T17:27:15 W qrc:/qml/editor/MobileServerSettingsEditor.qml:55: TypeError: Cannot read property 'serverLocalIp' of null

2018-05-17T17:27:15 W qrc:/qml/editor/MobileServerSettingsEditor.qml:52: TypeError: Cannot read property 'connectionAllowed' of null

2018-05-17T17:27:15 W qrc:/qml/editor/MobileServerSettingsEditor.qml:61: TypeError: Cannot read property 'connectionAllowed' of null

2018-05-17T17:27:15 W qrc:/qml/editor/MobileServerSettingsEditor.qml:97: TypeError: Cannot read property 'connectionAllowed' of null

2018-05-17T17:27:15 W qrc:/qml/editor/MobileServerSettingsEditor.qml:131: TypeError: Cannot read property 'connectionAllowed' of null

2018-05-17T17:27:15 W <Unknown File>: QML DelegateModel: Error creating delegate

2018-05-17T17:27:20 C cue.download.fw: Incorrect index contents: fw obj is empty "combined-image"

2018-05-17T17:27:20 I cue.download.fw: Incorrect index contents: condition for "image-priority" is empty

2018-05-17T17:28:18 I cue.init.ui: Trimming cache.

2018-05-17T17:35:21 I cue.lightings.player: Stopped lighting worker in 0x2b78

2018-05-17T17:35:21 W cue.dev: Device "K95 RGB PLATINUM" worker thread has stopped

2018-05-17T17:35:27 I cue.dev: Marked as slow startup "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col02#7&37ba9901&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:27 I cue.dev: Marked as slow startup "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col03#7&37ba9901&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:27 I cue.dev: Marked as slow startup "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col04#7&37ba9901&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:27 I cue.dev: Marked as slow startup "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_02#7&13e35b3f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:27 I cue.dev: Marked as slow startup "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_00#7&2d38952f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:27 I cue.dev: Marked as slow startup "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col01#7&37ba9901&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:27 I cue.dev: Marked as slow startup "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col05#7&37ba9901&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:28 I cue.dev: Opened device: "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col02#7&37ba9901&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:28 I cue.dev: Begin attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col02#7&37ba9901&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0

2018-05-17T17:35:28 I cue.dev: End attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col02#7&37ba9901&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0

2018-05-17T17:35:28 I cue.dev: Created new device "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d); ready: false

2018-05-17T17:35:28 I cue.dev: Opened device: "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col03#7&37ba9901&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:28 I cue.dev: Begin attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col03#7&37ba9901&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0

2018-05-17T17:35:28 I cue.dev: End attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col03#7&37ba9901&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0

2018-05-17T17:35:28 I cue.dev: Opened device: "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col04#7&37ba9901&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:28 I cue.dev: Begin attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col04#7&37ba9901&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0

2018-05-17T17:35:28 I cue.dev: End attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col04#7&37ba9901&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0

2018-05-17T17:35:28 I cue.dev: Opened device: "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_02#7&13e35b3f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:28 I cue.dev: Begin attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_02#7&13e35b3f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0

2018-05-17T17:35:28 I cue.dev: End attaching to "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_02#7&13e35b3f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1

2018-05-17T17:35:28 I cue.dev: Initializing "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d)

2018-05-17T17:35:28 I cue.dev: Failed to open device: (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_00#7&2d38952f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:28 I cue.dev: Failed to open device: (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col01#7&37ba9901&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:28 I cue.dev: Failed to open device: (vid=1b1c, pid=1b2d) "\\\\?\\hid#vid_1b1c&pid_1b2d&mi_01&col05#7&37ba9901&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}"

2018-05-17T17:35:28 I cue.dev: Initialized true "K95 RGB PLATINUM" (vid=1b1c, pid=1b2d)

2018-05-17T17:35:28 I cue.lightings.player: Started lighting worker in 0x19bc

2018-05-17T17:35:28 I cue.dev: Device insertion processing complete for K95 RGB PLATINUM.

2018-05-17T17:35:28 C cue.download.fw: Incorrect index contents: fw obj is empty "combined-image"

2018-05-17T17:35:28 I cue.download.fw: Incorrect index contents: condition for "image-priority" is empty

Edited by Zammin
Link to comment
Share on other sites

So.. Nobody has anything to say? I'm currently waiting on Corsair support to contact the CUE team about this, but any and all help is welcome..

 

I am also experiencing the issue with the profile/brightness/winlock buttons flickering.

Link to comment
Share on other sites

http://forum.corsair.com/v3/showthread.php?t=171258 same thing (i think?) here, they don't care about it, no replies in months. by the looks its a common issue with the k95platinum.

 

Thank you so much! I'm so glad I'm not alone here!

 

I noted that there is another thread linked in that one with the same issue again. I will send these to Corsair support. They are currently trying to get a replacement for me, but in case it's not a hardware issue I think it's important that they look into this on the software/firmware side of things.

Link to comment
Share on other sites

Yea I don't think its the keyboard. Can you try lowering the polling rate in iCUE for the K95 plat?

 

The team is setting up for Computex right now so it might be a week or two before they can respond.

 

Hey thanks for the response. I understand computex is right around the corner and I don't expect to hear anything right away.

 

I have not tried lowering the polling rate just yet. Support has already agreed to replace my keyboard so I'll see how that goes.

 

If the issue persists I can try lowering the polling rate, but considering I bought the product new, and it is advertised as being capable of running a 1000hz polling rate I would expect it to be able to do that without causing problems for itself. I guess what I'm saying is, if lowering the polling rate makes the issue go away, that's great as a short term fix but the product still needs to function as advertised.

 

If the problem lies with iCUE exclusively however, that's another story as iCUE is clearly in early access. However again it is worth noting that this issue has existed prior to iCUE's release, so there's a good chance it's either CUE related, firmware related or both. After looking at the other threads it looks to be fairly limited to the K95 platinum and not other models.

Edited by Zammin
Link to comment
Share on other sites

Hey thanks for the response. I understand computex is right around the corner and I don't expect to hear anything right away.

 

I have not tried lowering the polling rate just yet. Support has already agreed to replace my keyboard so I'll see how that goes.

 

If the issue persists I can try lowering the polling rate, but considering I bought the product new, and it is advertised as being capable of running a 1000hz polling rate I would expect it to be able to do that without causing problems for itself. I guess what I'm saying is, if lowering the polling rate makes the issue go away, that's great as a short term fix but the product still needs to function as advertised.

 

If the problem lies with iCUE exclusively however, that's another story as iCUE is clearly in early access. However again it is worth noting that this issue has existed prior to iCUE's release, so there's a good chance it's either CUE related, firmware related or both. After looking at the other threads it looks to be fairly limited to the K95 platinum and not other models.

 

Right ideally it should run at 1000Mhz, but if lowering the polling relieves the issue might be a USB controller issue? Also, you said you had this problem before iCUE so I'm guessing it's occurring on CUE 2 also. I see that you tried it in 3 different systems so I get why you suspect a software issue. Would be my first guess too.

Link to comment
Share on other sites

Right ideally it should run at 1000Mhz, but if lowering the polling relieves the issue might be a USB controller issue? Also, you said you had this problem before iCUE so I'm guessing it's occurring on CUE 2 also. I see that you tried it in 3 different systems so I get why you suspect a software issue. Would be my first guess too.

 

Yeah a compatibility issue between CUE/iCUE/the keyboard and the usb controller/driver is definitely a possibility, but it would be strange having seen this on two Gigabyte systems and one ASUS system.

Link to comment
Share on other sites

 Share

×
×
  • Create New...