ashQuick errors while scanning is started by Free Download Manager

Avast Free Antivirus / Premium Security
1

Any clues about what is happening?

2

Is there any way to configure the command line Free Download Manager will pass to ashQuick?

3

Yes, there is.
C:\Util\Antivirus\Avast\ashQuick.exe %file%
The argument %file% is an internal requirement of FDM.
Some files pass, others no. There isn’t any error like ‘file does not exist’ or ‘cannot scan file’.
Just this strange memory error…

4

OK, I’ll send you a special build tomorrow that will announce what command-line is passed to ashQuick.

5

Thanks Igor 8)

6

For instance…

7

And ashQuick crashed after these sessions?

8

No, everything is fine today. Not a single error 8)
Did you change anything into ashQuick.exe ?

9

No, nothing - just added the message box.

10

So… I can’t add more info. Considered solved I since then I have no more trouble (memory could not be read).

11

Just out of curiosity - could you try the following?

  1. Run (possible a longer ashQuick scan)
  2. Start Process Explorer and select the ashQuick.exe process
  3. Let the DLLs be displayed in the lower pane (Ctrl+D)
  4. If there’s no column called “Base”, add it (View / Select Columns / DLL / Base Address)
  5. Now, sort the DLLs by their base address and check what DLL is the crash address (774f6777) from. (I.e. find the DLL that has the nearest lower address).

What DLL is it?
Thanks.

12

Igor, I’m trying right now…
But it’s not being easy to ‘crash’ ashQuick.exe anymore ::slight_smile:
If I succeed, I’ll post.
I have Process Explorer opened showing the base address column of the DLL panel.
Waiting any crash…
Do you have a better idea, for instance, trying to scan a particular file?

13

No, it doesn’t have to crash… I’m just trying to find out what DLL is loaded into the ashQuick process at that address (which shouldn’t change much). So, just scan your C: drive, for example, and check the Process Explorer while ashQuick is running.

14

Here… which one is the ‘bad’ guy?

15

If you’d click on the “Base” header, the DLLs would get sorted by their base, so it would be easier to say :wink:
Anyway, I think the problem occurred in ole32.dll… which means that the problem will probably be somewhere completely else. Could you send me your ole32.dll file by e-mail?

16

I’ve did it… I thought the dll were sorted that way.

Sure, in a minute…

17

The crash occurred inside of ole32.dll, in a function called StartServer. So, my guess is that the problem was caused by some other application… possibly some 3rd party OCX, registered in the system, or something like that. I can’t say anything more just by the address, I’m afraid.

18

Thanks for the debugging but I can’t go further… I can’t imagine which ocx driver is making that.
Now I don’t have any other crash.