Jump to content

Scan locks up


Recommended Posts

  • Replies 75
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

4 minutes ago, TOH said:

Do you also need the MBAMService.exe file dump or just the c:\mb_crashdumps?

Just the dumps please

Just now, Benno1024 said:

dcollins - you might have him disable the Self Protection, which is likely preventing the process from being attached to for the dump.

Not a bad idea, but unfortunately that won't help here. Thanks for the idea though

Link to post
Share on other sites

  • Staff

I'd try this --

Quit mbam3 from the system tray, and make sure mbamservice is NOT running.

Download ProcDump from sysinternals:

https://download.sysinternals.com/files/Procdump.zip

Unzip it, then open an Admin-elevated command prompt, go to the directory which contains procdump.exe, and enter this command: 

     procdump.exe -e -w mbamservice.exe

 

Keep that window open, maybe minimize it.

Then start MBAM3 and do the scan (reproduce the error).  Check for a dump file (.dmp) in the same directory that procdump was run from.

 

Link to post
Share on other sites

Just now, Benno1024 said:

I'd try this --

Quit mbam3 from the system tray, and make sure mbamservice is NOT running.

Download ProcDump from sysinternals:

https://download.sysinternals.com/files/Procdump.zip

Unzip it, then open an Admin-elevated command prompt, go to the directory which contains procdump.exe, and enter this command: 

     procdump.exe -e -w mbamservice.exe

 

Keep that window open, maybe minimize it.

Then start MBAM3 and do the scan (reproduce the error).  Check for a dump file (.dmp) in the same directory that procdump was run from.

 

Good idea here. Thanks for the recommendation. @TOH would you be willing to try these steps? Let me know if any clarification is needed for these steps.

Link to post
Share on other sites

I'm checking with our other support members to see about remoting in, in the meantime, let's try @Benno1024's solution above first since it should be a quick one. Inside of MB3, can you go to Settings -> Protection and make sure the Enable Self-Protection Module is disabled? I've attached a screenshot of the setting.

Once you disable that setting, then try running another scan, waiting 5-10 minutes after the process hangs, and then seeing if there are any files under c:\mb_crashdumps. Thanks!

Screen Shot 2016-12-21 at 9.36.44 AM.png

Link to post
Share on other sites

  • Staff

@TOH,

Try these steps for running Procdump.

  1. Download the following Procdump.zip file: Procdump.zip
  2. Place procdump.zip in C:\
  3. Extract procdump.zip.
  4. Check that the extracted files are in the directory "C:\Procdump"
  5. Right click "mbamservice_procdump.bat" and select Run as administrator.
    • If you did the steps correctly you will see the following:
      procdump_running.png
  6. Run a threat scan with MBAM 3.0.
  7. When MBAMSERVICE.exe crashes it should close that command window and generate a memory dump file in "C:\Procdump".

Please follow these directions because "mbamservice_procdump.bat" needs to be run in the directory "C:\Procdump" for it to work correctly.

Link to post
Share on other sites

@TOH it looks like we still need some more data, sorry to keep pestering you. Can you find the folder C:\PROGRAMDATA (the ProgramData folder may be hidden, but you should be able to type it in and get there) and zip the entire AOL Downloads folder? You should just need to right click that file and choose Send to -> Compressed (Zipped) folder. It should create a .zip file that I'd like you to upload here. That file may be too large to upload here, and if it is, please upload the file to wetransfer.com using the instructions I mentioned before and email it to me. Thanks again!

Link to post
Share on other sites

Good news @TOH, with that zip file you uploaded I am able to replicate this issue! That means that while we don't have a solution for you at this exact moment, we should be able to figure one out without needing you to run a bunch of things for us! I won't jump the gun and say we're done yet, but hopefully we should be good. You've been a great help!

I know we've had you change a lot of settings, so just to make sure you're back in working order, I'd recommend doing the following things to clean up where left off:

  1. Download the attached zip file and run the .reg file inside of there. This will disable the localdumps we setup earlier.
  2. Delete C:\mb_crashdumps
  3. Delete C:\Procdump and C:\Procdump.zip
  4. In Malwarebytes 3.0, go to Settings -> Application and disable the Event Log Data option

This should put you right back where you were when you started using Malwarebytes 3. For the time being, it's probably best to keep that exclusion on C:\ProgramData\AOL Downloads until we get the issue resolved as well. Feel free to let me know if you have any more questions.

disable_localdumps.zip

Link to post
Share on other sites

  • Staff

Please keep it enabled.  It will protect your Malwarebytes files from being modified or deleted.

The Engineering team has identified which file is causing this issue.  "AOL Downloads\<subfolder>\comps\vwpt\Vwpt.exe"

Until we can fix this, as @dcollins mentioned, please keep your exclusion for the AOL Downloads folder.

Thank you so much for your help with us on this issue!

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.