The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Keyboards and Mice

Reply
 
Thread Tools Search this Thread Rate Thread Display Modes
  #1  
Old 05-15-2018, 11:36 PM
Zammin Zammin is offline
Registered User
Zammin's PC Specs
 
Join Date: Jan 2018
Posts: 76
POST ID # = 954821
Zammin Reputation: 10
Sad Second K95P after RMA, all original issues have returned. Corsair please help me out.

I had to RMA my first K95 platinum because it had two issues:

- Failure to auto switch profiles when prompted by CUE (when launching games and such)
- Random lights under the keys flickering white every so often.

The replacement I got has fixed the issue with profile switching (actually it hasn't, see posts below), which was my primary concern, however the issue with random LEDs flickering white every so often remains. It's a small issue and I thought it might be an issue with CUE, so I waited to see if the next few updates to CUE would fix it. There have been about 3 updates to CUE since then, and I have even tried iCUE and the issue persists.

I have tried running the keyboard without CUE recently and the issue still occurs. Perhaps it's a firmware issue however it's worth noting I am on the latest firmware.

Is this a relatively small issue? yes. However when purchasing Corsair's top of the line and most expensive keyboard I would expect no glitches. Especially after having to RMA the first one. I live in Australia and these things cost $300 here!

If anyone reading this has experienced the same thing, please let me know.

If anyone from Corsair is reading this, please chime in and give my your thoughts or some ideas to trouble shoot this. I will not be contacting Corsair's tech support because every time I deal with them they are unhelpful and often ignore me. I seem to have better luck posting on the forum.

Perhaps this is also worth posting in the RMA section of the forum?

Let me know.

Thanks.

Last edited by Zammin; 05-19-2018 at 11:17 PM. Reason: Edited title due to additional issues
Reply With Quote


  #2  
Old 05-16-2018, 12:54 PM
Corsair Mint Corsair Mint is offline
Corsair Employee
 
Join Date: Apr 2016
Posts: 648
POST ID # = 954913
Corsair Mint Reputation: 24
Default

Hi Zammin,

For the flickering, does it happen on different ports or different computers as well? Curious to here that it's still happening even after switching to another replacement unit.
Reply With Quote


  #3  
Old 05-16-2018, 02:55 PM
datsyuk datsyuk is offline
Registered User
 
Join Date: May 2017
Posts: 32
POST ID # = 954926
datsyuk Reputation: 20
Default

Check my threads and your logs from CUE for buffer write failures.
Reply With Quote


  #4  
Old 05-16-2018, 03:09 PM
gpvecchi's Avatar
gpvecchi gpvecchi is offline
Registered User
gpvecchi's PC Specs
 
Join Date: Aug 2012
Location: 44°43'25.02"N 10°23'55.59"E
Posts: 273
POST ID # = 954928
gpvecchi Reputation: 10
Default

Yup, CUE issue, not hardware.
Reply With Quote


  #5  
Old 05-16-2018, 09:03 PM
Zammin Zammin is offline
Registered User
Zammin's PC Specs
 
Join Date: Jan 2018
Posts: 76
POST ID # = 954968
Zammin Reputation: 10
Default

Quote:
Originally Posted by Corsair Mint View Post
Hi Zammin,

For the flickering, does it happen on different ports or different computers as well? Curious to here that it's still happening even after switching to another replacement unit.
Hi and thanks for the reply.

It does happen regardless of USB port, I don't really have another PC to test it on. It's unpredictable so I'd need to be using it on someone elses PC throughout the day to really test it. I have updated all my driver's though, and I'm not using a third party USB card or anything.

Quote:
Originally Posted by datsyuk View Post
Check my threads and your logs from CUE for buffer write failures.
Hey there, I've had a look through the logs and couldn't see anything about dropped packets, I'll see if it says anything about buffer write errors. is there anything else I should be looking for? I'm on iCUE right now.

Quote:
Originally Posted by gpvecchi View Post
Yup, CUE issue, not hardware.
I'm not entirely convinced that it's CUE, as I mentioned it does it when CUE isn't running as well. Might be a firmware problem.

Last edited by Zammin; 05-16-2018 at 10:26 PM.
Reply With Quote


  #6  
Old 05-16-2018, 10:25 PM
Zammin Zammin is offline
Registered User
Zammin's PC Specs
 
Join Date: Jan 2018
Posts: 76
POST ID # = 954975
Zammin Reputation: 10
Default

I had a look at my logs and there was only one of these:

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

Additionally, although not related to the keyboard it was followed by this:

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

If it helps, I can copy and paste the entire logs here. Let me know.

Last edited by Zammin; 05-16-2018 at 10:42 PM.
Reply With Quote


  #7  
Old 05-17-2018, 03:58 AM
Zammin Zammin is offline
Registered User
Zammin's PC Specs
 
Join Date: Jan 2018
Posts: 76
POST ID # = 954994
Zammin Reputation: 10
Default

I can't believe this, additionally to this issue, after leaving my PC on overnight the profile switching problem is back. As soon as the keyboard was prompted to enter the profile set for Titanfall 2 all the lights froze just like my first one. So the original problem is back. I've had so many problems with Corsair peripherals it's driving me nuts... :(

I had to make the pictures below links because for some reason they were showing up as huge in this thread, but this is what my Titanfall 2 profile is supposed to look like, orange/yellow to match the Corsair MM800RGB mouse mat you can see in the background:

https://i.imgur.com/2TUU9rO.jpg

This is what it looked like when I launched Titanfall 2. Notice how the Corsair mouse mat has switched correctly but the keyboard is still on my default (red) profile?

https://i.imgur.com/T0XKqa4.jpg

The rainbow wave at the top is frozen as well. The only way to remedy this is to disconnect the keyboard and plug it back in.

I will post the contents of the log file below, can someone from Corsair please have a look and help me fix this.

I want to like my Corsair stuff so badly, I love the aesthetic and feel of all the peripherals I've owned but I've had nothing but trouble with them since day one. I've returned 2 Glaive mice and RMA'd one K95P only to have the same issues surface again. I have absolutely no such issues with any of my Razer or Steel Series stuff. I've spent $355 on this keyboard including the double shot PBT keycaps (which really should be included on the K95P in the first place) and I don't want to have to replace it..

Log File Contents: (the issue occurred at 17:35, suspect entries are in RED)

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

Last edited by Zammin; 05-17-2018 at 04:10 AM.
Reply With Quote


  #8  
Old 05-17-2018, 04:57 AM
Zammin Zammin is offline
Registered User
Zammin's PC Specs
 
Join Date: Jan 2018
Posts: 76
POST ID # = 954995
Zammin Reputation: 10
Default

Oh also I can confirm the profile switching/freezing issue has happened on 3 separate systems. When I had my first K95P I owned an older 4790k system, and before RMA'ing it I tested it overnight on another person's PC (7600k system) and the exact same thing occurred. Now I have an 8700k system and the same issues are occurring.

So to summarise, the LED flickering issue occurred on both my old and new system, and the profile switching/freezing issue occurred on 3 separate PC's altogether.

Corsair, please give me your thoughts. I'm thinking it may be a problem with your K95P firmware, but I'd be happy to be proven wrong.
Reply With Quote


  #9  
Old 05-18-2018, 10:08 PM
Zammin Zammin is offline
Registered User
Zammin's PC Specs
 
Join Date: Jan 2018
Posts: 76
POST ID # = 955234
Zammin Reputation: 10
Default

Bumping this thread so it doesn't get buried, I really need help from Corsair here.
Reply With Quote


  #10  
Old 05-20-2018, 08:41 AM
Zammin Zammin is offline
Registered User
Zammin's PC Specs
 
Join Date: Jan 2018
Posts: 76
POST ID # = 955392
Zammin Reputation: 10
Default

Keyboard profile froze again today when launching Titanfall 2. Found these in the log again:

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 would really appreciate some assistance.
Reply With Quote


  #11  
Old 05-21-2018, 09:49 PM
Zammin Zammin is offline
Registered User
Zammin's PC Specs
 
Join Date: Jan 2018
Posts: 76
POST ID # = 955647
Zammin Reputation: 10
Default

Anybody??? Come on Corsair please don't ignore me here, I paid a lot of money for this keyboard, it shouldn't be giving me so much grief.
Reply With Quote


  #12  
Old 05-22-2018, 07:19 AM
Cri1654 Cri1654 is offline
Registered User
 
Join Date: Apr 2017
Posts: 14
POST ID # = 955671
Cri1654 Reputation: 10
Default

I have the same problem. It's so annoying and i can't do nothing about it. With the new iCUE the flickering seems to be worse than the CUE2 because now even my Corsair Sabre RGB becan to flicker. I don't even know if i should buy their products anymore. Also my keyboard is a Rapidfire RGB (RMA'd 2 times) with the new light controller so it should not flicker but it does.
Reply With Quote


  #13  
Old 05-22-2018, 07:41 AM
Zammin Zammin is offline
Registered User
Zammin's PC Specs
 
Join Date: Jan 2018
Posts: 76
POST ID # = 955673
Zammin Reputation: 10
Default

Quote:
Originally Posted by Cri1654 View Post
I have the same problem. It's so annoying and i can't do nothing about it. With the new iCUE the flickering seems to be worse than the CUE2 because now even my Corsair Sabre RGB becan to flicker. I don't even know if i should buy their products anymore. Also my keyboard is a Rapidfire RGB (RMA'd 2 times) with the new light controller so it should not flicker but it does.
Thanks for chiming in. Do you experience the profile freezing issue as well or just the flickering?
Reply With Quote


  #14  
Old 05-22-2018, 10:33 AM
Cri1654 Cri1654 is offline
Registered User
 
Join Date: Apr 2017
Posts: 14
POST ID # = 955691
Cri1654 Reputation: 10
Default

Just absurd amount of flickering
Reply With Quote


  #15  
Old 05-24-2018, 02:22 AM
Zammin Zammin is offline
Registered User
Zammin's PC Specs
 
Join Date: Jan 2018
Posts: 76
POST ID # = 955926
Zammin Reputation: 10
Default

I am waiting on Corsair support to contact the CUE team about these issues, but I have had zero luck getting a response from any of the Corsair employees here on the forum.

I'm not really sure why they aren't chiming in. I don't know if they are the same people as technical support or a separate group, either way I'm hoping to get at least one of these issues resolved before this thread is buried and never seen again..
Reply With Quote


Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 05:14 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2018, vBulletin Solutions, Inc.