Jump to content
Corsair Community

Driver crashes - Corsair M65 RGB


aijorgenson

Recommended Posts

I have a Corsair M65 RGB mouse(12k dpi). When playing games which require a lot of mouse movement, the drivers will crash and reinitialize. Sometimes the LEDs and scrollwheel on the mouse will not function but the actual optical sensor still works. Unplugging and plugging the USB temporarily resolves the issue.

 

I'm not looking to RMA because I really like the product and I depend on it. However, when playing CSGO and having the mouse drivers crash putting me in a situation where I can't aim for 20 seconds or so is very annoying in competitive.

 

I have a K95 RGB to go with the mouse, and I absolutely love the keyboard. I wasn't expecting to have any issues from a Corsair product and was pretty surprised when I started having issues with the mouse.

 

I'm sure it's a driver issue, and not a issue with the mouse itself. It's on the latest firmware.

 

I am a programmer and have a somewhat ok understanding of hardware. I can work alongside a Corsair engineer to resolve the issue.

Link to comment
Share on other sites

Here is a log where I was able to crash the mouse drivers again.

 

[2016-05-25T15:55:07]: UserSessionInfo: locked changed to 0.

[2016-05-25T15:55:07]: UserSessionInfo: connected changed to 1.

[2016-05-25T15:55:07]: UserSessionInfo: local changed to 1.

[2016-05-25T15:55:10]: UserSessionInfo: locked changed to 0.

[2016-05-25T15:55:10]: UserSessionInfo: connected changed to 1.

[2016-05-25T15:55:10]: UserSessionInfo: local changed to 1.

[2016-05-25T15:55:12]: UserSessionInfo: locked changed to 0.

[2016-05-25T15:55:12]: UserSessionInfo: connected changed to 1.

[2016-05-25T15:55:12]: UserSessionInfo: local changed to 1.

[2016-05-25T15:55:12]: Created new device object: M65 PRO RGB; ready: 0

[2016-05-25T15:55:12]: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_00#8&2b26db90&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-05-25T15:55:12]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_01&col01#8&371756b5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-05-25T15:55:12]: Attached to device object M65 PRO RGB: b=1 a=1

[2016-05-25T15:55:12]: Attached to device object M65 PRO RGB: b=1 a=1

[2016-05-25T15:55:12]: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_01&col01#8&13634f4b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-05-25T15:55:12]: Attached to device object M65 PRO RGB: b=1 a=0

[2016-05-25T15:55:12]: Initializing M65 PRO RGB...

[2016-05-25T15:55:12]: M65 PRO RGB : trying to force P00 instead of P04

[2016-05-25T15:55:12]: Created new device object: K95 RGB; ready: 0

[2016-05-25T15:55:12]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_00#8&134018f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-05-25T15:55:12]: Attached to device object K95 RGB: b=1 a=1

[2016-05-25T15:55:12]: Attached to device object K95 RGB: b=1 a=1

[2016-05-25T15:55:12]: Attached to device object K95 RGB: b=1 a=0

[2016-05-25T15:55:12]: Initializing K95 RGB...

[2016-05-25T15:55:12]: M65 PRO RGB : success, continue initialization on P00

[2016-05-25T15:55:12]: Initialized (st=1) K95 RGB.

[2016-05-25T15:55:12]: Device insertion processing complete for K95 RGB.

[2016-05-25T15:55:15]: Initialized (st=1) M65 PRO RGB.

[2016-05-25T15:55:16]: Device insertion processing complete for M65 PRO RGB.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:57]: Device vid=1b1c pid=1b2e is marked 'slow startup'.

[2016-05-25T16:00:58]: Created new device object: M65 PRO RGB; ready: 0

[2016-05-25T16:00:58]: Attached to device object M65 PRO RGB: b=1 a=1

[2016-05-25T16:00:58]: Attached to device object M65 PRO RGB: b=1 a=1

[2016-05-25T16:00:58]: Attached to device object M65 PRO RGB: b=1 a=0

[2016-05-25T16:00:58]: Initializing M65 PRO RGB...

[2016-05-25T16:00:58]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_00#8&134018f3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-05-25T16:00:58]: M65 PRO RGB : trying to force P00 instead of P04

[2016-05-25T16:00:58]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_01&col01#8&371756b5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-05-25T16:00:58]: M65 PRO RGB : success, continue initialization on P00

[2016-05-25T16:01:01]: Initialized (st=1) M65 PRO RGB.

[2016-05-25T16:01:02]: Device insertion processing complete for M65 PRO RGB.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...