CSISYNCCLIENT.EXE process claims high CPU usage

Hello,

I'm experiencing high CPU usage which is causing my computer to function very slow. In the task manager I see the process CSISYNCCLIENT.EXE a lot and using much CPU. Is there a way to stop this process from using so much CPU?

Rebooting the computer solves it for a moment, but the CPU slowly reaches it's maximum again after a while.

Is there a solution for this?

Thanks in advance!

Rense

July 17th, 2014 9:21am

Hi,

CSISYNCCLIENT.EXE is the Microsoft Office Document Cache Sync Client Interface that belongs to Microsoft Office 2013.

Please go to your Microsoft Upload Center 2013 and see if you have any pending documents. Try to cancel the uploading process or wait for the completion, then verify result.

Also, please make sure to install any available updates of your Office 2013 installation, then reboot your computer and try again. User reported that the June Windows Updates fixed the issue.

Hope this helps.

Thanks,

Ethan Hua CHN
TechNet Community Support

Free Windows Admin Tool Kit Click here and download it now
July 18th, 2014 5:52am

Hi Ethan,

The only thing I see is that the problem seems to occur since Service Pack 1 for Office 2013 was installed. I'm going to delete this update and see if this fixes the issue.

Rense

July 18th, 2014 10:41am

Hi,

How is it going? You should first try to install the updates and then verify result. If that doesn't fix the issue, then you can go and uninstall the Service Pack.

Thanks,

Ethan Hua CHN
TechNet Community Support

Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2014 9:59am

Hello,

I did a system recovery to the date the issue started. No problems anymore. I installed all the updates except the Service Pack 1 update. Still no problems, so I'm going to leave it with this. Everything is working and I'm not taking any risks by installing the SP1 update again.

Rense

  • Marked as answer by Rense H Wednesday, July 23, 2014 10:04 AM
July 23rd, 2014 10:04am

So, here we are almost 3/4 of a year later (or more based on some of the other blogs) with no solution.  At home, we have 2 Surface Pro 3 systems, a Lenovo Yoga Pro Tablet 2 10" (the one that just came out), and a Surface Pro 2.  All four systems are running Office 2013 (the one that's locally installed from our cloud account that we pay for each year) along with OneDrive.  

I sorted the Task Manager Processes by CPU, and this is what I found:

- The Surface Pro 2 shows the OneDrive Sync Engine and the Document Cache Sync Client running at the top of the Task Manager every once in a while for a few seconds, then they go back to the 0% of CPU.  The fan is hardly ever running and the system stays cool to the touch.
- The Lenovo does not show the Sync Client at the top of the Task Manager, but it does show the Microsoft Office Document Cache as taking up about 40% of the CPU for a few seconds every once in a while, then it drops to 0%.  The system does not have a fan, yet it does not get hot.
- Both of the Surface Pro 3 systems show that the Sync Client constantly (and I do mean constantly) uses 30-50% of the CPU and causes the systems to get very hot and keep the fan running at what sounds like full speed when the systems are turned on.  I don't remember this happening when I first bought them.
- When I uninstalled Office 2013 from one Surface Pro 3, the fan slowed down over a few minutes and the system returned to a normal cool temperature.  OneDrive Sync Engine and the Sync Client have disappeared.

I note that the Lenovo has an Intel Atom processor with 2G RAM and 32G drive.  OS is 32bit on an x64-based processor.  The Surface Pro 2 has an i5 with 8G RAM and 512G drive. OS is 64bit on an x64-based processor.  The Surface Pro 3 is the same i5 also with 8G RAM but only 256G drive.  OS is also 64bit on x64-based processor.

I guess my question is why do these three types of systems have different experiences with OneDrive???  Shouldn't it all work the same???

Free Windows Admin Tool Kit Click here and download it now
March 31st, 2015 9:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics