madcap123 Posted March 24, 2016 Share Posted March 24, 2016 Which then kills the mouse bindings (extra buttons). It only happens occasionally but is annoying if I am playing online in a team, and was wondering if there's anything I can do to help prevent it from happening. Software is up to date and haven't really changed any settings except for lighting. Windows 7 M65 RGB mouse K70 RGB (gen 2). P.S. There's no error message and it just seems to exit (no process and it disappears from taskbar). Link to comment Share on other sites More sharing options...
Toasted Posted March 25, 2016 Share Posted March 25, 2016 Can you upload the latest logs? Settings>Support>View logs. Does it only crash on that specific game or does it crash from any application? Any chance you are using complex macros on the mouse? Does event viewer show any entries under applications related to CUE? Link to comment Share on other sites More sharing options...
madcap123 Posted March 25, 2016 Author Share Posted March 25, 2016 Sadly, the logs start at the 24th and I haven't been in game so much since the last abrupt close down. However, I am seeing errors: 2016-03-24T23:40:26]: Failed to open device: vid=1b1c pid=1b13 path=\\?\hid#vid_1b1c&pid_1b13&mi_01&col01#8&7e717d2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} And [2016-03-25T04:25:53]: Mouse LED colors change failed. request timed out for M65 RGB Plus [2016-03-24T21:11:15]: Set dpi properties failed. Current storage 0.Device : M65 RGB,Execution result = 1, result = 0, platform error code = 1167. [2016-03-24T21:11:15]: Fail counter for M65 RGB reached zero, setting status 2. As well as [2016-03-24T21:11:17]: Device vid=1b1c pid=1b12 is marked 'slow startup'. Found in the logs. I have no macros setup. In event log, all I can find related to CUE is this: Faulting application name: CorsairHID.exe, version: 1.15.36.0, time stamp: 0x56b216d6 Faulting module name: Qt5Gui.dll, version: 5.4.1.0, time stamp: 0x54e2d846 Exception code: 0xc0000005 Fault offset: 0x00050fc0 Faulting process id: 0x900 Faulting application start time: 0x01d1856767b8cfd1 Faulting application path: C:\Program Files (x86)\Corsair\Corsair Utility Engine\CorsairHID.exe Faulting module path: C:\Program Files (x86)\Corsair\Corsair Utility Engine\Qt5Gui.dll Report Id: e8224765-f185-11e5-90ac-f46d0413aef9 Link to comment Share on other sites More sharing options...
madcap123 Posted March 27, 2016 Author Share Posted March 27, 2016 Well, it has happened again. Nothing in logs (I think they're just for initialisation anyway) and no other clue as to why it's happening. Never had this happen before with any other gaming peripheral software. Link to comment Share on other sites More sharing options...
madcap123 Posted April 1, 2016 Author Share Posted April 1, 2016 Thought I would let the world know that I haven't had any problems since I updated to 1.16 a few days ago. Link to comment Share on other sites More sharing options...
Toasted Posted April 4, 2016 Share Posted April 4, 2016 Does it CUE crash in any other game or is it just a specific game? If specific, Which game is it? Is the event log the same each time CUE crashes? Link to comment Share on other sites More sharing options...
Comet 1626864951 Posted April 15, 2017 Share Posted April 15, 2017 See http://forum.corsair.com/v3/showthread.php?p=899397 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.