hi !
I have this problem which started yesterday, I receive this error twice so far. I noticed that it happen at the boot.
this is the error
06/04/2008 13:22:46 1207488166 SYSTEM 1080 Internal error has occurred in module aswar scan function failed!, function C0000005.
06/04/2008 14:17:37 1207491457 SYSTEM 1008 Internal error has occurred in module aswar scan function failed!, function C0000005.
I hope that someone can help fix this issue.
tahnks in advance.
It didn’t take them to long in getting a fix for the original error, Internal error has occurred in module aswar scan function failed!, function A000010E. That however only seemed to effected those with FAT32 format.
After that fix some have seen a different error number relating to the same aswar module, so they may well be working on a fix, but taking time so there are no unforeseen consequences to the fix.
It really is nothing to worry about other than the event viewer entry it doesn’t effect the other aspects of avast 4.8, you just don’t have the anti-rootkit function working.
Just to let you know I am also getting this error. I have XPsp2 with NTFS and using Avast Pro 4.8.1169. 4/6/2008 12:00:24 PM SYSTEM 1492 Internal error has occurred in module aswar scan function failed!, function C0000005.
My computer is working ok, so will wait for the fix. Posted just to let you know that this is happening for more than one person. slybo
There is nothing to do, the error relates the the anti-rootkit not being able to run, this won’t effect any other part of avast and will run as normal. Just monitor the topics and see when a fix is announced.
Alwil have already fixed a similar problem but with a different error number. I don’t doubt they will do the same, as I said above this isn’t a critical error.
A c000005 error in most programs is general due to a memory leak of some sort within the application, so it will be a problem that Alwil will have to fix.
If it were a memory leak then it is something that would effect everyone so we should all in theory have the error and we aren’t. Not to mention a memory leak detected at boot would be something I have never seen.
Well it might not just be a memory leak, perhaps part of the program trying to write to memory that is protected, or in use by another application, module of Avast or another program all together.
let’s just wait for the problem to be solved, because me too I love avast and I don’t want to use another anti-virus.
by the way, I have xp2 with NTFS (not fat32).