Jump to content

mxhmembership

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by mxhmembership

  1. Hi, I tried the suggestions above and Malwarebytes still give me the same error. Tried to run Malwarebytes scan or update without the Bitdefender and Firewall and still had the same error. Turned UAC completely off too. I found the below thread. Followed instructions to replace my net.conf file and the problem was solved. https://forums.malwarebytes.org/index.php?/topic/149840-crash-when-database-update-attempted/ Thank you for all the help!!!!!!!!
  2. Thanks for the quick reply. Malwarebytes stops working whenever I click update or scan. Otherwise I can use the program without any problems. I used mbam-clean-2.0.2.0.exe to remove Malwarebytes. Then reinstalled Malwarebytes. This was done a few times. Also used the mbam-chamelon-3.1.4.0 to install Malwarebytes once. I don't recall installing version 1.75. However, I went through past posts from others in this forum and may have followed instructions to install v.1.75 from old links. The bitdefender only has virus shield and auto scan. It's version 1.0.21.1099. I specifically allowed malwarebytes through my firewall.
  3. Malwarebytes installed on a new computer. Crashes whenever I try to update or scan. Error message below: Problem signature: Problem Event Name: APPCRASH Application Name: mbam.exe Application Version: 1.0.0.532 Application Timestamp: 53518532 Fault Module Name: MSVCR100.dll Fault Module Version: 10.0.40219.325 Fault Module Timestamp: 4df2be1e Exception Code: 40000015 Exception Offset: 0008d6fd OS Version: 6.1.7600.2.0.0.256.48 Locale ID: 3081 Additional Information 1: 8374 Additional Information 2: 83748d7ce6919cf452bf5c3838e036f3 Additional Information 3: 2e01 Additional Information 4: 2e01b10c887fd7f971b05773252074ee Addition.txt CheckResults.txt FRST.txt
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.