Es liegt nur an dem Scriptblocker.
Well, you are the first one to have such a problem, nobody else ever reported this issue (and there certainly are many people running WinXP and Script Blocker) - so I'd tend to think the problem may be somewhere else (some kind of conflict with other tools running on those computers, for example).
Ohne Sciptblocker macht es jedoch keinen Sinn ein AVAST Pro zu installieren, es ist schade für die Firma alwil das sie keinen Support Ihren Händlern gegenüber geben können.
Completely wrong. Since the introduction of Web Shield, the Script Blocker is mostly an obsolete feature - there is hardly anything Script Blocker would detect that Web Shield would not. There are more useful features in avast! Professional (Enhanced User Interface, Scheduler, Push updates) that are not present in avast! Home. Installing avast! Pro only because of Script Blocker is a nonsence.
Da sollte sich schnellsten etwas ändern. das sage ich als Reseller von avast.
If there is a bug in avast!, we would certainly like to fix it. However, if we cannot reproduce the problem (and we cannot - as I said, everything is working correctly elsewhere), it is rather hard to do.
Do the following, please:
1. Send/post the list of running processes on the system (before shutdown)
2. For every bluescreen, there should be a corresponding minidump file in C:\Windows\Minidump. Select a few recent files and send them to
vlk@asw.cz.
Thanks.