MalwareBytes crashing my computer

[rkay]

My computer crashed yesterday and after a reboot loop and looking at the srt file, I was able to determine the issue was with mbamswissarmy.sys file. The error message stated that the file was corrupt. I renamed the file and then windows was able to boot up. Malwarebytes indicated there was an error and asked me to reboot. I did and after the reboot, Malwarebytes indicated that it is running properly. The mbamswissarmy.sys file is still renamed. Is Malwarebytes working properly? I have a licensed version. 

My concern is that MalwareBytes states it is working properly but it is not using the mbamswissarmy.sys file? Any suggestions.

[Malwarebytes]

***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 done so already, please run these two tools 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.

• Farbar Recovery Scan Tool (FRST)
  1. Download FRST and save it to your desktop
     Note: You need to run the version compatible with your system. You can check here if you're not sure if your computer is 32-bit or 64-bit
  2. Double-click to run FRST and when the tool opens click "Yes" to the disclaimer
  3. Press the "Scan" button
  4. This will produce two files in the same location (directory) as FRST: FRST.txt and Addition.txt
     • Leave the log files in the current location, they will be automatically collected by mb-check once you complete the next set of instructions
• MB-Check
  1. Download MB-Check and save to your desktop
  2. Double-click to run MB-Check and within a few second the command window will open, press "Enter" to accept the EULA then click "OK" 
  3. This will produce one log file on your desktop: mb-check-results.zip
     • This file will include the FRST logs generated from the previous set of instructions
     • Attach this file to your forum post by clicking on the "Drag files here to attach, or choose files..." or simply drag the file to the attachment area

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

[exile360]

Greetings and welcome

This is a known issue however the Developers did attempt to reduce the likelihood of this issue occurring in a recent release of Malwarebytes 3 so first, please make certain you are using the latest version (currently 3.3 or if you have beta updates enabled, 3.4).  As long as MB3 is able to scan then it should be using the driver as needed (it creates the driver on disk whenever it is called for, so renaming the old/corrupt copy of the driver which was causing the problem before will have no effect on the current installation and its ability to scan for/detect malware).

If the issue crops up again, please let us know and also please provide the requested logs in the response above mine from "Malwarebytes" for troubleshooting purposes and it might also be helpful to provide a copy of the driver (renamed if necessary) if the issue does occur again.  That said, as long as you're no longer seeing the problem then we probably don't need any further logs/info etc. because, while the steps taken by the Devs to work around this issue weren't necessarily an absolute fix for this issue, they did drastically decrease the chances of it occurring under normal circumstances and I do believe they are researching additional measures to permanently resolve the issue.

Please let us know if there's anything else we might assist you with.

Thanks  

[rkay]

Thanks. I am on version 3.3. Can I delete the renamed mbamswissarmy.sys file? 

[exile360]

Yes, you may delete the old renamed file.  It isn't needed any more.