Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: -Doug- on March 30, 2008, 09:57:16 AM
-
Hello!
I just updated my avast! home version to 4.8 and soon I noticed that there are some error messages in Log viewer:
30.3.2008 9:50:51 SYSTEM 1536 Internal error has occurred in module aswar scan function failed!, function A000010E.
30.3.2008 9:58:02 SYSTEM 1532 Internal error has occurred in module aswar scan function failed!, function A000010E.
30.3.2008 10:04:58 SYSTEM 1528 Internal error has occurred in module aswar scan function failed!, function A000010E.
30.3.2008 10:11:46 SYSTEM 1516 Internal error has occurred in module aswar scan function failed!, function A000010E.
30.3.2008 10:25:39 SYSTEM 1528 Internal error has occurred in module aswar scan function failed!, function A000010E.
30.3.2008 10:49:11 SYSTEM 1528 Internal error has occurred in module aswar scan function failed!, function A000010E.
So it has something to do with a new antirootkit system? Everytime I boot my machine there comes one error message more. I am using Windows XP SP2 home.
EDIT: Little bit more info, when I started to scan hard drive the error also comes:
30.3.2008 11:00:47 Username 2044 Internal error has occurred in module aswar scan function failed!, function A000010E.
-
yes, aswar is the antirootkit plugin...
Have you tried to repair your installation?
-
yes, aswar is the antirootkit plugin...
Have you tried to repair your installation?
I tried to repair installation but it didn't help. Same error message still comes to Log viewer after boot.
Any other thoughts?
-
Hi Doug,
could you please tell me a bit more about your hard drive layout?
E.g. is the system drive "C:" ? Do you have multiple logical disks (partitions)?
Do you have multiple physical disks?
Etc.
BTW the good news is that no matter what the problem is, we will be able to fix it with a regular virus database update (without a real program update). This is because the antirootkit logic is actually inside the virus databse.
Thanks
Vlk
-
Okay.
I have two hard drives (C and D) and my system drive is C as usual. I dont have any partitions. Well, and my computer file system is FAT 32 if it has some affect this problem.
-
The FAT32 information may be the clue, actually. We'll have this tested.
BTW what OS are you using? XP?
-
I am using Windows XP SP2 home.
;)
-
I have the same problem on my XP Sp2 system (dutch) with avast 4.8.
I have 3 partions. The system drive is C: and uses the NTFS file system.
The other partions also use the NTFS file system.
On my vista laptop everything works just fine :D
-
I too have this issue, but didn't see this topic before posting here, http://forum.avast.com/index.php?topic=34213.0 (http://forum.avast.com/index.php?topic=34213.0).
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.
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.
-
I checked the event viewer log of a XPSP2 machine but there are no such error messages.
-
Which section of the event viewer did you check, they are in the anti-virus section (if there are any) and they would also be in the error section of avast's log viewer. The suspicion from Vlk could be those with FAT32 formatted partition/s, though there was one person reporting this with NTFS, reply #7.
-
Which section of the event viewer did you check, they are in the anti-virus section (if there are any) and they would also be in the error section of avast's log viewer.
I had already checked there, too. No such error messages.
The suspicion from Vlk could be those with FAT32 formatted partition/s, though there was one person reporting this with NTFS, reply #7.
I forgot to mention it but all the partitions are NTFS.
-
Hello,
It's been quite a while since I ever posted here as I've had very few Avast problems. Except now. I too have the very same error. So kindly excuse me if I make any mistakes in this posting.
I have XP sp2, 2 drives , one of w/c has 3 partitions .All of these fat32 too.
I also have spywareterminator, comodo firewall, spybot, spyware blaster, and adaware 2007.
Can I or should I get rid of spyware terminator and comodo (change it with another FW that has no hips) since Avast already has some of the protection these offer.
BTW. I also did a clean install of Avast after seeing this error but still it remains.
Thanks
Mangyan
-
G'Day All,
After an unsatisfactory experience with the 4.8 Beta at beginning of month (IE & OE would not run sandboxed), I reverted to 4.7.
Today I upgraded to the official 4.8,
and sadly have to confirm this problem shown in event Viewer / AntiVirus
"Internal error has occurred in module aswar scan function failed!, function A000010E."
At boot time, in addition to Windows items, I have WinPatrol 12, Sandboxie 3.24 and Online Armor 2.1.0.119 and of course the Avast AshDisp.exe.
The first boot with Avast! 4.8 produced a blank desktop without any icons at all. After a forced shutdown, and a chkdsk on restart, the tray icons for Avast! and Sandboxie showed Error conditions but OA was OK.
Setting "Delay loading of Avast!.... " didn't help
but "Disable Rootkit Scan ......" did let all applications load properly
including using IE7 and OE sandboxed.
In addition to my profile below I would add that I run multiboot XP Pro SP2 systems on 2 HDDs each with multiple FAT32 partitions.
I am happy to keep using this Avast 4.8 and will await developments, since Vlk expects the bugfix to be possible via a regular virus database update.
Otherwise, congrats to the Avast! team.
Maurice
-
They will be trying to replicate the fault in the labs, which I think they should be able to do. So hopefully it shouldn't be long but in the meantime it really isn't a show stopper.
-
DavidR,
Sorry but it is a show stopper for me.
At the cold boot this morning (after a chkdsk),
WinPatrol, Sandboxie and Avast! all were hung - but Online Armor seemed OK. Event viewer reported the aswan error, although I had disabled the rootkit startup scan.
Managed to disable Sandboxie at startup - after a forced shutdown, restart produced same problems.
Attempt to get to Avast settings produced a window reporting RPC Error, and FAQ button started IE which was then hung.
Managed to kill WinPatrol in Program Manager,
meanwhile (5mins) somehow Sandboxie and Avast had come good.
Cold restart - Avast Ok this time -
Tried "Delay loading Avast Services ..." - reboot - Avast not started.
"The AAVM subsystem reported a RPC Error"
All in all, most unsatisfactory, so its back to Avast! 4.7 for me
at least until Vlk can report success with the fix for the root kit scan.
very dissappointed
Maurice
P.S. On more thing to try - Disable Avast! Raw disk Access at Boot.
-
I am having many of the same problems. I have three programs in common with you; Avast, WinPatrol, and Online Armour. I am using xp home and am only using one partition (NTFS)
I started a post called trouble with start up with 4.8 before I saw this.
-
jwa, et al
Update on previous post:-
Disabled "Raw disk access in Avast! boot-time scan"
Re-boot - (chkdsk) - WinPatrol, Avast! and OA all OK.
IE and OE OK in Sandboxie.
Re-enabled "rootkit scan on system startup"
Re-boot - (no chkdsk) - hung with blank desktop until mouse moved then desktop filled - WinPatrol, Avast! and OA all OK.
IE and OE OK in Sandboxie.
So, maybe attention needed to raw disk access at boot-time scan.
In both cases, Sandboxie control was NOT set to start when Windows starts - (starts when needed by IE and OE which are forced processes).
Reset Sandboxie to start when Windows starts.
Will reboot and report back.
Maurice
-
Hello again,
especially Doug, whose thread we seem to have stolen - sorry!
To update my experiences:
With raw disk access in avast! boot-time scan disabled
and rootkit scan enabled:
Reboot (no chkdsk) - winPatrol, Avast!, Online Armour and Sandboxie Control all have correct icons in Tray and seem OK.
IE and OE ok in Sandbox.
So, in my case at least, the problem lies with the Avast! raw disc access module, although Event viewer / Antivirus continues to report the aswar scan function failure.
For the while, I'll keep Avast! 4.8 with rootkit scan and raw disk access disabled and await developments.
Hope this helps improve Avast! 4.8
Maurice
-
In another topic Vlk said that the problem should be solved at last VPS update but unfortunately I still have this problem. Only change is that the error message is little bit different:
2.4.2008 17:13:27 SYSTEM 1520 Internal error has occurred in module aswar scan function failed!, function 00000001.
As you can notice the function is changed.
EDIT: Well, I noticed that when I start On-Demand scan it doesn't cause error messages anymore so it works little bit better.
-
The error number hasn't changed for me it remains the same.
Internal error has occurred in module aswar scan function failed!, function A000010E.
-
Same to me. Error has remained even with VPS updated (=080401-0).
-
Well everything works fine for me now on my Xp sp2 machine :)
-
I'm getting the same error........
I don't even see any option to disable or manage this new rootkit scan..........where is it supposed to be?
-
Program Settings, Troubleshooting, but there really is nothing to worry about. If it isn't working, it isn't effecting anything else so there is no need to disable it, I haven't.
-
Thx.
-
Your welcome.
-
Error continues remaining the same but since yesterday, after I've updated to VPS 090402-0, the function number indicated in Error Log has changed from A000010E to 00000001. I'm a Neswbie on the forum/matter, in any case is there any possibility of a conflict with other program installed on my PC such as Mail Washer Free 5.1.0 o Spy Sweeper 5.5.7.124 (in any case without antivirus)?
Thanks.
-
They are working on this in the labs trying to replicate the problem and then resolve it.
One important bit of information you don't say is What is your OS and are your Hard Disk partitions FAT32 format, as that seems to be the common link for those with the problem. So bearing that commonality it isn't conflict with other applications.
My error number remains the same, no change there, nothing to do really but wait for the resolution from avast.
-
Hi DavidR,
Question... are you FAT32? Don't see it in your sig line.
Thanx.
-
They are working on this in the labs trying to replicate the problem and then resolve it.
One important bit of information you don't say is What is your OS and are your Hard Disk partitions FAT32 format, as that seems to be the common link for those with the problem. So bearing that commonality it isn't conflict with other applications.
My error number remains the same, no change there, nothing to do really but wait for the resolution from avast.
My OS is XP SP2, HD partitions FAT32 format.
-
Intentional deletion.
-
Hi DavidR,
Question... are you FAT32? Don't see it in your sig line.
Yes, though you won't see that in my signature, nor will you see my inside leg measurement as for the most part it is irrelevant to the majority of issues ;D
-
ROFLMAO. ;D :o ;D
Thanks David.
-
Hello All,
Since my last post a couple of days ago I have experimented somewhat and would add the following comments in the hope they might help improve the startup situation.
1) It seems to me that there is , not surprisingly, some conflict between applications which want to start at boot time.
In my case they are Avast!, Online Armor, WinPatrol and Sandboxie, although I prefer to have the latter start when needed.
I wasted half a day trying to manage the startup order to no avail since all three (Avast!,OA & WP) insist on stating first and cannot be delayed.
2) Thinking it prudent, after all that mucking about, I completely uninstalled Avast! 4.8, which had been upgraded from 4.7.
I reinstalled 4.8 from the downloaded exe file, and since then the startup situation has settled down and Avast!, OA and WP appear to be cooperating during startup.
I still get
Internal error has occurred in module aswar scan function failed!, function 00000001
each startup.
3) Can it be confirmed that the Avast! rootkit scan on system startup has a 2 min. delay ? (Ref: Vlk elsewhere)
This might explain why sometimes the startup problem heals itself after a short delay.
Hope this helps those still having startup problems
i.e. try a clean reinstall from the exe file.
Maurice
-
I wasted half a day trying to manage the startup order
How? Doing what?
3) Can it be confirmed that the Avast! rootkit scan on system startup has a 2 min. delay ?
You mean seconds instead of minutes?
On version 4.8 the boot speed was improved and not delayed...
-
Tech,
1) Wasted half day.
Since it seemed that startup problems might be due to conflict between several startup applications (Avast, Online Armor & WinPatrol), I thought it might help if I could arrange for them to start, one after the other.
WinPatrol has such a facility, however I found that the start of both Avast! and Online Armor cannot be delayed.
2) Delayed start for rootkit scan:
It may be that I misinterpreted Vlk's comments
Quote
It's clearly the automatic rootkit scan. It is starting (by default) 2 minutes after the service is launched.
On a "normal" system, it only takes a couple of seconds to complete. If it takes 15 minutes in your case, it is definitely worth investigating.
Endquote
here:-
http://forum.avast.com/index.php?topic=34308.msg287594#msg287594
I connected "by default" with the "two minutes"
and now see that "default" should be connected to "automatic rootkit scan".
Sorry, I haven't yet found out how to properly post quotes and topic URLs. When I try, I keep getting logged out - so I copy what I want into Notepad and thence to the message being prepared..
Anyway, my system is currently behaving - but I fear more by good luck than good management.
Regards,
Maurice
Maurice
-
Hi!
Problem seems to be fixed! :) I don't get any error messages anymore.
Thanks to all of you! ;)
-
Same problem here.
XP SP2
2 HDD; 3 partitions.
HDD1: only C partition (20gb) fat32 formatted
HDD2: D and E partitions ntfs formatted
avast 4.8.1169, vps 080404-0
-
Further VPS 080404-0, as Doug I'm not having any error message now.
Thanks to everybody.
-
How can I verify if the anti-rootkit module works?
-
How can I verify if the anti-rootkit module works?
Do you have Home or Pro (trial) version?
-
Home edition.
-
XP: Windows Start > Run
"C:\Program Files\Alwil Software\Avast4\ashQuick.exe" "<RTK>SUPERQUICK"
Vista: Windows Start > write "cmd" without quotes > click CTRL+SHIFT+ENTER
Anwswer 'Yes' to UAC question.
Write down (or paste):
"C:\Program Files\Alwil Software\Avast4\ashQuick.exe" "<RTK>SUPERQUICK"
Click Enter
-
Did that, the scan started and finished with no problems.
This proves that the anti-rootkit module works?
-
Yes the anti-rootkit module is now working on my system (FAT32 formatted drives), tested using the ashquick rootkit command.
-
The problem seems to be solved here too.
After the update to 080404-0 I didn't restart the pc and so I got the error in the log viewer.
Now I restarted the pc and there's no error regarding the 'aswar scan function'.
-
Happy to report that since my last post, as promised by Vlk,
a VPS update (080404) has cured the rootkit scan at startup problem.
My troubleshooting options are now all cleared
and Avast! 4.8, Online Armor 2.1.0.119 and WinPatrol 12 are all collaborating at startup.
IE7 and OE6 are both operating correctly Sandboxed
and Avast Rootkit Scan on demand is also working.
All systems are "GO".
Congratulations to the Alwil Staff
Maurice
-
Hello again!
The problem occured again and now with new error function.
6.4.2008 11:47:38 SYSTEM 1532 Internal error has occurred in module aswar scan function failed!, function C0000005.
6.4.2008 14:25:08 SYSTEM 1532 Internal error has occurred in module aswar scan function failed!, function C0000005.
I think this started after yesterday VPS-updates.
-
Me too:
At least the error changed:
Internal error has occurred in module aswar scan function failed!, function C0000005.
IF there is a fix, please provide steps. Delay, no delay, disable, whatever. I just want this thing to go away.
-
a few topics have been made referring to this, hopefully someone in the know can give us some info on a fix
-
Same error here. But if I try the "C:\Program Files\Alwil Software\Avast4\ashQuick.exe" "<RTK>SUPERQUICK" command in Run, the scan works and finishes succesfully.
-
Discussion on the matter continues on Subject: Internal error has occurred in module aswar scan function failed!, http://forum.avast.com/index.php?topic=34213.
-
Hello All,
I got this new variety of rootkit scan error yesterday.
"Internal error has occurred in module aswar scan function failed!, function C0000005"
After updating to VPS 080406 this morning, all fixed again.
This is getting to be tedious.
Maurice
-
Hi, everyone :
So long time I wasn't here.
First of all congrats for the version 4.8 Release, it's working fine in my computer however I'm experiences some problems. The antivirus log error viewer is filling with errors related with my firewall (Online Armor 2.1.0.119 Free), here I send you the lines for today April 7th 2008
07-04-2008 0:19:53 1207541993 SYSTEM 1684 AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\Archivos de programa\Tall Emu\Online Armor\server.dat failed, 00000005.
07-04-2008 0:19:59 1207541999 SYSTEM 1684 AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\Archivos de programa\Tall Emu\Online Armor\server.dat failed, 00000005.
07-04-2008 0:19:59 1207541999 SYSTEM 1684 AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\Archivos de programa\Tall Emu\Online Armor\server.dat failed, 00000005.
07-04-2008 0:20:32 1207542032 SYSTEM 1684 Internal error has occurred in module aswar scan function failed!, function C0000005.
07-04-2008 0:33:59 1207542839 SYSTEM 1684 AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\Archivos de programa\Tall Emu\Online Armor\SentList.dat failed, 00000005.
07-04-2008 0:34:00 1207542840 SYSTEM 1684 AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\Archivos de programa\Tall Emu\Online Armor\server.dat failed, 00000005.
07-04-2008 0:35:35 1207542935 SYSTEM 1684 AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\Archivos de programa\Tall Emu\Online Armor\server.dat failed, 00000005.
07-04-2008 0:37:10 1207543030 SYSTEM 1684 AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\Archivos de programa\Tall Emu\Online Armor\SentList.dat failed, 00000005.
07-04-2008 0:37:10 1207543030 SYSTEM 1684 AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\Archivos de programa\Tall Emu\Online Armor\server.dat failed, 00000005.
07-04-2008 0:38:47 1207543127 SYSTEM 1684 AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\Archivos de programa\Tall Emu\Online Armor\server.dat failed, 00000005.
Also I have Superspyware Terminator but On-Demand Mode only, and I've checked the rootkit checker at startup
Also the Windows Log Viewer (Avast Antivirus section) is reporting the same errors, and the worst is when I perform a HDD check (both files check and surface check (Windows in-built HDD CHKDSK) because after the CHKDSK the startup freezes, so I had the following workaround :):
1. Pressing Alt+Ctrl+Del keys (Task Manager)
2. Stopping the explorer.exe process
3. Reboot
4. The start up works normally
So these are my glitches, but I hope that the developement team will find a solution to this problem, as far I can see I'm not the only who's experience this issue ;). My HDD is a NTFS file system
I'll post the following image
Kindly regards
MiguelAngelXP
-
These errors are unrelated to the anti-rootkit scan errors. The windows error 5 = Access is denied, which doesn't surprise me in the slightest given that it is related to your Firewall which is probably protecting its files. You have nothing to worry about.
The windows event viewer, anti-virus gets its information form the same source so there will be matching entries in both.
-
Thanks pal ;)
MiguelAngelXP
-
Your welcome.