Blues Screen Can't Figure it out

[burn14me]

There is a specific set of circumstances which results in a BSoD. I have to be logged in as administrator and then one of my accounts assigned either to my wife of my daughter is logged in while my admin account is still logged in. So both accounts are logged in. Then the second account is logged out. The admin account which is still logged in is reactivated. Then within a few minutes Blue screen.

 

[zigzag3143]

There is a specific set of circumstances which results in a BSoD. I have to be logged in as administrator and then one of my accounts assigned either to my wife of my daughter is logged in while my admin account is still logged in. So both accounts are logged in. Then the second account is logged out. The admin account which is still logged in is reactivated. Then within a few minutes Blue screen.

My first recommedation is to remove symantec and replace it with Microsoft Security essentials.

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/

Second your gaming mouse is being blamed. I would re-install it.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder\120909-31262-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0301a000 PsLoadedModuleList = 0xfffff800`03257e50
Debug session time: Wed Dec  9 19:49:23.238 2009 (GMT-5)
System Uptime: 0 days 15:30:27.861
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading 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
---------

1: 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: 
+612a952f03b1df54
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003083c2e to fffff8000308bed0

STACK_TEXT:  
fffff880`02f1ac88 fffff800`03083c2e : 00000000`00000100 00000000`00000000 fffff880`02f1b490 fffff800`030b8e28 : nt!KeBugCheck
fffff880`02f1ac90 fffff800`030b1bed : fffff800`03298c24 fffff800`031d1a3c fffff800`0301a000 fffff880`02f1b3f0 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1acc0 fffff800`030b9250 : fffff800`031d9b5c fffff880`02f1ad38 fffff880`02f1b3f0 fffff800`0301a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1acf0 fffff800`030ba82e : fffff880`02f1b3f0 fffff880`02f1b490 fffff880`00000001 fffff800`030985e0 : nt!RtlDispatchException+0x410
fffff880`02f1b3d0 fffff800`030e87c2 : 00000000`00000002 fffff800`035f9e15 fffffa80`07761000 00000000`00000000 : nt!RtlRaiseStatus+0x4e
fffff880`02f1b970 fffff880`061965f8 : fffffa80`06a18dc0 fffffa80`00000000 fffffa80`0a67d0e0 fffffa80`0836d500 : nt! ?? ::FNODOBFM::`string'+0xf63c
fffff880`02f1b9f0 fffffa80`06a18dc0 : fffffa80`00000000 fffffa80`0a67d0e0 fffffa80`0836d500 00000000`00000006 : Mo3Fltr+0x5f8
fffff880`02f1b9f8 fffffa80`00000000 : fffffa80`0a67d0e0 fffffa80`0836d500 00000000`00000006 fffff800`035f9354 : 0xfffffa80`06a18dc0
fffff880`02f1ba00 fffffa80`0a67d0e0 : fffffa80`0836d500 00000000`00000006 fffff800`035f9354 00000000`00000000 : 0xfffffa80`00000000
fffff880`02f1ba08 fffffa80`0836d500 : 00000000`00000006 fffff800`035f9354 00000000`00000000 fffffa80`0836d380 : 0xfffffa80`0a67d0e0
fffff880`02f1ba10 00000000`00000006 : fffff800`035f9354 00000000`00000000 fffffa80`0836d380 fffffa80`06a18dc0 : 0xfffffa80`0836d500
fffff880`02f1ba18 fffff800`035f9354 : 00000000`00000000 fffffa80`0836d380 fffffa80`06a18dc0 fffff800`0308e516 : 0x6
fffff880`02f1ba20 00000000`00000000 : fffffa80`0a469ea0 00000000`00000000 00000000`000007ff 00000000`00000050 : hal!HalpDmaFreeMapRegisters+0x30


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Mo3Fltr+5f8
fffff880`061965f8 ??              ???

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_Mo3Fltr+5f8

BUCKET_ID:  X64_0x1E_Mo3Fltr+5f8

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