Vunak Posted December 31, 2015 Share Posted December 31, 2015 Have been having CUE crash with this error, sometimes it just says its a Fatal Error and my log file isn't logging anything so I cant post the logs. Any ideas? Link to comment Share on other sites More sharing options...
Toasted Posted January 1, 2016 Share Posted January 1, 2016 Have you tried running CUE as admin? Is Windows, BIOS, chipset drivers, etc up to date? Have you tried reinstalling CUE, previous version of CUE or a different install location? Link to comment Share on other sites More sharing options...
Vunak Posted January 1, 2016 Author Share Posted January 1, 2016 Have you tried running CUE as admin? Is Windows, BIOS, chipset drivers, etc up to date? Have you tried reinstalling CUE, previous version of CUE or a different install location? I have tried all of that and yes all of my drivers are up to date and my BIOS is as well. CUE gets ran in admin mode on startup. Link to comment Share on other sites More sharing options...
Toasted Posted January 3, 2016 Share Posted January 3, 2016 Run a system file check and see whether it resolves the issue. In command prompt with admin rights, type sfc /scannow Link to comment Share on other sites More sharing options...
Vunak Posted January 8, 2016 Author Share Posted January 8, 2016 Still getting the crashes after trying everything suggested. I don't get the crashes with only my scimitar plugged in. But if I have my scimitar and k95 rgb plugged or only my k95 rgb plugged it crashes while in games. Link to comment Share on other sites More sharing options...
Toasted Posted January 10, 2016 Share Posted January 10, 2016 Check CUE log's and see whether anything useful shows up. You can access the log files in Settings > Support > View logs or the default file path; C:\Users\-Your Username-\AppData\Local\Corsair\HID\logs Link to comment Share on other sites More sharing options...
Vunak Posted January 11, 2016 Author Share Posted January 11, 2016 T his is what the log says, its pretty short. even if its been active for a few hours, this is what it normally says: [2016-01-11T00:17:36]: UserSessionInfo: locked changed to 0. [2016-01-11T00:17:36]: UserSessionInfo: connected changed to 1. [2016-01-11T00:17:36]: UserSessionInfo: local changed to 1. [2016-01-11T00:17:37]: UserSessionInfo: locked changed to 0. [2016-01-11T00:17:37]: UserSessionInfo: connected changed to 1. [2016-01-11T00:17:37]: UserSessionInfo: local changed to 1. [2016-01-11T00:17:38]: Device profile (meta) for device vid=1b1c pid=c04 not found. [2016-01-11T00:17:38]: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_00#7&10fe81b8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-01-11T00:17:38]: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_01&col01#7&28c20dfd&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-01-11T00:17:38]: Created new device object: K95 RGB; ready: 0 [2016-01-11T00:17:38]: Attached to device object K95 RGB: b=1 a=1 [2016-01-11T00:17:38]: Attached to device object K95 RGB: b=1 a=0 [2016-01-11T00:17:38]: Initializing K95 RGB... [2016-01-11T00:17:38]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#8&afab0e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-01-11T00:17:38]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#8&13dfc74c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-01-11T00:17:38]: Created new device object: Scimitar; ready: 0 [2016-01-11T00:17:38]: Attached to device object Scimitar: b=1 a=1 [2016-01-11T00:17:38]: Attached to device object Scimitar: b=1 a=0 [2016-01-11T00:17:38]: Initializing Scimitar... [2016-01-11T00:17:38]: Initialized (st=1) K95 RGB. [2016-01-11T00:17:38]: Device insertion processing complete for K95 RGB. [2016-01-11T00:17:41]: Initialized (st=1) Scimitar. [2016-01-11T00:17:42]: Device insertion processing complete for Scimitar. Thanks again for the help. Link to comment Share on other sites More sharing options...
Toasted Posted January 12, 2016 Share Posted January 12, 2016 Weird. In the logs, CUE is failing to open a device which is related to the keyboard. Do you have any unknown devices or devices with errors in Device Manager? Contact customer service, ask for instructions for a 'hard reset' and see whether that resolves your issue. https://corsair.secure.force.com/ Have you tried 'resetting' CUE? You can do this by deleting the files in %appdata%\Corsair. Note: It will remove all user created content. Link to comment Share on other sites More sharing options...
Vunak Posted January 20, 2016 Author Share Posted January 20, 2016 Weird. In the logs, CUE is failing to open a device which is related to the keyboard. Do you have any unknown devices or devices with errors in Device Manager? Contact customer service, ask for instructions for a 'hard reset' and see whether that resolves your issue. https://corsair.secure.force.com/ Have you tried 'resetting' CUE? You can do this by deleting the files in %appdata%\Corsair. Note: It will remove all user created content. Thanks for the suggestions. I'm not sure what resolved all my issues. But wanted to update and say that everything has been working smoothly for the past couple days. Thanks again for the help. Link to comment Share on other sites More sharing options...
Toasted Posted January 20, 2016 Share Posted January 20, 2016 Good to hear. It could have been a update in Windows or something related. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.