Jump to content

Windows 10 build 1809 detects Malwarebytes as "Stopped Working" at reboot.


Recommended Posts

That is, if I reboot the system, it will show up in reliability monitor as "malwarebytes service stopped working". Seems to be caused by the self protection module. 

Logs are attached.

The error in the monitor is as follows:

Problem Event Name:    BEX64
Application Name:    mbamservice.exe
Application Version:    3.2.0.704
Application Timestamp:    5b9acf90
Fault Module Name:    SelfProtectionSdk.dll
Fault Module Version:    3.0.0.360
Fault Module Timestamp:    5b995ba2
Exception Offset:    000000000014e2a9
Exception Code:    c0000409
Exception Data:    0000000000000007
OS Version:    10.0.17763.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    b4ad
Additional Information 2:    b4ad75583f5312f04a624f3f83775fbc
Additional Information 3:    7069
Additional Information 4:    7069ba0537579f6d877652ad45a05209

 

mbst-grab-results.zip

Link to post
Share on other sites
  • Staff

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes 3 Help forum.

 

If you are having technical issues with our Windows product, please do the following: 

Spoiler

If you haven’t already done so, please run the Malwarebytes Support Tool and then attach the logs in your next reply:

NOTE: The tools and the information obtained is safe and not harmful to your privacy or your computer, please allow the programs to run if blocked by your system.

  • Download Malwarebytes Support Tool
  • Once the file is downloaded, open your Downloads folder/location of the downloaded file
  • Double-click mb-support-X.X.X.XXXX.exe to run the program
    • You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Click Yes to consent.
  • Place a checkmark next to Accept License Agreement and click Next
  • You will be presented with a page stating, "Welcome to the Malwarebytes Support Tool!"
  • Click the Advanced Options link

    welcome mbst.png
     
  • Click the Gather Logs button

    gatherlogs.png
     
  • A progress bar will appear and the program will proceed to gather troubleshooting information from your computer
  • Upon completion, click OK
  • A file named mbst-grab-results.zip will be saved to your Desktop
  • Please attach the file in your next reply. Before submitting your reply, be sure to enable "Notify me of replies" like so:

     notify me.jpeg  


    Click "Reveal Hidden Contents" below for details on how to attach a file:
     
    Spoiler

    To save attachments, please click the link as shown below. You can click and drag the files to this bar or you can click the choose files, then browse to where your files are located, select them and click the Open button.

    mb_attach.jpg.220985d559e943927cbe3c078b
     

One of our experts will be able to assist you shortly.

 

If you are having licensing issues, please do the following: 

Spoiler

For any of these issues:

  • Renewals
  • Refunds (including double billing)
  • Cancellations
  • Update Billing Info
  • Multiple Transactions
  • Consumer Purchases
  • Transaction Receipt

Please contact our support team at https://support.malwarebytes.com/community/consumer/pages/contact-us to get help

If you need help looking up your license details, please head here: https://support.malwarebytes.com/docs/DOC-1264 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

Link to post
Share on other sites
  • Staff

That's correct.  In fact, you can test this yourself if you wish.  Aside from verifying that the Chameleon driver is running, you can also try terminating any of Malwarebytes' processes via any tool such as Task Manager and you should receive an "access denied" error from Windows (you won't see this error if self-protection is disabled and it will allow you to terminate them if self-protection isn't running which you may also verify if you wish). 

Link to post
Share on other sites
  • Staff

Yes, it should be the same for all those affected.  While I don't know all of the technical details, it appears that there's a problem with the driver not shutting down properly when the shutdown command is called which results in the error, however I haven't seen any reports so far of it impacting performance or stability in any way so it seems to be a minor issue and I expect it will be corrected in the next release (the affected version is the recently released 3.6.1).

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.