Piccolo Posted October 8, 2014 Share Posted October 8, 2014 Hello all, I have experienced a few BSODs in windows during normal operation, and using the debug tools in the Windows SDK, it is linked back to SnakeEyes.sys which is part of the driver for the M65 mouse. I am using the most recent driver on a clean install of Windows 8.1 x64. Can anyone else confirm having this issue as well? Normally the recommended action is to update to the latest driver, but that has already been done. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000047, fffff802998ef1ac, 0, 0} *** ERROR: Module load completed but symbols could not be loaded for SnakeEyes.sys Probably caused by : SnakeEyes.sys ( SnakeEyes+1abe ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000047, The exception code that was not handled Arg2: fffff802998ef1ac, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded. FAULTING_IP: nt!RtlRaiseStatus+18 fffff802`998ef1ac 488b8424b8010000 mov rax,qword ptr [rsp+1B8h] BUGCHECK_STR: 0x1E_c0000047 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre DPC_STACK_BASE: FFFFF8029B252FB0 LAST_CONTROL_TRANSFER: from fffff802999e1eda to fffff8029995aca0 STACK_TEXT: fffff802`9b24a5c8 fffff802`999e1eda : 00000000`0000001e ffffffff`c0000047 fffff802`998ef1ac 00000000`00000000 : nt!KeBugCheckEx fffff802`9b24a5d0 fffff802`999621ed : fffff802`9b24add0 00000000`00000001 fffff802`9b24ad30 fffff802`9b24a740 : nt!KiFatalExceptionHandler+0x22 fffff802`9b24a610 fffff802`998ef3a5 : 00000000`00000001 fffff802`99807000 fffff802`9b24ad00 fffff800`00000000 : nt!RtlpExecuteHandlerForException+0xd fffff802`9b24a640 fffff802`998ef1e2 : 00000000`00000000 00000000`00000000 00000000`c0000047 00000000`00000000 : nt!RtlDispatchException+0x1a5 fffff802`9b24ad10 fffff802`9998f02b : ffffe000`72cbfad0 fffff800`69401a22 ffff0000`00000000 00000000`00000001 : nt!RtlRaiseStatus+0x4e fffff802`9b24b2b0 fffff800`6c49aabe : 00000000`00000064 ffffe000`00000001 00000000`00000000 ffffe000`72abe250 : nt! ?? ::FNODOBFM::`string'+0x23e7b fffff802`9b24b360 fffff802`9988ddf8 : ffffe000`706e6650 fffff802`9b24b489 ffffe000`72a93190 ffffe000`706e6acb : SnakeEyes+0x1abe fffff802`9b24b3e0 fffff800`68a018fc : 00000000`ffffffff 00000000`00000000 00000000`00000004 ffffe000`72b4b980 : nt!IopfCompleteRequest+0x588 fffff802`9b24b4f0 fffff800`68a0e364 : ffffe000`7229c790 00000000`00000000 fffff802`00000001 ffffe000`7229c502 : Wdf01000!FxRequest::CompleteInternal+0x23c fffff802`9b24b5b0 fffff800`6b72af16 : ffffe000`7229c790 fffff802`9b240000 ffffe000`7229c5f0 ffffe000`7229c5f0 : Wdf01000!imp_WdfRequestComplete+0x8c fffff802`9b24b620 fffff800`6b72be8c : ffffe000`7229c790 00000000`00000001 ffffe000`7229c810 fffff802`9b24b7a0 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x15a fffff802`9b24b680 fffff800`6b71902b : 00000000`00000780 ffffe000`72bfc790 00000000`00000000 fffff800`6a734dcb : USBXHCI!Bulk_ProcessTransferEventWithED1+0x3a8 fffff802`9b24b730 fffff800`68a99c81 : 00000000`00000000 ffffe000`71376a60 00001fff`8d403a58 fffff802`99aeff00 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0x427 fffff802`9b24b830 fffff802`9984a130 : fffff802`99aeff00 fffff802`9b24bb00 ffffe000`72bfc5a0 fffff802`9986cae0 : Wdf01000!FxInterrupt::DpcHandler+0xc1 fffff802`9b24b860 fffff802`9984934b : fffff802`99aed180 ffffe000`7352f430 00000000`00000004 fffff802`999e1628 : nt!KiExecuteAllDpcs+0x1b0 fffff802`9b24b9b0 fffff802`9995e7ea : fffff802`99aed180 fffff802`99aed180 fffff802`99b54a00 ffffe000`720dc080 : nt!KiRetireDpcList+0xdb fffff802`9b24bc60 00000000`00000000 : fffff802`9b24c000 fffff802`9b246000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: SnakeEyes+1abe fffff800`6c49aabe 8a05682b0000 mov al,byte ptr [snakeEyes+0x462c (fffff800`6c49d62c)] SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: SnakeEyes+1abe FOLLOWUP_NAME: MachineOwner MODULE_NAME: SnakeEyes IMAGE_NAME: SnakeEyes.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5046e3ae FAILURE_BUCKET_ID: 0x1E_c0000047_SnakeEyes+1abe BUCKET_ID: 0x1E_c0000047_SnakeEyes+1abe ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x1e_c0000047_snakeeyes+1abe FAILURE_ID_HASH: {cae96842-2066-7e0e-cf76-7e3f5ef52622} Followup: MachineOwner --------- Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted October 9, 2014 Corsair Employee Share Posted October 9, 2014 There may be a conflict with the device Piccolo. Are you using Daemon Tools? If so, try this: http://www.sevenforums.com/bsod-help-support/296881-kmode-exception-not-handled.html Link to comment Share on other sites More sharing options...
Piccolo Posted October 9, 2014 Author Share Posted October 9, 2014 I am not using Daemon tools but I am using Power ISO, so I will try your fix and report back. Thank you. Link to comment Share on other sites More sharing options...
Piccolo Posted October 9, 2014 Author Share Posted October 9, 2014 No SPTD version was detected so I assume it is not installed and the issue is not related to that. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted October 9, 2014 Corsair Employee Share Posted October 9, 2014 Try the mouse on a different machine to see if it causes any issues as well. If it does, then we know the mouse may have an issue and we'll replace it. Otherwise, it may be system specific. Link to comment Share on other sites More sharing options...
Piccolo Posted October 9, 2014 Author Share Posted October 9, 2014 Try the mouse on a different machine to see if it causes any issues as well. If it does, then we know the mouse may have an issue and we'll replace it. Otherwise, it may be system specific. I believe it may be 8.1 related somehow. I've been using the mouse for a couple months now on Windows 7 without any problems but recently did a fresh install to Window 8.1 and now have the problem. I'm going to do a removal and fresh install of the M65 software and drivers and will see if something during the install process went wrong. Again, thanks for the help. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted October 9, 2014 Corsair Employee Share Posted October 9, 2014 Thanks Piccolo, please keep me informed. Also, have you tried switching USB ports? Are you using 2.0 or 3.0? Did you also check to ensure you have the latest BIOS too? I see a lot of BIOS updates improve USB compatibility so if you haven't, its a good place to start. Link to comment Share on other sites More sharing options...
Piccolo Posted October 9, 2014 Author Share Posted October 9, 2014 Hello James, All of my hardware has the latest updates and drivers as this is a brand new build. The USB ports are 3.0 but there are 2.0 ports as well that I can try if the issue reoccurs. I just did a remove/reinstall of the drivers and will see if there's a difference. The crash sometimes occurs only once a day so it may be a while before I can fully test for issues, but I will report back when I can. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted October 10, 2014 Corsair Employee Share Posted October 10, 2014 Thanks again Piccolo. Feel free to PM me your findings too. Link to comment Share on other sites More sharing options...
ken27238 Posted October 13, 2014 Share Posted October 13, 2014 Hi everyone, first time poster. I too have the BSOD issue but it happens to me at the exact same time down to the second. 9:01:52 EST. But I seem to have fixed it. I had my M65 plugged in directly to my computer because I updated the firmware. 2 days ago I plugged it into the USB passthrough on my K70 and that's when it started BSODing. today I plugged it into my computer directly and it did not BSOD today that that time. Link to comment Share on other sites More sharing options...
Piccolo Posted October 16, 2014 Author Share Posted October 16, 2014 Just a quick update. After uninstalling the drivers and then re-installing it appears to have corrected the issue. I have not had a BSOD since then. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted October 16, 2014 Corsair Employee Share Posted October 16, 2014 @Piccolo, glad to hear you got the issue resolved. @Ken, that is a very specific analysis. Did you ever figure out why it only happens at that time? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.