Jump to content

mwac.sys BSOD multiple times


Recommended Posts

  • Staff

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes for Windows 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.

  1. Download Malwarebytes Support Tool
  2. Once the file is downloaded, open your Downloads folder/location of the downloaded file
  3. 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.
  4. Place a checkmark next to Accept License Agreement and click Next
  5. You will be presented with a page stating, "Get Started!"
  6. Click the Advanced tab on the left column

    mbst_get_started.jpg
     
  7. Click the Gather Logs button

    mbst_advanced_gather_logs.jpg
     
  8. A progress bar will appear and the program will proceed with getting logs from your computer

    mbst_getting_logs.jpg
     
  9. Upon completion, a file named mbst-grab-results.zip will be found on your Desktop. Click OK

    mbst_log_saved_desktop.jpg
     
  10. 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/hc/en-us/requests/new to get help

If you need help looking up your license details, please head here: Find my premium license key

 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

 

Link to post
Share on other sites

  • Staff

Greetings,

I'm sorry that you are experiencing problems with the software but hopefully the issue will be resolved soon.  In the meantime, if you haven't already seen it, I would recommend taking a look at this topic, in particular this post and the subsequent conversation that follows there.  It appears that the Malwarebytes Developers are aware of the issue and are investigating a fix which will be included in a future release, though unfortunately I have no ETA on when the fix/release will be available.

You have a couple of options to work around the issue, assuming it is the same one being reported in the other thread I linked to, which are covered in the post in the second link I posted above.  With that said, I looked at your logs and you appear to be running Avast AV and I am aware of some recent reports of issues with recent versions of Avast and Malwarebytes on some systems so it may be worth testing to see if disabling or removing Avast resolves the issue, and if it does, try to narrow down the issue to a single module/component of Avast to see if just that single component can be disabled or if exclusions can be created in Avast for Malwarebytes' files and processes to prevent the BSODs from occurring.  The list of items to exclude for Malwarebytes can be found in this support article and it may also prove helpful to exclude Avast's primary program folder (likely located under C:\Program Files and/or C:\Program Files (x86)) along with Avast's primary data folder which is likely located under C:\ProgramData from Malwarebytes using the method described under the Allow a file or folder section of this support article.

Please let us know how it goes and if you are able to successfully determine the cause of the BSODs.

Thanks

Link to post
Share on other sites

  • Staff

Thank you for the dump. We're reviewing the data now.

In the meantime, could you provide some additional information:

  • How often does the BSOD occur? Are you able to reproduce it on-demand?
  • Are there particular triggers of it or is it seemingly random? Any potential correlation with certain activities that result in it occurring?
  • When the BSODs occurred previously, were you connected to a VPN?
  • When did this first start occurring? Were any significant changes made around this time?


Are you able to temporarily uninstall Avast, reboot and check if the BSOD persists? This is always the best approach to ruling out (or confirming) if third-party Anti-Virus software is involved.

Edited by LiquidTension
Link to post
Share on other sites

How often does the BSOD occur? Are you able to reproduce it on-demand?

  • Most of my crashes have been when playing Final Fantasy XIV. With how long the crash reporting takes each time it happens, I have not tried different scenarios.

Are there particular triggers of it or is it seemingly random? Any potential correlation with certain activities that result in it occurring?

  • The last three times I think it has been when I tab out of FFXIV and open another program.

When the BSODs occurred previously, were you connected to a VPN?

  • Nope, no VPN. I have recently started using a Pi-hole.

When did this first start occurring? Were any significant changes made around this time?

  • I don't remember the date I started using a Pi-hole, but the first minidump was on 2/12/2020 so that could be around the time I changed my computer's DNS lookup.
Link to post
Share on other sites

  • Staff

Thank you for this information.

The dump file provided indicates the MWAC driver is crashing due to one of its internal data structures being corrupted. Unfortunately, there's not enough information to pinpoint the cause but this is typically indicative of interference from other installed software.

From the logs, we can see you also have GlassWire installed, which is another potential factor involved.

Could you try performing a clean boot and see if the issue is still exhibited.

https://support.microsoft.com/en-gb/help/929135/how-to-perform-a-clean-boot-in-windows

When performing it, ensure Malwarebytes Service is left as checked/enabled. Afterwards, please check if the BSOD occurs using the same scenario.

-----

Regarding the changes made to use Pi-hole - would it be possible to temporarily reverse these changes for the purpose of troubleshooting and check if this has any impact on the issue?

Edited by LiquidTension
Link to post
Share on other sites

Hi @LiquidTension,

I found the app that was causing all my BSOD's. I've been turning things on and off trying different things and nothing changed what was happening. However, whenever I run my app  with Malwarebytes and Final Fantasy XIV running after a time something triggers in the memory and I get my BSOD. As long as I run my app, do what I need to do, and then close said app, I can avoid the whole system halting. It's not the ideal solution but at least it works.

I tried removing the Pi-hole from the equation as well and nothing changed. The app keeps causing the BSOD.

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
 Share

  • 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.