Solved Kmode exception not handled

[Hisophonic]

Ok ive just had this crash a few mins ago and i ran WhoCrashed which said this:

On Wed 10/07/2013 17:00:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071013-25662-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Arc]

If you want to get it debugged, you need to post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[Hisophonic]

I think i did this properly
Here is the zip file with the required files

 

[Arc]

The BSOD is caused by Corsair M65 Gaming Mouse driver (c:\windows\system32\drivers\snakeeyes.sys).

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for SnakeEyes.sys
*** ERROR: Module load completed but symbols could not be loaded for SnakeEyes.sys

Probably caused by : SnakeEyes.sys ( SnakeEyes+1abe )

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

Update the driver from the manufacturer's website.Vengeance® M65 FPS Laser Gaming Mouse

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

 

[Hisophonic]

Seems to run fine.
Thanks for the help.

 

[Arc]

Good to know

For any further issue, let us know

 

[Hisophonic]

Will do thanks