My Win7 optimization documentary 1 --- Service Management sometimes clearly does not run any program, but the CPU usage remains high, which is often caused by some Win7 self-starting services. These services may be designed to optimize system performance and increase CPU utilization during idle hours. However, for most users, these services are all pitfall! We need to manually start or simply disable it based on the actual situation. Here are a few services that once made my CPU usage as high as 100%: SSDP Discovery Service Description: "When you find network devices and services using the SSDP protocol, such as UPnP devices, the SSDP devices and services running on the local computer are also reported. If you stop this service, SSDP-based devices will not be found. If this service is disabled, any service dependent on this service cannot be started normally ." Corresponding process: svchost.exe suggested processing method: switch from automatic failover to manual failover. When the svchost.exe process consumes too much CPU, stop this service. (Because of the dependency, you need to stop the UPnP Device Host Service First) UPnP Device Host Service Description: "allow the UPnP Device to Host on this computer. If you stop this service, all the host's UPnP devices stop working and cannot add other host devices. If this service is disabled, any services explicitly dependent on it cannot be started ." Corresponding process: svchost.exe suggested processing method: switch from automatic failover to manual failover. When the svchost.exe process consumes too much CPU, stop this service. Microsoft. NET Framework NGEN Service Description: Pre-compiled in the background. net assemblies (SET) [New Service after VS2010 is installed] corresponding process: mscorsvw.exe suggested processing method: changed from "automatic" to "disabled"