BlueScreen BCCode 1e


  1. Posts : 3
    Windows 7 x64
       #1

    BlueScreen BCCode 1e


    Hello,

    I upgraded to Windows 7 x64 from 32-bit vista three days ago. As I was reinstalling some programs I got bluescreened a couple times so googled the error and saw something about updating video card drivers (I had forgot about those). So I updated my card drivers and the problem seemed to go away. However, I just got the same BlueScreen BCCode 1e again today so decided to look for some expert advice.

    Here's the error report and attached are the .dmp files.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.48
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1e
    BCP1: 0000000000000000
    BCP2: 0000000000000000
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1


    Thanks for your help,

    Frans
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Welcome!

    It looks like Mo3Fltr.sys is 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.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp2_DumpFiles.zip\042010-23836-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\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.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c95e50
    Debug session time: Tue Apr 20 16:13:12.947 2010 (GMT-4)
    System Uptime: 0 days 3:44:59.023
    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: 
    +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 fffff80002ac032e to fffff80002ac85d0
    
    STACK_TEXT:  
    fffff800`03fd3c88 fffff800`02ac032e : fffffa80`00000001 fffff800`02c6d5f8 fffff800`03fd4490 fffff800`02af5524 : nt!KeBugCheck
    fffff800`03fd3c90 fffff800`02aee2ed : fffff800`02cd6b88 fffff800`02c0fa40 fffff800`02a58000 fffff800`03fd43f0 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff800`03fd3cc0 fffff800`02af5950 : fffff800`02c17b24 fffff800`03fd3d38 fffff800`03fd43f0 fffff800`02a58000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`03fd3cf0 fffff800`02af6f2e : fffff800`03fd43f0 fffff800`03fd4490 fffff800`00000001 00000000`00000001 : nt!RtlDispatchException+0x410
    fffff800`03fd43d0 fffff800`02b24b52 : 00000000`00000002 fffff800`02a11e15 fffffa80`04f8c100 00000000`00000000 : nt!RtlRaiseStatus+0x4e
    fffff800`03fd4970 fffff880`04f5d5f8 : fffffa80`053abdc0 fffffa80`00000000 fffffa80`052360e0 fffffa80`04bd5e00 : nt! ?? ::FNODOBFM::`string'+0xf5fc
    fffff800`03fd49f0 fffffa80`053abdc0 : fffffa80`00000000 fffffa80`052360e0 fffffa80`04bd5e00 00000000`00000006 : Mo3Fltr+0x5f8
    fffff800`03fd49f8 fffffa80`00000000 : fffffa80`052360e0 fffffa80`04bd5e00 00000000`00000006 fffff800`02a11354 : 0xfffffa80`053abdc0
    fffff800`03fd4a00 fffffa80`052360e0 : fffffa80`04bd5e00 00000000`00000006 fffff800`02a11354 00000000`00000000 : 0xfffffa80`00000000
    fffff800`03fd4a08 fffffa80`04bd5e00 : 00000000`00000006 fffff800`02a11354 00000000`00000000 fffffa80`04bd5c60 : 0xfffffa80`052360e0
    fffff800`03fd4a10 00000000`00000006 : fffff800`02a11354 00000000`00000000 fffffa80`04bd5c60 fffffa80`053abdc0 : 0xfffffa80`04bd5e00
    fffff800`03fd4a18 fffff800`02a11354 : 00000000`00000000 fffffa80`04bd5c60 fffffa80`053abdc0 fffff800`02acac26 : 0x6
    fffff800`03fd4a20 00000000`00000000 : fffffa80`04c12970 00000000`00000000 00000000`000007ff 00000000`00000050 : hal!HalpDmaFreeMapRegisters+0x30
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    Mo3Fltr+5f8
    fffff880`04f5d5f8 ??              ???
    
    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
    ---------
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #3

    fkouwen said:
    Hello,

    I upgraded to Windows 7 x64 from 32-bit vista three days ago. As I was reinstalling some programs I got bluescreened a couple times so googled the error and saw something about updating video card drivers (I had forgot about those). So I updated my card drivers and the problem seemed to go away. However, I just got the same BlueScreen BCCode 1e again today so decided to look for some expert advice.

    Here's the error report and attached are the .dmp files.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.48
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1e
    BCP1: 0000000000000000
    BCP2: 0000000000000000
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1


    Thanks for your help,

    Frans

    All three of these were caused by Mo3fltr.sys which is your gaming mouse driver. I would download a new copy and install

    Let us know if you need help

    Ken
      My Computer


  4. Posts : 3
    Windows 7 x64
    Thread Starter
       #4

    Thank you for a quick response, that program looked like bad news as soon as I ran it.

    Unfortunately I thought I had removed it already and it isn't showing up in my Programs and Features uninstall list. Even when I search for the PCProbe it doesn't show up; any suggestions for how to find it?

    Frans

    Edit: Just got that second post, will reinstall mouse drivers and let you know if the problem persists.
    Last edited by fkouwen; 20 Apr 2010 at 15:42. Reason: More info
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #5

    Looks like Ken was right; it does look as if Mo3Fltr.sys is the mouse driver, not the Asus PC Probe.

    Go to C:\Windows\System32\Drivers, and delete Mo3Fltr.sys.

    Let us know how it works out.
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    JK, its not about being right, but team work. thanks for looking, +rep for your dedication


    Ken
      My Computer


  7. Posts : 3
    Windows 7 x64
    Thread Starter
       #7

    Thank you both,

    I reinstalled the mouse drivers, then deleted the .sys file just in case. Weird thing was all the other drivers in my system32 folder had their date modified as at least a year later than that one. Am I right in assuming this means it wasn't being updated and that may have been the reason it was causing a conflict?

    Frans
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:58.
Find Us