The past couple weeks I have noticed the CPU used by "System" in Task Manager stays between 25 and 50%, even when the system is idle, on a Haswell i7 system.
Looking in process explorer, which doesn't always launch successfully, it shows all the CPU heavy threads to be in covefs.sys. The CPU heavy threads have > 10K context switches per second.
When I first noticed this, I had no antivirus running, as lately I have been having an impossible time finding one that doesn't conflict with Windows Media Center Extender usage. I have since been running MSSE and scanned with MalwareBytes as I feared it could be some malware making the usage high.
First noticed the issue with the stable release (x64), upgraded to the beta and the problem persists.
It really doesn't make sense, as there hasn't been an update to DrivePool itself in a long time when this first started. The pool was expanded from 4 drives to 6 about two months ago. Any ideas?
Edit: Actually, come to think of it, the timing of this issue is roughly when I stopped using BitDefender, as it kept WMC extenders from connecting after an update. And even after uninstalling it, it turned out Windows Defender which got turned on as part of the update process was actually blocking the connections. When I figured that out, I was unable to reinstall BitDefender. Maybe some remnant of it is still around causing the CPU usage?
Question
glugglug
The past couple weeks I have noticed the CPU used by "System" in Task Manager stays between 25 and 50%, even when the system is idle, on a Haswell i7 system.
Looking in process explorer, which doesn't always launch successfully, it shows all the CPU heavy threads to be in covefs.sys. The CPU heavy threads have > 10K context switches per second.
When I first noticed this, I had no antivirus running, as lately I have been having an impossible time finding one that doesn't conflict with Windows Media Center Extender usage. I have since been running MSSE and scanned with MalwareBytes as I feared it could be some malware making the usage high.
First noticed the issue with the stable release (x64), upgraded to the beta and the problem persists.
It really doesn't make sense, as there hasn't been an update to DrivePool itself in a long time when this first started. The pool was expanded from 4 drives to 6 about two months ago. Any ideas?
Edit: Actually, come to think of it, the timing of this issue is roughly when I stopped using BitDefender, as it kept WMC extenders from connecting after an update. And even after uninstalling it, it turned out Windows Defender which got turned on as part of the update process was actually blocking the connections. When I figured that out, I was unable to reinstall BitDefender. Maybe some remnant of it is still around causing the CPU usage?
Link to comment
Share on other sites
6 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.