Windows 7: System Service Error BSO

*******************************************************************************
*                                                                             *
*                        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: 
+0
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 fffff800036d85fe to fffff800036e0c10

STACK_TEXT:  
fffff800`04e3ea88 fffff800`036d85fe : 00000000`00000000 00000000`00000000 fffff800`04e3f290 fffff800`0370c830 : nt!KeBugCheck
fffff800`04e3ea90 fffff800`0370c4fd : fffff800`038ea71c fffff800`03827c30 fffff800`03664000 fffff800`04e3f1f0 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`04e3eac0 fffff800`0370b2d5 : fffff800`0382b0fc fffff800`04e3eb38 fffff800`04e3f1f0 fffff800`03664000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`04e3eaf0 fffff800`0370e5c6 : fffff800`04e3f1f0 fffff800`04e3f290 00000000`00000001 00000000`0000000f : nt!RtlDispatchException+0x415
fffff800`04e3f1d0 fffff800`0369b70a : fffff800`04e39080 00000000`00000022 00000000`00000000 00000000`00000000 : nt!RtlRaiseStatus+0x4e
fffff800`04e3f770 fffff880`06f935f8 : fffffa80`0aac79b0 00000000`00000000 fffffa80`069bef20 fffffa80`0acdee00 : nt! ?? ::FNODOBFM::`string'+0xf5a9
fffff800`04e3f7f0 fffffa80`0aac79b0 : 00000000`00000000 fffffa80`069bef20 fffffa80`0acdee00 fffffa80`09a4d770 : Mo3Fltr+0x5f8
fffff800`04e3f7f8 00000000`00000000 : fffffa80`069bef20 fffffa80`0acdee00 fffffa80`09a4d770 fffff880`058ea3b4 : 0xfffffa80`0aac79b0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Mo3Fltr+5f8
fffff880`06f935f8 ??              ???

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