BSOD i just got whilst on WoW

BcCode 1e it said

I have the attachments on here. If there's anything else I need to post, lemme know.

the asdasd.txt is what is in the blue screen viewer thing when i hate save as text file.. i didnt know if i should add it or not, so i did.

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xnyk\Windows_NT6_BSOD_jcgriff2\010912-21933-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03656000 PsLoadedModuleList = 0xfffff800`0389b670
Debug session time: Mon Jan  9 14:35:55.378 2012 (UTC - 7:00)
System Uptime: 0 days 1:06:54.268
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Unable to load image \SystemRoot\system32\drivers\Mo3Fltr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Mo3Fltr.sys
*** ERROR: Module load completed but symbols could not be loaded for Mo3Fltr.sys
Probably caused by : Mo3Fltr.sys ( Mo3Fltr+5f8 )

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: 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:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6130613031313361
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800036ca5fe to fffff800036d2c10

STACK_TEXT:  
fffff800`00b9ba88 fffff800`036ca5fe : 00000000`00000000 fffffa80`075040c0 fffff800`00b9c290 fffff800`036fe830 : nt!KeBugCheck
fffff800`00b9ba90 fffff800`036fe4fd : fffff800`038dc71c fffff800`03819c30 fffff800`03656000 fffff800`00b9c1f0 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9bac0 fffff800`036fd2d5 : fffff800`0381d0fc fffff800`00b9bb38 fffff800`00b9c1f0 fffff800`03656000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9baf0 fffff800`037005c6 : fffff800`00b9c1f0 fffff800`00b9c290 00000000`00000001 00000000`0000000f : nt!RtlDispatchException+0x415
fffff800`00b9c1d0 fffff800`0368d70a : fffff800`00b96080 00000000`00000022 00000000`00000000 00000000`00000000 : nt!RtlRaiseStatus+0x4e
fffff800`00b9c770 fffff880`09c715f8 : fffffa80`07479dc0 00000000`00000000 fffffa80`0b9b2750 fffffa80`0c240900 : nt! ?? ::FNODOBFM::`string'+0xf5a9
fffff800`00b9c7f0 fffffa80`07479dc0 : 00000000`00000000 fffffa80`0b9b2750 fffffa80`0c240900 fffffa80`0752d940 : Mo3Fltr+0x5f8
fffff800`00b9c7f8 00000000`00000000 : fffffa80`0b9b2750 fffffa80`0c240900 fffffa80`0752d940 fffff880`0585c3b4 : 0xfffffa80`07479dc0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Mo3Fltr+5f8
fffff880`09c715f8 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Mo3Fltr+5f8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Mo3Fltr

IMAGE_NAME:  Mo3Fltr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48d1c1fd

FAILURE_BUCKET_ID:  X64_0x1E_0_Mo3Fltr+5f8

BUCKET_ID:  X64_0x1E_0_Mo3Fltr+5f8

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

0: kd> lmvm Mo3Fltr
start             end                 module name
fffff880`09c71000 fffff880`09c74200   Mo3Fltr  T (no symbols)           
    Loaded symbol image file: Mo3Fltr.sys
    Image path: \SystemRoot\system32\drivers\Mo3Fltr.sys
    Image name: Mo3Fltr.sys
    Timestamp:        Wed Sep 17 20:50:37 2008 (48D1C1FD)
    CheckSum:         0000E60E
    ImageSize:        00003200
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The crash was due to your gaming mouse. The driver appears to be pre-Windows 7, so please update it. If you are unable to update it, replace it with hardware that is up to date. To check if it is up to date, use the following steps.

1. Click Start Menu
2. Right click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Expand Human Interface Devices, Mice and other pointing devices, or Sound video and game controllers to find your mouse
6. Right click on the mouse and click Properties
7. Check the Driver Date in the Driver tab.

If the date is before July, 2009, the driver is not necessarily compatible with Windows 7. You could try installing it with the steps in Drivers - Install Vista Drivers on Windows 7

it does say it's from 2008 but there's no updates available for it. what do i do?

edit: nvm i guess if it happens again i will just uninstall the drivers

xnyk said:

it does say it's from 2008 but there's no updates available for it. what do i do?

edit: nvm i guess if it happens again i will just uninstall the drivers

Good plan. I know most gaming mouses will revert to just being regular mouses without the gaming software. I imagine yours functions as a normal mouse if the drivers are uninstalled?

Any luck with the gaming mouse drivers after uninstall?