Skip to main content

Avast 7 AV causes afcdpsrv to crash

Thread needs solution

My XP SP3 system upgraded to Avast 7 (1427) a couple of days ago and upon reboot Acronis True Image Home (2011) Continuous Data Protection (CDP) crashed in afcdpsrv.exe. Tried upgrading to the latest Acronis release (ATIH 2012) but still had interop problem with Avast 7. I was able to downgrade to Avast 6 OK and things are stable once again.

Since Avast 7 was the newest install and ATIH 2011 & 2012 have been stable for sometime, I suspect something in Avast is causing afcdpsrv to crash. The problem may very well be in the Acronis server. It is likely not reacting to some sort of file system/volume access failure in a good manner. (See attached excerpt from afcdpsrv.log)

Has anyone else seen this type of issue?

I'm also logging this problem with Avast...

/ted

Attachment Size
afcdpsrv1.txt 6.16 KB
0 Users found this helpful

Technical follow-up and temporary solution FWIW:

I focused on these messages in the afcdpsrv log which appear just before it crashes:

15:51:00: tid=0x0000163C>EVENT_ONERROR driver log:
15:51:00: tid=0x0000163C>AFCDP3593: KCdpSession[88B0D000]: OnError - created change 88893AF8 0xC00000BB for [][]
15:51:00: tid=0x0000163C>AFCDP3593: KCdpProtectedVolume: Failed to get file name (OnOpened) with status 0xC00000BB
15:51:00: tid=0x0000163C>AFCDP3593: KCdpProtectedVolume: Failed to get file name (TryGetName) with status 0xC00000BB

It looks like the Acronis driver (afcdp.sys) is getting STATUS_NOT_SUPPORTED (0xC00000BB) errors for FS calls going thru the underlying Avast driver (aswSnx.sys). The curious thing I also observed is that after the initial install/upgrade of Avast 7 and before the system was re-started, CDP continued to work. I think this is due to the fact that aswSnx was not loaded yet or was above afcdp in the FS stack. I changed the afcdp file filter's 'altitude' so it loaded under aswSnx and so far no hangs or crashes (keeping fingers crossed).

Going forward, someone at Acronis and/or Avast should check on their products inter-op. The solution I came up with is only a hack work-around at best. The Acronis software is not very robust in handling these (un-expected) errors - looks like memory pool corruption followed by crashing. And, the Avast driver shouldn't be causing them in the first place.

/ted