Jump to content
Corsair Community

Cue Randomly Crashing disabling side keys


Sunzz

Recommended Posts

So i got my corsair scimitar the other day and its the best mouse iv ever had! the only problem is that the corsair cue software seems to crash randomly, and when it does it disables the side mouse buttons, so when im playing a game, for example world of warcraft, all my buttons stop working unless i start the software again :(. Anyone else with this problem?
Link to comment
Share on other sites

There seems to be a problem with WoW (see here)

 

You can find the log of CUE here: %LOCALAPPDATA%\Corsair\CUE\logs

 

hmm im not sure if this is the log as iv got a few at similar times :S also im not using the beta

 

2016-08-26T12:58:08 I cue.init: CUE version: 2.3.74

2016-08-26T12:58:08 I cue.init: Updates server: https://www3.corsair.com/software/HID/

2016-08-26T12:58:08 I cue.init: Build type: Public Release

2016-08-26T12:58:08 I cue.manifest: Tried 28 files.

2016-08-26T12:58:08 I cue.manifest: Loaded: 35 manifests.

2016-08-26T12:58:08 I cue.session: Locked changed to false

2016-08-26T12:58:08 I cue.session.win: Will notify 'connected changed to' with delay

2016-08-26T12:58:08 I cue.session: Local changed to true

2016-08-26T12:58:10 I cue.session: Connected changed to true

2016-08-26T12:58:10 I cue.dev: Requesting working state enter because session connected.

2016-08-26T12:58:10 I cue.dev.enum.hid: Entering working state.

2016-08-26T12:58:10 I cue.sdk: Entering working state, session connected.

2016-08-26T12:58:10 I cue.sdk: Starting router.

2016-08-26T12:58:10 I cue.dev: Device profile (meta) for device vid=1038 pid=1200 not found.

2016-08-26T12:58:10 I cue.dev: Device profile (meta) for device vid=1038 pid=1200 not found.

2016-08-26T12:58:10 I cue.dev: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&1267f21&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2016-08-26T12:58:10 I cue.dev: Created new device object: Scimitar; ready: 0

2016-08-26T12:58:10 I cue.dev: Attached to device object Scimitar: b=0 a=0

2016-08-26T12:58:10 I cue.dev: Attached to device object Scimitar: b=0 a=0

2016-08-26T12:58:10 I cue.dev: Device profile (meta) for device vid=1038 pid=1200 not found.

2016-08-26T12:58:10 I cue.dev: Device profile (meta) for device vid=1038 pid=1200 not found.

2016-08-26T12:58:10 I cue.dev: Attached to device object Scimitar: b=0 a=1

2016-08-26T12:58:10 I cue.dev: Initializing Scimitar...

2016-08-26T12:58:10 I cue.dev: Device profile (meta) for device vid=1038 pid=1200 not found.

2016-08-26T12:58:10 I cue.dev: Scimitar : trying to force P00 instead of P04

2016-08-26T12:58:10 I cue.dev: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&18ea0b66&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2016-08-26T12:58:10 I cue.dev: Scimitar : success, continue initialization on P00

2016-08-26T12:58:13 I cue.dev: Initialized (st=1) Scimitar.

2016-08-26T12:58:13 I cue.dev: Device insertion processing complete for Scimitar.

2016-08-26T12:58:17 C cue.updater.software.checker: Empty hash string line.

2016-08-26T12:59:01 I cue.init.ui: Starting UI.

2016-08-26T12:59:02 W qrc:/qml/ui/accordion/LibraryPropertyViewsAccordionItem.qml:374: TypeError: Cannot call method 'start' of null

2016-08-26T12:59:02 W qrc:/qml/ui/accordion/LibraryPropertyViewsAccordionItem.qml:374: TypeError: Cannot call method 'start' of null

2016-08-26T12:59:04 I Firmware Download: Aborting idle process not supported.

2016-08-26T12:59:17 W qrc:/qml/editor/BasicLightingEditor.qml:85: TypeError: Cannot read property 'currentColor' of undefined

2016-08-26T12:59:17 W qrc:/QtQuick/Controls/ComboBox.qml:563: ReferenceError: modelData is not defined

2016-08-26T12:59:17 W qrc:/QtQuick/Controls/ComboBox.qml:563: ReferenceError: modelData is not defined

2016-08-26T12:59:17 W qrc:/QtQuick/Controls/ComboBox.qml:563: ReferenceError: modelData is not defined

2016-08-26T12:59:17 W qrc:/QtQuick/Controls/ComboBox.qml:563: ReferenceError: modelData is not defined

2016-08-26T14:52:29 I cue.dev: Requesting working state leave because of transition to Suspended or Shutdown state.

2016-08-26T14:52:29 I cue.dev.enum.hid: Leaving working state.

2016-08-26T14:52:29 W cue.dev: Device "Scimitar" worker thread has stopped

2016-08-26T14:52:29 I cue.sdk: Leaving working state, because of transition to Suspended or Shutdown state.

2016-08-26T14:52:29 I cue.sdk: Stopping router.

2016-08-26T14:52:29 I cue.init: Quit

2016-08-26T14:52:29 I cue.init.ui: Engine shut down.

2016-08-26T14:52:29 W "There are still \"2\" items in the process of being created at engine destruction."

Link to comment
Share on other sites

  • 5 weeks later...

I'm going to bump this thread. I have purchased a Strafe RGB today and got the newest software installed without issue. Upon activation of the software it just crashes immediately.

 

- Tray icon shows up -> crash

- Tray icon shows up -> right click -> crash

 

Either way it's the same result. Further log inspection shows almost the exact lines except mine stops at:

2016-09-24T21:01:29 W qrc:/qml/ui/accordion/LibraryPropertyViewsAccordionItem.qml:397: TypeError: Cannot call method 'start' of null
2016-09-24T21:01:29 W qrc:/qml/ui/accordion/LibraryPropertyViewsAccordionItem.qml:397: TypeError: Cannot call method 'start' of null

 

If i look in the application section of Event Viewer it seems that Qt5Gui.dll would be the culprit.

 

Faulting application name: CUE.exe, version: 2.4.66.0, time stamp: 0x57bc2511
Faulting module name: Qt5Gui.dll, version: 5.6.1.0, time stamp: 0x5745cee6
Exception code: 0xc00000fd
Fault offset: 0x002ccbb7
Faulting process id: 0x1648
Faulting application start time: 0x01d216e6852f7338
Faulting application path: C:\Program Files (x86)\Corsair\Corsair Utility Engine\CUE.exe
Faulting module path: C:\Program Files (x86)\Corsair\Corsair Utility Engine\[b]Qt5Gui.dll[/b]
Report Id: a8414046-9c0e-4e54-b1bf-47a1556e9364
Faulting package full name: 
Faulting package-relative application ID: 

 

I believe either some resources are missing or not properly linked or Corsair has compiled some custom version of the Dll for their use and there is a problem with its implementation.

 

System: Win10 x64 Pro

Link to comment
Share on other sites

  • 6 months later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...