not posting this in the 1044 thread, it’s such a mess there :
okay…
no idea why that happened, I have currently no scheduled scan at all. I had to reboot to stop that (could have just as well restarted Avast services), see screen shots.
Well, without knowing what was being read (e.g. from Process Monitor)… hard to say anything.
yeah I thought about that by I was in a hurry to stop it and I rebooted… if it happens again I’ll launch process monitor first 
Maybe store the whole Process Monitor log, just in case - it also contains the stacks of the API calls, so it might tell us what exact parts of avast! code it was called from (with the proper symbols).
is that what I need to get and install before saving a procmon log?
http://msdn.microsoft.com/en-us/windows/hardware/gg463028#
I found this in the options, no idea if I need to perform any additional step, install the package I mentioned or not…
edit: must leave the computer, back in a little while…
No, I think you don’t need that - it’s if you wanted to see/resolve the symbols yourself. But if you send us the log (provided it happen again), it’s up to how we have the tool configured here; I believe the info is stored in the log in any case.
(Besides, symbols to avast! modules are not on MS servers, so you wouldn’t see that anyway :))