I’ve noticed this for a about half a year now but every now and then, after I turn on my laptop, the fan spins really quick and task manager shows that AvastSvc.exe takes up 25% of my CPU (it doesn’t fluctuate). The core graph also shows that all 4 cores are pretty active and there is no end to that process unless I perform a restart, then things go back to normal, but again, after another restart or so, AvastSvc takes over 25% of my CPU again.
Not sure if this is a bug (memory leak), but I’d rather look into this in more depth to make sure Avast isn’t playing dirty tricks on our PCs and start mining for cryptos behind our back.
My system:
Windows 7 SP1 x64
AMD A10-5750 CPU (4 core 2.5Ghz)
HGST Travelstar Z7K500 500GB HDD
8GB DDR3 RAM
UPDATE 1: After disabling my wifi, the process closes and my PC gets back to normal again, even after re-enabling the wifi, which reinforces the idea of hidden crypto mining.
UPDATE 2: As it turns out, the problem seems to actually be Avast Antirootkit, with the log file in “C:\ProgramData\AVAST Software\Avast\log\aswAr.log”. But even after disabling it from the Core Shields UI, it still triggers on reboot. The service is so annoying that if I attempt a restart when AvastSvc is running, i have to wait till it finishes, with the screen just saying “Restarting” or “Shutting Down”.
Did that too. I perform clean formats of my PC from time to time.
P.S. Asyn, if you’re not familiar with programming or at least the internal workings of Avast source code, I suggest you stop replying as I’m very knowledgeable of PCs, programming, cryptography and how they work and I’m definitely not your average Avast customer.
Well, actually, i have friends that have the same issue, however i haven’t experienced this before. Although over the time I’ve heard about a lot of complaints about CPU issues related to avast.
Ok, after a little bit of digging and analysis, it turns out that the culprit was Avast Antirootkit. It randomly triggers a scan that takes 30 MIN. AND TAKES UP 25% of my CPU!? This is normally fixed by disabling Rootkit Detection in Core Shield, however it is not recommended. Buy boy, I sure wish Avast would fix this and make this feature less taxing on the CPU.
The output is recorded in “C:\ProgramData\AVAST Software\Avast\log\aswAr.log”
