Skip to main content

High CPU Demand

Thread needs solution

Hi, The application is really dragging performance down. When installed it seems to be responsible for consuming upwards of 70% of the available CPU. When uninstalled the demand is way down on this, I dont know why this is happening. The other machine that I have acronis on does not suffer from this problem. I use both machines for my work and find the Dell M6800 Precision Workstation practically useless for workflow due to the lag between action and response.

It used not to be this way, I dont believe that I have changed the system architecture in any way, can you offer any insight as to why this might be happening. I have an attached Buffalo NAS drive LS-QL815 and run Bitdefender as a virus/firewall.

Has Acronis implemented an "intelligent" program that runs in the background. What can I shut down in the background that may return performance to where it was before?

Attachment Size
cpu_demand.jpg 120.19 KB
0 Users found this helpful

My Apologies pending,

Spent time to uninstalled a series of programs added over the last six months, reinstalled of most of these including acronis. The problem may have been deeper than acronis.

Previously only went as far as uninstalling acronis and virus scanning program; this seemed to be when cpu demand issues began; and this has appeared to return CPU demand to 'normal'. Now it seems that it may have been something else. The rebuilding of the system from where it was 6 months ago may have fixed it. Now have NET framework 4.6.1 where as had 4.5.2 previously (this may have been a bit 'dirty' due to issues with another program install issues). I've done all this on wifi network link - will plug back into ethernet cable network tomorrow and see if it behaves well in this as well.... There seemed to be different behaviour between the two previously - dont know why.

Hopefully all well - again apologies.

PD, thanks for following up and providing feedback on your situation!  

I agree that windows can get "dirty", even on a seemingly healthy system.  I installed Win 10 fresh after i upgraded to it the first time.  Then I rebuilt and installed all apps and had what I considered a pristine system for about 6 months. Then, I started having VSS errors that prevented backups from running out of the blue but noticed other weird Windows log issues too and soon had other strange issues that I wouldn't have come across if I hadn't started digging more.  Unfortunately, Windows is also constantly upgrading and updating itself, as well as all of the third party apps and whatever scanning and AV tools we all use and sometimes background OS issues happen without our knowledge.  Add different hardware issues (dirty drives, etc) and 2 seeminlgly similar builds can have completely different operations and reliability.

I originally dis an inplace "upgrade" again which I figured would resolve things, but still had all kinds of weird issues. Decided it would save time and lost hair in the long run to just start clean again and things have been fine on the entire OS for another 6 months and am hoping they stay that way again.

Rebuilding the OS almost always solves these issues, but there are few of us who actually want to do that (even though that is usually the best/cleanest option).