Avast Internet Security + MBAM pro + SAS known compatibility issues?

Avast Free Antivirus / Premium Security
1

Hi,

After the major infection I got last week I started using MBAM pro + SuperAntiSpyware pro with Avast Internet Security 6, and just wanted to know if there are any known compatibility issues ? will it slow down my net browsing speed / computer performance?

Also, I kept getting a threat alert on MBAM and name of the process was avastsvc.exe, I will copy paste it below from the log. Let me know if I should exclude Avast on MBAM or exclude MBAM on Avast. I kept getting it every few seconds at times and it got really annoying. I contacted MBAM moderators about it and they are looking into it, but why question is why is it detecting an avast module as a threat?

20:04:30 Chatura IP-BLOCK 94.100.18.194 (Type: outgoing, Port: 56182, Process: avastsvc.exe)
20:04:30 Chatura IP-BLOCK 94.100.18.194 (Type: outgoing, Port: 56183, Process: avastsvc.exe)
20:23:46 Chatura IP-BLOCK 94.100.18.194 (Type: outgoing, Port: 57291, Process: avastsvc.exe)
20:23:46 Chatura IP-BLOCK 94.100.18.194 (Type: outgoing, Port: 57292, Process: avastsvc.exe)
21:20:07 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58739, Process: avastsvc.exe)
21:20:07 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58740, Process: avastsvc.exe)
21:20:07 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58742, Process: avastsvc.exe)
21:20:07 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58743, Process: avastsvc.exe)
21:20:15 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58746, Process: avastsvc.exe)
21:20:15 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58747, Process: avastsvc.exe)
21:20:15 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58749, Process: avastsvc.exe)
21:20:15 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58750, Process: avastsvc.exe)
21:20:15 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58752, Process: avastsvc.exe)
21:20:15 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58753, Process: avastsvc.exe)
21:20:24 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58755, Process: avastsvc.exe)
21:20:24 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58756, Process: avastsvc.exe)
21:20:32 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58789, Process: avastsvc.exe)
21:20:32 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 58790, Process: avastsvc.exe)
21:45:18 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 59895, Process: avastsvc.exe)
21:45:18 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 59896, Process: avastsvc.exe)
21:45:18 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 59898, Process: avastsvc.exe)
21:45:18 Chatura IP-BLOCK 124.217.249.182 (Type: outgoing, Port: 59899, Process: avastsvc.exe)
21:52:48 Chatura IP-BLOCK 109.236.80.148 (Type: outgoing, Port: 60942, Process: avastsvc.exe)
21:52:48 Chatura IP-BLOCK 109.236.80.148 (Type: outgoing, Port: 60943, Process: avastsvc.exe)
21:52:56 Chatura IP-BLOCK 109.236.80.148 (Type: outgoing, Port: 60997, Process: avastsvc.exe)
21:52:56 Chatura IP-BLOCK 109.236.80.148 (Type: outgoing, Port: 60998, Process: avastsvc.exe)
21:52:56 Chatura IP-BLOCK 109.236.80.148 (Type: outgoing, Port: 60999, Process: avastsvc.exe)
21:52:56 Chatura IP-BLOCK 109.236.80.148 (Type: outgoing, Port: 61000, Process: avastsvc.exe)
21:53:28 Chatura IP-BLOCK 217.23.8.113 (Type: outgoing, Port: 61140, Process: avastsvc.exe)
21:53:28 Chatura IP-BLOCK 217.23.8.113 (Type: outgoing, Port: 61141, Process: avastsvc.exe)

2

Three resident shields are not good. Please turn off superantispyware’s.
Malwarebytes + Avast! has no known issues

3

You need to Exclude MBAM files.

Please see the MBAM help on AVG:
Section H
http://forums.malwarebytes.org/index.php?showtopic=10138&st=0&p=167851&#entry167851

4

Hello

IMO avastsvc.exe has been blocked because avast!'s Web Shield module acts as an transparent proxy which will redirect your http connections to port 12080 and therefore MBAM sees avastsvc.exe as a process attempting to connect to Malicious IPs.