BattlEye's problem was something else -- their app called undocumented API which was primarily designed for debuggers. During that call, system suspended that process and it deadlocked.
When your system gets deadlocked, you should generate full memory.dmp and send us for further analysis. Yesterday you sent me avastsvc's dump but there was no active scanning thread in that moment, so the problem was somewhere else, or it was gone. Full memory dump would be helpful (we can analyze kernel and user-mode threads). Thanks.
the irony is that BE author removed BE from the system and applications still got frozen threads en random
when each of the end-users with the problem removed avast, everything went fine ...
actually (or most importantly) those 'stuck' threads unfroze when the Avast! uninstall did it's job
also the issue still happens on systems w/o any BattlEye at all ...
full system memory dumps were sent without BattlEye also in the last report
so take look at those in first place
from my observation with last week issues it also seems like
Avast! goes into hardened mode/deepfreeze lock and prevents any other operations elsewhere
if it's directly or indirectly linked to the stuck threads problem I do not know