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

Avast Free Antivirus / Premium Security
1

This issue will be resolved in today’s VPS update, due in about 4 hours.

Sorry for the trouble.

Thanks
Vlk

2

thank you :slight_smile:

3

Vlk, thank you.

Any comment on what caused the problem or why it failed to show up in the Beta testing?

4

:wink: ;D

Waiting for this isue to test it with impatience… :stuck_out_tongue:

Anyway, thanks in advance. i will post here afetr VPS update to say if it works 8)

Bye.

5

if you dont mind me asking what will the definition (VPS update code) be that contains this fix?

6

It is 080407-1 and it’s already out.

7

Thanks Vlk, I will see if it has fixed it, although it only logs the error on boot up or restart so it could be a while before I can check, again thanks

8

Just updated and rebooted without an entry in the event log so it appears to have worked, thanks.

9

Same here, so the issue is solved :slight_smile:

Greetz, Red.

10

Thanks Vlk. Just received file number 080407-1 (04.53 pm UK time).

11

Ok,

i updated with VPS 080407-1, make on ereboot, no more message in windows event viewer.
I make a scanning on demand, no message.
I rebbot one time again, no message.

So, it seems to be soved from my side also. :smiley:

Thanks to you Vlk. ;D

12

Problem also fixed here.
Hopefully this was the last problem related to the anti-rootkit module.

13

Well tonight 20:00 (-4 GTM Greenwich) in Chile I’ll check it, I hope it works :wink: , so I’ll tell you how it goes for me. Because this error is affecting after performing a CHKDSK in startup Thanks

Kindly regards
Miguel Angel

14

Problem is fixed also with me after VPS 080407-1. Thanks a lot to Vlk, let’s keep our fingers crossed as regards the next VPS updates.

15

You don’t have to keep anything x-ed, really :slight_smile:
The problem has been solved.

16

Vlk,
Seems fixed for me also after vps 080407-1.
It was getting to try my patience a bit - but well done, thanks
Maurice

17

Fixed here too, good job man ;D

18

the error has not been logged since I checked this morning, good work guys :slight_smile: