Behavior Shield Freezes PC during Services Startup

Avast Free Antivirus / Premium Security
1

avast! program version is free 5.1.889. After receiving virus definition update 110213-1, released 2011-02-13, 10:34:28, behavior shield froze (locks up) entire PC. Upon reset, after login and welcome screen, at desktop, PC freezes. CHKDSK never found any problems.

This issue occurred on two Win7 x64 PCs, one of which is a fresh rebuild two days ago.

My current workaround was to boot in safe mode and uninstall the behavior shield; all other shields remain running.

Event log info:

The following boot-start or system-start driver(s) failed to load:
aswSP
aswTdi
discache
SASDIFSV
SASKUTIL
spldr
Wanarpv6

2

Did you try to uninstall avast! then reinstall it from scratch along with super anti spyware

3

SUPERAntiSpyware was already installed and I did do a full scan; only tracking cookies were found. I also have Spybot S&D installed.

As soon as I narrowed it down to avast!, I uninstalled/reboot/reinstalled it on the 2-day-old PC: no change. It appears something in yesterday’s behavior shield update causes this. To further test, is there a way to manually revert definitions?

4

Try uninstalling spybot and then reinstall the behaviour shield and see if that works for you,there has been some issues with spybot and avast on some systems, if you still recieve problem’s then revert back to uninstalling the behaviour shield again or another option is to try the 6 beta.

5

I mean uninstall it also then reinstall it"SAS"

6

I understand now. I’m rebuilding my wife’s computers this week; I’ll try installing avast!+update first to see if it conflicts with subsequent SAS or SBSD installations.

I’d still fault the 13 Feb avast! update since that is what changed/introduced the crash. More so in that I don’t have SAS or SBSD actively scanning; I only have them installed for reactive scans and immunise. They do, however, have daemons running for Windows Security Centre that I’ll look to disable.

7

SAS should not be a problem, only spybot. Even when disabled i think there are still active driver’s which is why i say to try uninstalling it, a better tool to use would be malwarebytes as it’s far superior to spybot and does not conflict with avast.

8

I mean to uninstall sas and avast! to get rid of thier drivers then reinstalling them,as sas have drivers also :wink:

9

I know that SAS has driver’s but like i said earlyer SAS should not be a problem as it does not conflict with avast where as spybot can.

10

I have been using SAS and SAS Pro in conjunction with avast for many years without problem.

What you haven’t said is what version of SAS you have and it is only SAS Pro that is a resident anti-spyware scanner. The free version of SAS is on-demand only, whilst it has a service loaded if you have the Right click option enabled (context menu) to scan individual files with SAS.

Neither of these have cause me any problems in the past.

11

SBSD 1.62, which hasn’t changed in quite some time; I think its time to retire it. Like I said, I only use it for it’s immunise function, which may be redundant with avast!'s Web Shield (any thoughts on that?); therefore, I see comparing it to Malwarebytes as apples-to-oranges.

I have SAS Free 4.48.1000 installed but not actively monitoring (it doesn’t start w/Windows, it’s not integrated with Security Centre, real-time protection is not enabled). SAS and Malwarebytes look like oranges to me.

Thank you all for the responses so far; I’ll post what I find when I get to it.

12

That’s right the free version of SAS isn’t resident, so won’t be listed in the Windows Security/Action centre.