Internal error has occurred in module aswar scan function failed!

[skipperl]

OK, I uninstalled avast, then used the avast uninstall utility, turned off bios fan option, reinstalled nvidia system board drivers, turned c "n" Q on in bios(for the heck of it,,should not need it), removed unwanted pivot driver(HP driver).   I restarted and so far so good on restart.  Trying complete power down as we speak, no alarm and now rebuilding vrdb.  Still have the errors in event log as stated above.  But, seems like fan issue may be resolved.  Once again, the only thing that has been changed is the latest avast update,,, I honestly don't get it.  OOOps, I take that back, speaking of the pivot driver, I installed a new monitor, HP W2207h.  This is where the pivot driver came from.  It definitely could be related, lousy HP s\w.  Monitor s\w, AV s\w causing cpu fan issues?  I got to get out of this business.  I will keep you informed, please let me know if there is a fix for the event log errors,  I am one of those IT guys that hate any kind of errors showing up anywhere.,,,,,,,Thanks

[Lisandro]

Obviously you would lose the self-defence module and rootkit scan in on-demand scans.

What about on-access... Does we have on-access protection over rootkits?
If so, I think the option will disable this protection either.

[DavidR]

Only in the sense that their signatures might be detected by the on-access providers, but I don't think that there is a resident rootkit running in the background to be able to detect and deal with rootkits.

A simplification, perhaps over simplification, a very rough example there has to be two scans to detect a rootkit, one showing what the windows API shows as running (and rootkits hide from those) and one to show those running at a lower level and the two are compared.

[sanctuaryforever]

I have this issue since today but my file format is NTFS not FAT32 can someone help me please? :'(

Is there any news on when it can be fixed?

ps is the forum busy as I cant get access sometimes?

[DavidR]

Post the details of the error as I believe the error number is different. Check the windows event viewer and click the copy icon, or the avast log viewer and past here.

The original error (FAT32 related):
28/03/2008 22:20   SYSTEM   1360   Internal error has occurred in module aswar scan function failed!, function A000010E. 

[sanctuaryforever]

Internal error has occurred in module aswar scan function failed!, function C0000005. 

client 90

[DavidR]

Yes slightly different to the original error number I reported, but this may have been an unintentional consequence of the fix for the other error (this is speculation on my part). I no longer get the original or the new error number which seems to effect NTFS thater than FAT32

[skipperl]

No, not just ntsf, I have fat 32:


Event Type:   Error
Event Source:   avast!
Event Category:   Client
Event ID:   90
Date:      4/6/2008
Time:      10:30:08 AM
User:      N/A
Computer:   SKIPPC
Description:
Internal error has occurred in module aswar scan function failed!, function C0000005. 

Original error gone.  Seems like we are trading one error for another.  My question is what besides the rootkit scan does this error effect on the system?  Me no likey errors.

[sanctuaryforever]

what has Vlk said about this issue are they aware of it and are they trying to work on a fix?

[DavidR]

I don't believe Vlk has specifically mentioned this error number, so I can't say if he is aware of it or working on it, but I will raise it elsewhere.

[N@URINE]

hi guys !
I have the same problem : http://forum.avast.com/index.php?topic=34465.0

[Chrisatrax]

Hi Folks,

Yes... I have noticed the same types of errors as well within the last week. I think this has been happening since the last Avast program update. I am using Avast Version: 4.8 Home Edition, Build: April2008 (4.8.1169). Xtreme Toolkit version: 1.9.4.0.

Here are 3 types of Event Errors/Warnings I have just got today.

Event Type:   Error
Event Source:   avast!
Event Category:   Client
Event ID:   90
Date:      04/06/2008
Time:      08:05:59 AM
User:      N/A
Computer:   CHRISTOPHER1
Description:
Internal error has occurred in module aswar scan function failed!, function C0000005.
===============================================================
Event Type:   Warning
Event Source:   avast!
Event Category:   Client
Event ID:   90
Date:      04/06/2008
Time:      10:08:45 AM
User:      N/A
Computer:   CHRISTOPHER1
Description:
AAVM - scanning warning: x_AavmCheckFileDirectEx [UNI]: \\Christopher2\MY
DOCUMENTS\My Pictures\CD Cover & Biz Card Templates\My CD Cover Pix\Kal David CD
Back Cover.jpg (\\Christopher2\MY DOCUMENTS\My Pictures\CD Cover & Biz Card
Templates\My CD Cover Pix\Kal David CD Back Cover.jpg) returning error, 00000005. 
==============================================================

Event Type:   Error
Event Source:   avast!
Event Category:   Client
Event ID:   90
Date:      04/06/2008
Time:      10:08:45 AM
User:      N/A
Computer:   CHRISTOPHER1
Description:
AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of \\Christopher2\MY
DOCUMENTS\My Pictures\CD Cover & Biz Card Templates\My CD Cover Pix\Kal David CD
Back Cover.jpg failed, 00000005. 
=================================================================

So that's it for now, I will be checking back to this thread to see what it may be. Thanks.

Christopher

[acapulco08]

 >:(The situation seemed to be fixed with VPS 040404-0 the day before yesterday, but since this morning further to VPS 080406-0 the problem has come back to me too. Same Internal error, while code event reads 1912 and code function the same (= C000005). Apparently there is a sort of instability depending on VPS update.

[DavidR]

An earlier VPS update corrected a similar problem with aswar, but with a different number ( A000010E), perhaps that was the one that was corrected for you. I don't recall anyone else reporting the C0000005 error as being fixed, but there are a few different topic on this problem, so hard to tell.

[MauriceW]

Hello All,
I would like to correct an earlier post on the other thread

http://forum.avast.com/index.php?topic=34209.msg288846#msg288846

that VPS update 080406 corrected the startup rootkit scan error
(function C0000005)

After my PC was off for 2hrs, rootkin scan on startup error back.
Not fixed this time by VPS update 080407-0.

It seems to me that there is an erratic conflict between my startup applications, 
namely WinPatrol, Online Armor , Avast! and Sandboxie,
although the Control GUI for the latter is disabled in WinPatrol.
It seems that once the error has occurred, shutting down or disabling these other startup apps doesn't correct it.

Since I see my security being dependent on
1) Sandboxie, 2) Online Armor and 3) Avast!
I guess I'll have to live with a minor disability with Avast!

Maurice