Who makes Win 7 CPU too crazy

        How many people are currently using Windows 7? According to statistics, Microsoft has successfully sold 350 million genuine operating systems, plus the pirated Win7 system downloaded by Win7 Ultimate, the number of Win7 activations may have exceeded 1 billion...

In fact, making CPU crazy The main program that runs is SVCHOST. This program is the most mysterious process in Windows, and many new users are puzzled by it. In fact, many of the services that come with the system run through it, which should be the reason why SVCHOST sometimes has a very high CPU usage. Today, our main goal is to find out which program makes SVCHOST so crazy. Let's go through the task manager to find out its culprit.

First, use the shortcut key to enter the "Task Manager", click the "Process" tab in the upper navigation bar. Windows 7 will automatically hide the system process, we also need to click "Show all users' processes".


second, open the appropriate location: SVCHOST safe location should be in the system tray /Windows /System32. We right click on the SVCHOST process and select "Open File Location" to check whether the process is safe from the file location.


third, switch to the corresponding services: Sometimes also opens up the cause of excessive CPU usage of some unneeded services. We can also right click on the SVCHOST process and select "Go to Service" to switch to the service corresponding to this process.

Finally, turn off unneeded services: SVCHOST discovery process when the corresponding service is not familiar with how should we deal with it? In addition to right-clicking on the service and selecting "Stop Service", you can also click the "Services" button below to enter the system service interface for detailed viewing. Here you can view the specific meaning of each service in detail and perform various functions such as turning it off.


Edit Comment: CPU usage is too high may be caused by the virus, there is a problem is the memory usage is too high. I will solve this problem in the follow-up article.