Results 1 to 13 of 13
  1. #1
    3 Star Lounger
    Join Date
    Dec 2009
    Location
    South Carolina
    Posts
    222
    Thanks
    76
    Thanked 1 Time in 1 Post

    WE crashing more in the last 6 mo that in 20+ yr of using Win.

    Hi

    W7 pro 32 bit on desktop & laptop.

    Below is an error I have been getting from WE more in the last 6 mo that in 20+ yr of using Win.

    I was only copying 2, 1.5 MB folders to a USB Dr while deleting 2, 1.5 MB folders on my PC's HD. Part the way thru
    this error pop-up appeared:

    Any reason this happened and appears to be re-occurring. W7 Pro was freshly re-installed in Dec, 2015.

    Problem signature:
    Problem Event Name: BEX
    Application Name: Explorer.EXE
    Application Version: 6.1.7601.17567
    Application Timestamp: 4d6727a7
    Fault Module Name: mbamext.dll
    Fault Module Version: 3.1.1.0
    Fault Module Timestamp: 56cde4b9
    Exception Offset: 0001ed16
    Exception Code: c0000417
    Exception Data: 00000000
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 1033
    Additional Information 1: 984c
    Additional Information 2: 984ccad22518274038883c008b4d6d0a
    Additional Information 3: ba1b
    Additional Information 4: ba1b31f3f5d659b34f211f00d5f81a70

    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    cheers,

    klxdrt

  2. #2
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,444
    Thanks
    52
    Thanked 1,028 Times in 956 Posts
    I'd do some error checking / correction.
    1. Open a Command Prompt and type "CHKDSK /f c:" and follow the prompts to check the file system.
    2. Open a Command Prompt and type "sfc /scannow" to check / repair Windows.

    cheers, Paul

  3. #3
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    6,969
    Thanks
    159
    Thanked 918 Times in 876 Posts
    The fault seems to be caused by MBAM.

    Is it the Pro or free version you are using ?

    Usually a reinstall of a program when it gets buggy can resolve.

    Use this MBAM uninstaller, reinstall after the reboot to see if the error reoccurs.

    https://support.malwarebytes.org/cus...are-?b_id=6438

  4. #4
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,629
    Thanks
    299
    Thanked 599 Times in 498 Posts
    MBAM > Settings > General settings > Explorer context menu entry > select no.

  5. #5
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    6,969
    Thanks
    159
    Thanked 918 Times in 876 Posts
    Quote Originally Posted by satrow View Post
    MBAM > Settings > General settings > Explorer context menu entry > select no.
    What exactly does that do when it is default set to Yes, Andy ?

  6. #6
    Super Moderator RetiredGeek's Avatar
    Join Date
    Mar 2004
    Location
    Manning, South Carolina
    Posts
    9,565
    Thanks
    384
    Thanked 1,480 Times in 1,346 Posts
    Sudo,

    It gets rid of the ShortCut to scan a file.

    ON:
    MBAMFESCM.PNG

    OFF:
    MBAMFESCMOFF.PNG

    HTH
    May the Forces of good computing be with you!

    RG

    PowerShell & VBA Rule!

    My Systems: Desktop Specs
    Laptop Specs

  7. The Following User Says Thank You to RetiredGeek For This Useful Post:

    Sudo15 (2016-05-11)

  8. #7
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,629
    Thanks
    299
    Thanked 599 Times in 498 Posts
    mbamext.dll = MBAM's context menu extension, the module that is 'blamed' for the Explorer crash.

  9. The Following User Says Thank You to satrow For This Useful Post:

    Sudo15 (2016-05-11)

  10. #8
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    6,969
    Thanks
    159
    Thanked 918 Times in 876 Posts
    While I can occasionally get an iexplore stopped responding, I think I've only ever had one WE crash with mine default set to Yes.

    That is now set at No, so hopefully no more crashes

  11. #9
    Silver Lounger RolandJS's Avatar
    Join Date
    Dec 2009
    Location
    Austin metro area TX USA
    Posts
    1,801
    Thanks
    101
    Thanked 135 Times in 132 Posts
    I'm offline today, what is WE? Windows Explorer, correct?
    "Take care of thy backups and thy restores shall take care of thee." Ben Franklin revisited.
    http://collegecafe.fr.yuku.com/forum...-Technologies/

  12. #10
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,629
    Thanks
    299
    Thanked 599 Times in 498 Posts
    Yes, Windows Explorer:

    Application Name: Explorer.EXE
    Application Version: 6.1.7601.17567
    Application Timestamp: 4d6727a7
    Fault Module Name: mbamext.dll
    The Exception Code: c0000417, indicates that "An invalid parameter was passed to a C runtime function". Not that it helps us mortals much.

  13. #11
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    6,969
    Thanks
    159
    Thanked 918 Times in 876 Posts
    Quote Originally Posted by satrow View Post
    Yes, Windows Explorer:

    The Exception Code: c0000417, indicates that "An invalid parameter was passed to a C runtime function". Not that it helps us mortals much.
    I came across that when I was researching the error code and figured that perhaps a reinstall may sort it.

    Wonder when the OP is getting back.....

  14. #12
    3 Star Lounger
    Join Date
    Dec 2009
    Location
    South Carolina
    Posts
    222
    Thanks
    76
    Thanked 1 Time in 1 Post
    Quote Originally Posted by RolandJS View Post
    I'm offline today, what is WE? Windows Explorer, correct?
    You got it> Windows Explorer

    klx

  15. #13
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,629
    Thanks
    299
    Thanked 599 Times in 498 Posts
    Well, as it happened (this time) during a small disk copy operation, perhaps an SFC/SCANNOW and chkdsk /f /r should be the first steps?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •