Solved BSOD on Skyrim 0x0000001e

[xnyk]

I got a BSOD on skyrim.
Files attached here...

http://www.sevenforums.com/crashes-debugging/207384-bsod-i-just-got-whilst-wow.html

that's what happened last time (files also attached there). I think it's my mouse, that's what i was told last time, but this time it was from a different location I think. I don't know though, I'm stupid when it comes to tech stuff.

 

[zigzag3143]

Why did you start second thread?

Not your mouse, your Mcaffee.


I do notice McAffee which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST!

http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

Microsoft Security Essentials - Free Antivirus for Windows

 

[xnyk]

Oh I don't know, I just thought that's how it was. Also, the first BSOD was from mcafee as well? I payed for a year though which blows...

 

[zigzag3143]

Oh I don't know, I just thought that's how it was. Also, the first BSOD was from mcafee as well? I payed for a year though which blows...

No idea, There was only one dmp in the uploaded file.

 

[xnyk]

oh i've only gotten a BSOD twice and they both had the same error code..

 

[writhziden]

oh i've only gotten a BSOD twice and they both had the same error code..

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xnyk\Windows_NT6_BSOD_jcgriff2\011312-19375-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`03664000 PsLoadedModuleList = 0xfffff800`038a9670
Debug session time: Fri Jan 13 13:55:07.540 2012 (UTC - 7:00)
System Uptime: 0 days 2:24:09.430
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 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_0_Mo3Fltr+5f8

BUCKET_ID:  X64_0x1E_0_Mo3Fltr+5f8

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

0: kd> lmvm Mo3Fltr
start             end                 module name
fffff880`06f93000 fffff880`06f96200   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

Yeah, both of your crashes point toward your mouse. I'm guessing the driver was re-installed.

If you continue to have crashes without McAfee installed (zigzag3143 is right that McAfee is a known cause of BSODs on some systems), you will need to delete all remnants of the mouse driver on your system so Windows cannot install the driver on startup. You will also need to change the configuration of how driver software is installed so it does not install through Windows updates. To do so, see how to Disable Automatically Installing a Driver on Startup (the Realtek portion does not apply to you, but the steps do for the mouse driver Mo3Fltr.sys).