Internal error has occurred in module aswar scan function failed!

[DavidR]

I have been a little tardy in my checking in the beta builds as I missed errors (Subject Title) in the running of the aswar module.

This has been happening since the 25th March 2008 and I have just noticed it.

25/03/2008 13:38   SYSTEM   1360   Internal error has occurred in module aswar scan function failed!, function A000010E. 
26/03/2008 12:46   SYSTEM   1380   Internal error has occurred in module aswar scan function failed!, function A000010E. 
27/03/2008 14:02   SYSTEM   1364   Internal error has occurred in module aswar scan function failed!, function A000010E. 
28/03/2008 12:10   SYSTEM   1376   Internal error has occurred in module aswar scan function failed!, function A000010E. 
28/03/2008 22:20   SYSTEM   1360   Internal error has occurred in module aswar scan function failed!, function A000010E. 
29/03/2008 11:56   SYSTEM   1376   Internal error has occurred in module aswar scan function failed!, function A000010E. 
29/03/2008 12:34   SYSTEM   1340   Internal error has occurred in module aswar scan function failed!, function A000010E. 
30/03/2008 00:35   SYSTEM   1340   Internal error has occurred in module aswar scan function failed!, function A000010E. 
30/03/2008 11:50   SYSTEM   1372   Internal error has occurred in module aswar scan function failed!, function A000010E. 
See below for detail of last two avast log viewer and windows event viewer (anti-virus section, I had just been monitoring the System log).

This one was for after the reboot on update to 4.8.1169
30/03/2008 00:35   SYSTEM   1340   Internal error has occurred in module aswar scan function failed!, function A000010E. 

Windows XP Event Viewer entry.
Event Type:   Error
Event Source:   avast!
Event Category:   Client
Event ID:   90
Date:      30/03/2008
Time:      00:35
User:      N/A
Computer:   PC1
Description:
Internal error has occurred in module aswar scan function failed!, function A000010E. 


This one on system boot this morning.
30/03/2008 11:50   SYSTEM   1372   Internal error has occurred in module aswar scan function failed!, function A000010E. 

Also, this one, only difference this one is under my UserName and not System.
30/03/2008 12:02   UsrNme   2844   Internal error has occurred in module aswar scan function failed!, function A000010E. 

Windows XP Event Viewer entry.
Event Type:   Error
Event Source:   avast!
Event Category:   Client
Event ID:   90
Date:      30/03/2008
Time:      12:02
User:      N/A
Computer:   PC1
Description:
Internal error has occurred in module aswar scan function failed!, function A000010E. 

As these were internal errors, there was nothing on screen to jog me into examining the logs, so I'm not sure if this is a problem, e.g. the anti-rootkit isn't running on boot or not.

Win XP Pro SP2, 2 HDDs with c:, d: on drive zero and e:, f: on drive 1 (e: is my DVD) all are FAT32 format.

[Vlk]

There's a similar thread about this. It looks like the issue is related to the system volume being formatted as FAT32.
We'll try to simulate this in our lab tomorrow.

Thanks
Vlk

[DavidR]

Thanks Vlk, I found it after I created this topic (isn't it always the way) and have contributed to that topic as well I look forward to you testing and results.

[Vlk]

This issue will be resolved with today's VPS update (due in about 3 hours).

Thanks
Vlk

[DavidR]

Thank-you.

[acapulco08]

I have been a little tardy in my checking in the beta builds as I missed errors (Subject Title) in the running of the aswar module.

This has been happening since the 25th March 2008 and I have just noticed it.

25/03/2008 13:38   SYSTEM   1360   Internal error has occurred in module aswar scan function failed!, function A000010E. 
26/03/2008 12:46   SYSTEM   1380   Internal error has occurred in module aswar scan function failed!, function A000010E. 
27/03/2008 14:02   SYSTEM   1364   Internal error has occurred in module aswar scan function failed!, function A000010E. 
28/03/2008 12:10   SYSTEM   1376   Internal error has occurred in module aswar scan function failed!, function A000010E. 
28/03/2008 22:20   SYSTEM   1360   Internal error has occurred in module aswar scan function failed!, function A000010E. 
29/03/2008 11:56   SYSTEM   1376   Internal error has occurred in module aswar scan function failed!, function A000010E. 
29/03/2008 12:34   SYSTEM   1340   Internal error has occurred in module aswar scan function failed!, function A000010E. 
30/03/2008 00:35   SYSTEM   1340   Internal error has occurred in module aswar scan function failed!, function A000010E. 
30/03/2008 11:50   SYSTEM   1372   Internal error has occurred in module aswar scan function failed!, function A000010E. 
See below for detail of last two avast log viewer and windows event viewer (anti-virus section, I had just been monitoring the System log).

This one was for after the reboot on update to 4.8.1169
30/03/2008 00:35   SYSTEM   1340   Internal error has occurred in module aswar scan function failed!, function A000010E. 

Windows XP Event Viewer entry.
Event Type:   Error
Event Source:   avast!
Event Category:   Client
Event ID:   90
Date:      30/03/2008
Time:      00:35
User:      N/A
Computer:   PC1
Description:
Internal error has occurred in module aswar scan function failed!, function A000010E. 


This one on system boot this morning.
30/03/2008 11:50   SYSTEM   1372   Internal error has occurred in module aswar scan function failed!, function A000010E. 

Also, this one, only difference this one is under my UserName and not System.
30/03/2008 12:02   UsrNme   2844   Internal error has occurred in module aswar scan function failed!, function A000010E. 

Windows XP Event Viewer entry.
Event Type:   Error
Event Source:   avast!
Event Category:   Client
Event ID:   90
Date:      30/03/2008
Time:      12:02
User:      N/A
Computer:   PC1
Description:
Internal error has occurred in module aswar scan function failed!, function A000010E. 

As these were internal errors, there was nothing on screen to jog me into examining the logs, so I'm not sure if this is a problem, e.g. the anti-rootkit isn't running on boot or not.

Win XP Pro SP2, 2 HDDs with c:, d: on drive zero and e:, f: on drive 1 (e: is my DVD) all are FAT32 format.

[acapulco08]

I'm facing the same situation at any system boot after I've updated to 4.8.1169 version on last March 31. Same situation reported by DavidR on his post dated March 30, same reference data apart from event ID 1920 or 19121 and event category which is N/A to me.

My system Windows XP HE SP2, 1 HD C FAT32 format.

Can anybody assist me?

 

Thanks and regards.

 

Acapulco08

[Vlk]

The problem is supposed to be fixed with yesterday's VPS update (080401-0).

[psw]

Probably not ( http://www.avast.ru/forum/viewtopic.php?p=29098#29098 )

Now error info looks like this

Internal error occurred in module aswar scan function filed!, function 00000001

[DavidR]

It is still there for me Vlk and someone else, -Doug-
http://forum.avast.com/index.php?topic=34209.msg287506#msg287506.

The error number, etc. remains the same for me (see image), VPS 080401-0. It hasn't changed to 00000001.

Edit: Though that coincides with my boot, I can't recall exactly when I got VPS 080401-0, so there might be a change. Checking the event viewer it was at 22:11 on 08/04/01, so no change for me.

[skipperl]

Same error for me as well:

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

And here's something alittle odd, since this error began my MSI CoreCenter monitoring s\w has started reporting the incorrect fan speed for the CPU.  The fan speed would fall below the low rpm limit and give me an alarm.  I  checked the fan and connections and also checked that the fan was working OK in the BIOS, everything looked fine and the speed in the BIOS was correct. I have since uninstalled\re installed the app, tried different monitoring s\w like speedfan and so far found that the only solution was to set smartfan in the BIOS and now all the monitoring s\w seems to work, however this does not allow me to adjust fan speeds.  Very strange.  I have not uninstalled avast yet as I can not figure out the connection,,,,yet.

However the original problem seems to be the key as it would hang my system at times.  I had verified this this with matching the system time with the crash time and the time the avast error was reported in the event log.  They all match.

I have the latest avast as of this morning 2/3/06

Any thoughts welcome

[DavidR]

I can't see any connection either, if anything at boot with the activity and increased/heavy cpu activity the fan would be running quicker. Unless there is a pause in the boot where is litle or no activity (is there ?) with an auto fan/thermal reduction.

The problem is supposed to be fixed with yesterday's VPS update (080401-0).

Any update on the labs testing on this ?

[skipperl]

Actually the fan runs faster at first, which is correct, senses the temp of the cpu and than slows down as usual, then as the seemly delayed start of the avast routines kick in is where the fan goes below norm rpm.  I am still running bios controlled with no problems.  So I can only conclude that something is messing with the sensor s\w being able to communicate with the motherboard properly.  This in itself is very disturbing.  Believe me, I don't get it either, but I have been tetsing and finding problems with various other antivirus s\w's such as ZA, Norton AVG, etc and found this one really bizzare.  I like avast on my xp machine but won't think twice about getting rid of it if I think its messing with my sensors somehow.   I guess my next step would be to uninstall avast and see if the symptoms stop.  OR I guess I can check off the boxes in the trouble shooting area to see if the problem goes away.

[skipperl]

Question, if I begin disabling things in the troubleshooting tab, will avast still function as far as antivirus protection?

[DavidR]

Most of the  items in the troubleshooting section would have no impact on normal running of avast. Obviously you would lose the self-defence module and rootkit scan in on-demand scans.