Using Win2k Pro, ashWebSv.exe or ashServ.exe do not cause problems.
A lot of modules is loaded into RAM which are also loaded and used by other programs.
Assuming that Avast is at least partly C(..) programmed, there may occasionaly occur a memory conflict. This may be due to the compiler used by the Avast designers, the operating system itself or another program. I have seen such problems with Acrobat Reader 7 and some other qualified software. Usually nothing serious: some instruction on a specific memory location can't be read and the OS is not knocked out.
I'm afraid system crashes and RAM "tumors" (see the concerning thread), are due to malicious intruders, not yet detectable and penetrating the firewall when you open it (!).
As a matter of fact, I recently found a rootkit and its hidden generator because of the changes it tried (unsuccessfully) to make in Avast and the Sygate firewall. They were after my creditcard data and I don't even have one
.
The virus did not succeed because all vulnerable files are protected and monitored for changes. There are many freeware programs giving this additional protection. Some of them malware themselves.
