* Introducing * - beta version of upcoming avast update (4.6.689)

[RejZoR]

There is something wrong with ashQuick. I checked folder full of malware to decide which one to submit it to Alwil (undetected ones) and i got this error after few processed files:

[RejZoR]

I checked same folder with ashSimpl2.exe and got the same error (this time forashSimpl2.exe). But in this case avast! finished scan,showed Results panel and when i clicked Close in it,i got the error mentioned above.

[Vlk]

Please pack them all to an archive and upload them to ftp://cat.asw.cz/incoming

Thanks,

[RejZoR]

Ok, i'm already uploading it. The package is quiet big (16MB). Some files are still in encrypted ZIP archives,because i made just a quick sweep for stuff that is not encrypted.
Use password: infected , to unpack those later...

First time i checked them with ashQuick i got warning for low virtual memory (i have over 1GB for page file on separate partition and 512MB of physical RAM) and after that error above. Every next time i didn't got any virtualmemory warning,just runtime error.

[igor]

Unfortunatelly, no error here
Can you please try to identify the problematic file?

[RejZoR]

Yeah i tried,but when i removed it,next one did the same.
I can remember ztoolbar.zip was one of them.

I'll reinstall avast! now and try again...

[igor]

If you scan that file alone, do you get the same error?

Btw, you said the error appeared after a few scanned files. Of course I don't know whether you have the files in separate folders, but ztoolbar.zip would rather be scanned later than the others (alphabeticcaly).

[RejZoR]

I have reinstalled avast! and i still get the same error. I don't know whats going on with avast!.

[igor]

OK, can you please try to find the exact file causing the problem? For example, by binary division of your folder
I don't get any problems here...

It would be rather strange if you didn't get the same error after reinstallaion...

[RejZoR]

Got the exactly same thing in my sandbox running Windows XP without any service pack. Now i wonder whats wron on your end...

[igor]

Well, I'm afraid I really cannot do anything about it without the "bad" file 

[RejZoR]

I'm not sure if "bad" file has anything to do with it. Sandbox gave me the exactly same symptoms. First virtual memory warning,after that few 10 files tested and bam,thing dies off.
I went over same files with NOD32 and it didn't complained about anything.
I have restored image and i'll check same files with official release of avast!...

[igor]

How about Enhanced? If it crashes too, does it help if you turn off some packers (WinExec, for example)?

Also, check the virtual memory usage (of ashQuick, for example) in Task Manager during the scan - does it grow continuously, or does it jump up and down?

[RejZoR]

Ok,just tried on perfectly fresh sandbox environment with official build.
Same thing,only th¸is time i got that report error to MS dialog. ashQuick crashed again,virtual memory as well and again on ztoolbar.zip ...

[Vlk]

Is there an UNPxxxx file in the <avast>\data\log folder generated?