I am using the updated avast! 4.6 Home.
How can I solve the problem of ashServ.exe running in 99% CPU usage?
I take about 30 minutes to open Explorer window.
I am using AMD 1GHz.
256MB RAM
Windows XP
60GB Hard Disk
Can you check the sensitivity of Standard Sheild Provider, it should be set to normal.
maybe you have set it to high? This is often cause for similar problems.
Left click the avast icon in the sysem tray, choose the Standard Sheild and set → Normal.
Have you tried it? If it is happening than you can check which files are scaned and probably are causing the problem.
Check in Task Manager which files are scaned. If those are some files that are not suspicious to you, you can set avast to ignore them in future scans.
Try, if it does not work, return here and I will sugest something more.
Sorrry my mistake. :-
Don’t look in task manager.
Left click the avast icon in the tray, check beside the Standard Shield what files are scanned when CPU is high.
P.S. Just curious, was there a particular file or archive that was causing the problem?
Please if you have the time you can try one more thing.
In the Standard Shield’s settings, turn on the “Show detailed info on performed action” option (it’s on the Advanced page) and move the sensitivity slider to High.
Then perform the scan once more - and tell me what file(s) avast is scanning (there should be a popup window displayed in the bottom-right corner of the window showing this information).
maybe I’m not up to date here but I had this problem just now, it was because I refused a restart after having downloaded a random update avast! wanted… so this could be a potential bug? I mean, it shouldn’t do that…
What makes you think that the problem was related to the fact that you have not rebooted even though avast asked you to do so? I mean, it sounds quite unlikely that these two events would actually be related…
The 100% CPU usage can be caused by a number of factors. The principal question always is: “is the avast tray icon (the (a) ball) spinning or not?” If it’s spinning, it means avast is scanning something and it’s usually quite easy to find the cause (and a remedy).
I am having the same problem only it is set on normal, also I disabled it and it still is eating any free CPU power it can… I have V4.8.1229… The only fix I have so far is reset my computer then it’ll slowly work it’s way back to eating the CPU again, but thats not really a fix…
The guidelines for solving of the problem “ashServ.exe using too much CPU” has always been the same:
Check if the avast tray icon is spinning (while CPU usage is high)
If it is, click it (wait for the dialog box to open), and check which file is being scanned (the Last Scanned field); the Scanned Count value should be increasing (spinning icon means a scan is in progress)
Find out which of the providers is scanning the file (click “Details” button and check out the Last Scanned value for each of the providers). The most common providers that may cause this are Standard Shield, P2P Shield and IM Shield.
I found this thread by googling because I had the same problem with the 100% CPU. I am confused about why you are only giving a solution for “if the icon is spinning”. Mine wasn’t/isn’t spinning with this problem, and I didn’t see that the OP had a spinning icon either.
What is the procedure when the icon ISN’T spinning? And what is the cause of the 100% CPU useage?
Thanks
Were there a simple “here is the answer” solution to the problem you are experiencing (that is fortunately rare among avast users) then there would be posted in this thread that simple solution answering your question.
Perhaps you would be willing to take the time to answer the earlier series of questions posed in this thread by Tech (reply #9) that may assist us to help you to a solution.
My solution was to keep closing windows I was using for various websites, until the CPU useage dropped. So I’m not sure if this had anything to do with Avast. I was just wondering if anyone had confirmed that this happens when you don’t reboot after an Avast update, since I think I ignored a reboot request the day before this happened.
The reason why the rotating icon thing was mentions is because when it is rotating, it indicate that avast is actually scanning something and that would elevate the CPU usage.
So if you have high/100% CPU usage but no rotating icon, something is locked and this could be a conflict/clash with something else, usually security based. Hence all the questions.
If you were able to get into the Task Manager to report which Process is using all the CPU% that also helps, but once again it is another question, because as Alan said it isn’t a simple solution.
Whilst closing down windows may have got rid of the symptoms (100% CPU) for you, it doesn’t help track down the cause.
OK, now I have 100% cpu usage and no icon spinning… some times it spins though. Windows Vista 64-bit. Avast 4.8. (I also didn’t reboot when it asked me, but i don’t think that’s the cause of the problem (it would be crazy otherwise))
I always have the virus database updated, and same goes for the program.
I didn’t notice this problem earlier, and i think it started about 3 weeks ago.
I’m also doing a quick scan just to make sure i don’t have any virus
BTW, my resident shield/protection never finds any virus, while quick scan or full scan does. does the resident protection have less “power”?
does the p2p shield protects only if you use kazaa or direct connect?
if for my email I use only gmail, can i disable the email shield and outlook shield?
Also, in my “installed provider” list i have a dozen elements some of which have the same name but they are not active. are those the old providers? and the ones that I’m currently using the up to date ones?
The resident protection is only scanning files that are active, e.g. they are being opened and run, etc. that is what is meant by on-access, when the file is accessed it will be scanned.
So it isn’t any different they use the same signatures and scanning engine, just that the on-demand scan is scanning all files depending on the strength and areas you select to be scanned. Over time as you have routed out these inactive files you shouldn’t bump into to this very often.
Sorry I can’t help with P2P questions I don’t use them at all.
Gmail uses SSL (secure encrypted) email designed to keep prying eyes out including AVs. avast can’t currently scan SSL email without something like STunnel to act as a middleman in the process, version 5 of avast should have that functionality incorporated so you can scan SSL email. Gmail does scan its email so the risk is minimal and if you exercise care, don’t open attachments or click links in unsolicited email (without checking them out) then that risk is even lower.
Being stuck on safebrowsing.clients.google.com/safebrowsing/download....etc gives me the impression that you tried modifying the Internet Mail redirect ports and added the SSL port gmail numbers, as I said avast currently can’t handle SSL to doing that would doom it to failure.
I think we have gotten to the crux of your original problem, your installation is stuffed (sorry about getting technical), there are 7 providers and normally only 6 running (unless you have MS Outlook not express installed).
So I would suggest a clean reinstall:
Download the latest version of avast http://www.avast.com/eng/download-avast-home.html and save it to your HDD, somewhere you can find it again. Use that when you reinstall.
Download the avast! Uninstall Utility, find it here and save it to your HDD.
Now uninstall (using add remove programs, if you can’t do that start from the next step), reboot.
run the avast! Uninstall Utility, reboot. If step 1 failed it may be necessary to run this from safe mode, once complete reboot into normal mode.
I have Avast 4.8, winxp pro sp3
ashServ.exe eating 100% cpu is really annoying.
I think you (avast developers) should give more control about this issue, like:
allow changing ashServ.exe process priority (may be from avast icon)
allow stopping the process
allow completely exiting from avast (right click - exit)
if I switch the protection off - nothing changes, still ashServ.exe takes all cpu.