3 replies to this topic

[Amethyst]

I have 2 different computers with the paid version of Malwarebytes running. With the laptop, I have occasional error when I update Malwarebytes. I run the updater manually, and when this error occurs, it's a Microsoft error, involving "faulting application mbam.exe, version 1.41.0.0, faulting module ntdll.dll, version 5.1.2600.3520, fault address 0x0001ab0a. This has happened 4 times since Sept 13/09. The last 2 occurrences were within the last 5 days.

The laptop is running Windows XP Pro SP2, with Outpost Free firewall and AVG free 8.5.423. No other problems are occurring with this system. When I retry the update, it seems to work.

[exile360]

Greetings

Please give this a shot and see if it helps (Note: you should exclude these files from Outpost as well as AVG):

Please exclude the following files from your antivirus:

For Windows XP:

• C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe
  
• C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe
  
• C:\Program Files\Malwarebytes' Anti-Malware\mbamservice.exe
  
• C:\Documents and Settings\All Users\Application Data\Malwarebytes' Anti-Malware\rules.ref
  
• C:\Windows\System32\drivers\mbam.sys
  
• C:\Windows\System32\drivers\mbamswissarmy.sys

Note: If using a software firewall besides the built in Windows Firewall you'll need to exclude them from it as well

Please post back and let us know how it goes.

Thanks

[Amethyst]

Thanks, Exile. I've added those to AVG. AVG and Malwarebytes have had some issues lately, haven't they? I hadn't seen anything on my systems that made me think AVG was causing any problems, but maybe it is.

I'm not sure what to do with Outpost. Outpost has rules for mbam.exe and mbamservice.exe, but none of the others show up on the list. I'm not sure OP Free has any provision to actually exclude anything, but it is allowing the Malwarebytes applications that it has seen anyway. If it happens again, I'll give OP's logs a look and see if it records anything.

[exile360]

Yes, I suspect it's AVG as they've had many issues with MBAM lately (including a few FP's where they were detecting MBAM's files as malware, but those were corrected). Hopefully excluding those will fix the issue. If they were already excluded then I'd recommend removing them from exclusions in AVG and re-adding them again, as sometimes exclusion settings can become corrupt due to application changes (such as the installation of a new version of MBAM).

Keep us posted