How to solve the CPU resources full

1, the driver has not been certified, resulting in 100% of CPU resources.

A large number of beta drivers are flooding the web, causing difficult to find fault causes.

2, anti-virus software CPU utilization rate occupies 100%

Now the anti-virus software is generally added to the Web page, mail, personal privacy of the immediate monitoring of the function, this will undoubtedly increase the burden of the system. For example: When playing a game, it will be very slow. Shutting down the antivirus software is the most straightforward solution.

3, virus, Trojan caused.

A CPU occupancy rate of 100% failure is often caused by a virus trojan, such as shock wave virus. You should first update the virus library and scan your computer for the whole machine. Next, use the antispyware ad-aware to check for spyware. Many friends on the forum have encountered Svchost.exe occupy cpu100%, this is often the performance of poisoning.

System services in Svchost.exe are implemented as dynamic-link libraries (DLLs), some of which point an executable program to Svchost.exe, which invokes the corresponding service's dynamic-link library and adds the appropriate parameters to start the service. It is precisely because of its specificity and importance that makes it easier to become the host of some virus Trojans.

A large number of worms are rapidly replicating within the system, resulting in high CPU utilization. Solution: Use the latest anti-virus software in DOS mode for antivirus. Update anti-virus software and firewalls regularly, strengthen anti-virus awareness, master the correct anti-virus knowledge.

4, start-> run->msconfig-> start, turn off unnecessary startup items, restart.

5, the network connection causes the CPU utilization rate to occupy 100%

View network Connections. Mainly is the network card. When your 2000/xp is a server, when you receive a connection request from port 445, the system allocates memory and a small amount of CPU resources to service these connections, which occurs when the load is overloaded. To solve this problem can be resolved by modifying the registry, open the registry, find Hkey-local-machnesystemcurrentcontrolsetserviceslanmanserver, and create a new name on the right; MaxWorkItems "; then double-click the value, if your computer has more than 512 memory, set to 1024, if less than 512, set to 256.

6, view "Svchost" process

Svchost.exe is a core process of the XP system. Svchost.exe not only appears in XP, but there are Svchost.exe in systems that use NT kernels. In general, the number of Svchost.exe processes in 2000 is 2, while the number of Svchost.exe processes in XP has risen to 4 and more than 4.

How can you tell which are the normal Svchost.exe processes and which are the virus processes?

The Svchost.exe key value is in "HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows Ntcurrentversionsvchost", and each key value represents a separate Svchost.exe group.

Microsoft also provides us with a way to see how the system is running services in the Svchost.exe list. As an example of XP: In Run, enter: cmd, and then enter in the command line mode: Tasklist/svc. The system lists the list of services. If you are using a 2000 system, replace the previous "tasklist/svc" command with the following: "Tlist-s".

If you suspect that your computer may be infected with a virus, Svchost.exe services can find anomalies by searching for Svchost.exe files. In general, you will find only one Svchost.exe program in the "C:windowssystem32" directory. If you find a Svchost.exe program in another directory, it is likely to be poisoned.

Another way to confirm that Svchost.exe is poisoned is to see the execution path of the process in the Task Manager. However, because the task manager in the system itself cannot see the process path, use a Third-party process viewer.

The above briefly describes the Svchost.exe process of the relevant situation. In short, Svchost.exe is a core process of a system, not a virus process. However, because of the particularity of the Svchost.exe process, the virus will do everything possible to invade Svchost.exe. You can confirm whether poisoning is possible by looking at the execution path of the Svchost.exe process.

7, the network card, video card, sound card Uninstall, and then install the driver again.

8, reload the system, the commonly used software, certainly also must install the drive.

Take a few days to see if this problem does not occur, and then install other software, but it is best to install a software, first in a few days. There are problems and then install!

Features: Server normal CPU consumption should be below 75%, and CPU consumption should be up and down, the server with this problem, the CPU will suddenly be at 100% level, and will not drop. Looking at task Manager, you can see that DLLHOST.EXE consumes all of the CPU idle time,

In this case, the administrator has to restart the IIS service, and strangely, after restarting the IIS service, everything is fine, but it may be some time before the problem comes up again.

Direct reason:

One or more Access databases are corrupted during multiple reads and writes, while Microsoft's MDAC system is writing to this corrupted access file, the ASP thread is in block state, and the other threads can only wait, IIS is deadlocked, and all CPU time is consumed in dllhost.

Solution:

Install the first class information surveillance interception system, using the "Chief File Checker IIS health inspector" software,

To enable the Find deadlock module, set:

--wblock=yes

Directory to monitor, specify the directory of your host's files:

--wblockdir=d:test

Monitor the file save location of the generated log in the log directory of the installation directory, the file name is: logblock.htm

Stop IIS, start the Chief File Checker IIS health inspector, and then start IIS, and the Chief File Checker IIS health inspector will record the last written Access file in Logblock.htm.

After a period of time, when the problem comes out, such as when the CPU is once again at 100% levels, you can stop IIS, check the last 10 files recorded by logblock.htm, and note that the most problematic is often the access file for the counter class, for example: "**count." MDB "," **count. ASP, you can first delete the last 10 files or suspect files to the Recycle Bin, and then start IIS to see if the problem occurs again. We believe that after careful searching, you can certainly find this file that has been bothering you for a while.