I’ve got a problem with using aVast! 4 Home on my PC. The problem is, that ashServ.exe don’t start and the whole system runs very slowly - it takes about 10 minutes to see whole desktop.
2 WD hard drives, configured as RAID 0 (RAID created by motherboard controller)
3rd hard drive connected to Adaptec SATA RAID 1430SA controller
Windows XP Professional PL with Service Pack 2 and all newer updates
Funny thing is, that when I’ve installed another copy of Windows on the drive that isn’t a part of RAID config, aVast works fine. The problem occures only on RAID 0 config.
Someone has any idea, what can I do? I do really like aVast and I don’t want to stop using it.
I don’t think the problem has anything to do with RAID.
Try to check the option “Delay loading of avast! services after other system services” on the Troubleshooting page of avast! settings - does it help?
Unfortunatelly - it doesn’t help. When I start Windows, when I see the logon screen I receive an error message (I’ll write it original, Polish version and my - I hope good enough - translation).
ashServ.exe - Błąd aplikacji
Instrukcja spod "0x00e9eb0c" odwołuje się do pamięci pod adresem "0x00000004". Pamięć nie może być "written".
Kliknij przycisk OK, aby przerwać działanie programu.
Kliknij przycisk Anuluj, aby rozpocząć debugowanie programu
ashServ.exe - Application error
Instruction from "0x00e9eb0c" reffer to memory address "0x00000004". Memory could not be "written".
Click OK to stop program.
Click Cancel, to start debugging program.
ashServ.exe - Błąd aplikacji
Instrukcja spod "0x00dbeb0c" odwołuje się do pamięci pod adresem "0x00dbeb0c". Pamięć nie może być "written".
Kliknij przycisk OK, aby przerwać działanie programu.
Kliknij przycisk Anuluj, aby rozpocząć debugowanie programu
ashServ.exe - Application error
Instruction from "0x00dbeb0c" reffer to memory address "0x00dbeb0c". Memory could not be "written".
Click OK to stop program.
Click Cancel, to start debugging program.
I’ve tested my memory with MemTest-86 (over 8 hours) - no errors.
This indeed doesn’t look like a hardware problem, i.e. MemTest probably won’t find anything.
The addresses (00e9eb0c, 00dbeb0c) doesn’t look OK - it’s not the address range of avast! code, i.e. either the execution somehow got completely out of scope, or there’s some 3rd-party module being loaded into avast!.
Don’t know what to suggest… are you able to start the on-demand scanners (avast! Simple User Interface, avast! Explorer Extension…) and use them without problems?
It seems that they start, but I’m not sure if they work correctly. There are also lot of problems with aVast updates because the whole system runs like lazy turtle. I couldn’t updated aVast viruses database or program files.
Second copy of the system, the same PC, the same drivers but XP installed on non-RAID drive - aVast works well. I don’t know what’s going - RAID driver has a bug? RAID controller in nForce 4 Ultra has strange bug?