Many different BSOD KMODE_EXCEPTION_NOT_HANDLED 1E

AVPMARINE · 17 Jun 2014

Hi guys I have recently built this new PC using my old hard drives and GPU. I have been experiencing many BSOD which I have been googling for fixes for days and new ones just keep popping up I'm out of ideas here any help would be greatly appreciated.

Things I have done - Reinstalled Windows 7 on SSD.
Reinstalled Windows 7 on Hard Drive.
Windows repair multiple times and many Windows 7 reinstall.
Uninstalled and reinstalled graphics drivers and tried other drivers.
Installed all drivers from motherboard disk.
Installed all Windows 7 updates and running service pack 1.
Disabled / enabled XMP in motherboard bios / manually set timing and voltage on ram
Checked temperature on parts - Motherboard 20-25c GPU 30-70c CPU 20-50
Updated devices in Device Manager.
Re seated RAM / tried with one stick and still BSOD.

Thanks for the help. I have attached my crash dumps below!

PeregrineX · 17 Jun 2014

The BSOD is caused by your Corsair M65 Gaming Mouse driver.

Code:

*******************************************************************************
*                                                                             *
*                        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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for SnakeEyes.sys
*** ERROR: Module load completed but symbols could not be loaded for SnakeEyes.sys
*** WARNING: Unable to verify timestamp for iusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3hub.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF800048D2FB0

LAST_CONTROL_TRANSFER:  from fffff800032bf5be to fffff800032c7b90

STACK_TEXT:  
fffff800`048cb8f8 fffff800`032bf5be : 00000002`00000000 00000000`00000000 fffff800`048cc100 fffff800`032f2a90 : nt!KeBugCheck
fffff800`048cb900 fffff800`032f275d : fffff800`034d6380 fffff800`03413260 fffff800`03252000 fffff800`048cc060 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`048cb930 fffff800`032f1535 : fffff800`03417038 fffff800`048cb9a8 fffff800`048cc060 fffff800`03252000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`048cb960 fffff800`032f4832 : fffff800`048cc060 fffff800`048cc100 fffffa80`00000001 fffffa80`00000003 : nt!RtlDispatchException+0x415
fffff800`048cc040 fffff800`0327d98a : fffffa80`087e5000 fffff880`0f23d74e fffffa80`093ae9f0 fffff880`0f23d74e : nt!RtlRaiseStatus+0x4e
fffff800`048cc5e0 fffff880`053e5abe : fffffa80`08f77d40 fffffa80`00000000 fffffa80`090f8880 fffff880`04ca1200 : nt! ?? ::FNODOBFM::`string'+0xf429
fffff800`048cc660 fffffa80`08f77d40 : fffffa80`00000000 fffffa80`090f8880 fffff880`04ca1200 fffffa80`07df7790 : SnakeEyes+0x1abe
fffff800`048cc668 fffffa80`00000000 : fffffa80`090f8880 fffff880`04ca1200 fffffa80`07df7790 00000000`00000000 : 0xfffffa80`08f77d40
fffff800`048cc670 fffffa80`090f8880 : fffff880`04ca1200 fffffa80`07df7790 00000000`00000000 fffffa80`07ed5010 : 0xfffffa80`00000000
fffff800`048cc678 fffff880`04ca1200 : fffffa80`07df7790 00000000`00000000 fffffa80`07ed5010 fffff880`01401c27 : 0xfffffa80`090f8880
fffff800`048cc680 fffffa80`07df7790 : 00000000`00000000 fffffa80`07ed5010 fffff880`01401c27 00000000`00000000 : iusb3hub+0x19200
fffff800`048cc688 00000000`00000000 : fffffa80`07ed5010 fffff880`01401c27 00000000`00000000 00000000`00000000 : 0xfffffa80`07df7790


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SnakeEyes+1abe
fffff880`053e5abe ??              ???

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:  X64_0x1E_SnakeEyes+1abe

BUCKET_ID:  X64_0x1E_SnakeEyes+1abe

Followup: MachineOwner
---------

I see that the driver is outdated:

Code:

SnakeEyes    Corsair M65 Gaming Mou Kernel        9/5/2012 3:31:26 PM

Please visit the Corsair Website to download the latest version of the driver.

Best of luck,

PeregrineX