MB freezes PC - conflict wirth Avast? Uninstalled MB again

[glnz]

For the second time in a row, a reinstall of MB Premium (free period) causes my PC to freeze.  Had to uninstall it again.  My guess is that MB and Avast are fighting each other.

 

My PC is a Dell Optiplex 755 desktop with 4GB RAM and Win XP Pro SP3 that I continue to update with the POS 2009 hack.

 

My Avast is Avast Free version 10.4.2233.

 

How do I directly download MB Free (not premium), which of course is passive and does nothing unless I run a manual scan?

 

Sorry, and thanks.

[daledoc1]

Hello:
 
The installer is the same for Free, Trial and Premium.  Download HERE
Paid users "activate" the software with their paid license to enable the Premium features.
There is one Trial per PC per program version.
So, if you have the Trial now and wish to revert to Free, there are several options:

• Allow the trial to expire in 14 days & then click the "End Trial" button in the "Trial Expired" popup;
• Click the "End Free Trial" link in the GUI;
• Click the "End Trial" popup notification at any time from the "Trial Expiring" popup;
• Perform a clean reinstall, using the method described here: MBAM Clean Removal Process 2x - be sure to "opt out" (remove the check mark from) the Free trial, IF it is offered again during the installation wizard.
• (For users with the paid, Premium version -- not the Trial -- one can also click the "My Account" GUI link > "Deactivate". This will revert the program to the Free, manual, on-demand version.)

Having said all that, you might want to try a clean install of the new Beta build.
See here for the changelog and special download link.
 
And you might want to exclude MBAM files from Avast (instructions are below) and Avast from MBAM (see screenshot)
 
Please let us know if that resolves your issue.
If it does not, we'll need to get some diagnostic logs.
 
Thanks,
---------------------------

Please exclude the following files from your Antivirus Software for your version of Windows:


For 32 bit versions of Windows XP, Windows Vista, Windows 7 & Windows 8:

• C:\Program Files\Malwarebytes Anti-Malware\mbam.exe
• C:\Program Files\Malwarebytes Anti-Malware\mbamdor.exe
• C:\Program Files\Malwarebytes Anti-Malware\mbampt.exe
• C:\Program Files\Malwarebytes Anti-Malware\mbamservice.exe
• C:\Program Files\Malwarebytes Anti-Malware\mbamresearch.exe
• C:\Program Files\Malwarebytes Anti-Malware\mbamscheduler.exe

For 64 bit versions of Windows Vista, Windows 7 & Windows 8:

• C:\Program Files (x86)\Malwarebytes Anti-Malware\mbam.exe
• C:\Program Files (x86)\Malwarebytes Anti-Malware\mbamdor.exe
• C:\Program Files (x86)\Malwarebytes Anti-Malware\mbampt.exe
• C:\Program Files (x86)\Malwarebytes Anti-Malware\mbamresearch.exe
• C:\Program Files (x86)\Malwarebytes Anti-Malware\mbamservice.exe
• C:\Program Files (x86)\Malwarebytes Anti-Malware \mbamscheduler.exe

Note: If you are using a software firewall besides the built in Windows Firewall, you'll need to exclude MBAM.EXE, MBAMSERVICE.EXE and MBAMRESEARCH.EXE from it, as well.

Note: Once that's done, please make sure that if either of those programs has any sort of web filter, that you add the following as a trusted site:

data-cdn.mbamupdates.com

[glnz]

daledoc1 - Thanks for your info.  Unfortunately, your steps don't fix the issue on my PC.

 

After adding your six exclusions and one trusted site into Avast, I did a reboot and got a BSOD on the shutdown.  See attached jpg.  On the bootup, my desktop froze before any icons showed on the desktop or on the bottom bar.  Had to do a hard shutdown and go into safe mode, where I downgraded MB to Free and made sure it wouldn't start with Windows.  On the next bootup, I again downgraded MB to Free.

 

The following bootup (right now) is OK.

 

I did not do your large pic above - that is, I did not add Avast to MB's exclusions.  Do you think that will fix this?  Remember that I'm XP Pro SP3, and your pic is obviously for Win 7 or higher.

[daledoc1]

Hello:
 
Sorry to hear about the BSOD.
Alas, it's not a common issue reported here at the forum, even for other XP users on older system, such as yours.

Was this with 2.1.8.1057 or with 2.2.0.1022?
 
Either way, BSOD are usually caused by hardware problems, driver issues or (sometimes) malware (e.g. rootkits).

And I wonder if this could be a contributing factor:

 

Win XP Pro SP3 that I continue to update with the POS 2009 hack

We do have a special forum area for BSOD (here) and another for malware problems (here).
 
In order to know where best to continue with deeper work to resolve your issue, we need a bit more system information.
Please read the following and attach to your next reply the 3 requested logs - Diagnostic Logs (the 3 logs are: FRST.txt, Addition.txt and CheckResults.txt)

 

The logs will help to determine which sub-forum is the best one to start the work needed to try to fix your issue.

Alternatively, if you prefer, you may wish to log a ticket directly with the help desk HERE.  They will assist you, one-on-one, via email.

 

Thank you,