igor0
9
ATI Tools may of course access a different file (out of i386 folder).
I’d suggest to try to disable particular packers to see if something helps (the first ones to try would probably be OLE, CAB, Installer). Btw, did you also add some extensions to be scanned “on open”? How long did you wait (after changing the profile) before concluding it’s frozen?
You might try to find what is avast! scanning by enabling the report file creation (with all, even “OK files”, included), but I’m not sure the report would be complete after the freeze. Also, you may enable the “Show detailed info on performed action” in the Standard Shield provider to see what’s being scanned, but it might possibly make the problem even worse.