New
#1
BSOD error 0x000000E1
I randomly get BSOD's with the error 0x00000E1 and when im playing games.
I randomly get BSOD's with the error 0x00000E1 and when im playing games.
Welcome
All your dumps show Mo3Fltr.sys as the cause. It is part of the Asus PCProbe program, and is notorious for causing crashes.
I suggest removing it completely using Programs and Features. If the BSODs persist, please continue to upload the dmps.
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Yusra\Downloads\saifoo\SF_15-09-2012\091512-22152-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*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 Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030 Machine Name: Kernel base = 0xfffff800`03658000 PsLoadedModuleList = 0xfffff800`0389c670 Debug session time: Sat Sep 15 14:26:15.353 2012 (UTC + 6:00) System Uptime: 1 days 0:46:55.101 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 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.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: +3739316361303932 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 fffff800036cebbe to fffff800036d7190 STACK_TEXT: fffff800`00b9bb38 fffff800`036cebbe : 00000000`00328cc9 fffffa80`094ab000 fffff800`00b9c340 fffff800`03702160 : nt!KeBugCheck fffff800`00b9bb40 fffff800`03701e2d : fffff800`038dd770 fffff800`0381a2f0 fffff800`03658000 fffff800`00b9c2a0 : nt!KiKernelCalloutExceptionHandler+0xe fffff800`00b9bb70 fffff800`03700c05 : fffff800`0381dfac fffff800`00b9bbe8 fffff800`00b9c2a0 fffff800`03658000 : nt!RtlpExecuteHandlerForException+0xd fffff800`00b9bba0 fffff800`03703efe : fffff800`00b9c2a0 fffff800`00b9c340 00000000`00000001 00000000`00000001 : nt!RtlDispatchException+0x415 fffff800`00b9c280 fffff800`0368cd7a : fffffa80`08140050 fffffa80`09aa9010 00000000`00000000 fffffa80`08140a18 : nt!RtlRaiseStatus+0x4e fffff800`00b9c820 fffff880`0925c5f8 : fffffa80`09ab1460 00000000`00000000 fffffa80`094523c0 fffffa80`0986ff00 : nt! ?? ::FNODOBFM::`string'+0xf5a9 fffff800`00b9c8a0 fffffa80`09ab1460 : 00000000`00000000 fffffa80`094523c0 fffffa80`0986ff00 fffffa80`081401a0 : Mo3Fltr+0x5f8 fffff800`00b9c8a8 00000000`00000000 : fffffa80`094523c0 fffffa80`0986ff00 fffffa80`081401a0 fffff880`06c7f78f : 0xfffffa80`09ab1460 STACK_COMMAND: kb FOLLOWUP_IP: Mo3Fltr+5f8 fffff880`0925c5f8 ?? ??? 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`0925c000 fffff880`0925f200 Mo3Fltr T (no symbols) Loaded symbol image file: Mo3Fltr.sys Image path: \SystemRoot\system32\drivers\Mo3Fltr.sys Image name: Mo3Fltr.sys Timestamp: Thu Sep 18 08:50:37 2008 (48D1C1FD) CheckSum: 0000E60E ImageSize: 00003200 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4