Very high CPU utilization caused by SEP Client (ccSvcHst.exe) by certain Windows Power Management Modes.


Article ID: 169514


Updated On:


Endpoint Protection


It has been observed that, when a Power Scheme with lower consumption is set, SEP Client (ccSvcHst.exe) starts to utilize up to 90% of CPU making a computer unresponsive / unusable. 


Certain Power Management Modes in Widows Operating Systems allow portable computers to shut down or set into a sleep mode some functionalist in order to save power. Most common ones, are to disable screen or other components like WiFi module:


With Windows Power Management Modes users can also set custom Power Schemes:


When a Power Scheme with lower consumption is set, operating system will disable the unused cores in a multicore CPU`s during an idle time in order to save power. This operation will left less CPU computing capability to the SEP Client that is already running, which most likely will lead the SEP Client to utilize the most resources that left available.

When CPU cores are disabled during the idle time a System Event 37 is being logged by Kernel-Power with following details:


Log Name:  System

Source:        Microsoft-Windows-Kernel-Processor-Power

Event ID:      37

Task Category: (7)

Level:           Warning


The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.


Check your current Power Scheme in "Power Options" applet of Control Panel.

If your current Power Scheme is set to low power consumption, you can either:


A. Modify the current Power Scheme to set Maximum Processor State to 100%:





B. Switch to High Performance Power Scheme:


C. Note also that the Power Management options can be found in most of the modern CMOS settings. Use your BIOS /UEFI console to adjust the power settings to maximum performance of the CPU. Settings may vary however depending on the motherboard, therefore review manufacturer`s motherboard / computer documentation.