The dllhost exe process consumes 100 CPUs

1. The dllhost process causes 100% CPU usage to be occupied

Features: The normal CPU consumption of the server should be below 75%, and the CPU consumption should be up and down, the server with this problem, the CPU will suddenly be at the 100% level, and it will not drop. Looking at the task manager, you can see that it is consuming all the CPU idle time, and the administrator has to restart the IIS service in this case, and the strange thing is that everything works fine after restarting the IIS service, but maybe after a while, the problem reappears.

Direct cause: One or more access databases are corrupted during multiple reads and writes, and when Microsoft's MDAC system writes this corrupted access file, the asp thread is in a block state, and other threads can only wait, IIS is deadlocked, and all CPU time is consumed in dllhost.

Solution: Install the "First-in-Class Information Monitoring and Interception System", use the "Chief Document Inspector IIS Health Inspector" software, enable the "Find Deadlock Module", and set up:

wblock=yes

The directory to be monitored, specify the directory where your host's files are located

wblockdir=d:\test

The file file for monitoring the generated logs is stored in the log directory of the installation directory with the file name:

Stop the IIS, start the "Chief Document Inspector IIS Health Officer" again, and start the IIS again, and the "Chief Document Inspector IIS Health Officer" will record the last written access file in .

After some time, when the problem comes up, for example the CPU will be at 100% all the time again, you can stop the IIS, check the last ten files that have been recorded, note that the most problematic is often the access file of the counter class, for example: "*count.".mdb", you can delete the last ten files or suspicious files to the ** site, and then start IIS to see if the problem reappears.

We are confident that after a careful search, you will definitely be able to find this file that has been worrying you for a while.

Virus. I've been hit too.

This situation is likely to be poisoned, so let's kill it after updating the virus database.

Delete this program.

Cause analysis: 1. Some test public beta drivers may occupy 100% of the CPU, first of all, you need to rule out whether a new driver has been installed recently.

2. If the process occupies 100% of the CPU after booting, it may be that the system comes with a virus scanner.

3. Some anti-virus software may occupy the process to monitor some web pages, programs, software, plug-ins, etc., which may increase the load on the CPU, you can turn off some monitoring of anti-virus software.

4. Virus infection, Trojan poisoning, etc. will also cause the process to occupy too much CPU, and the Trojan horse will inject into the process. It is recommended to install the anti-virus software to check for viruses and check whether it is poisoned, and it is recommended to use 360 and NOD32 for scanning.

Troubleshooting method: Method 1:

1. Press CTRL+ALT+DELETE to open the task manager, find the program with a high CPU occupation, and right-click to go to service.

2. In the service of the task management blocker, you can see what service the current process is occupied by, so as to stop the corresponding service to troubleshoot. As you can see from the figure below, Windows Defender is occupying a process, which is a built-in antivirus scanner for Windows. The effect is not good, it is recommended to disable this service and install antivirus software by yourself.

Method. 2. Use the command that comes with the system, open the start menu--- run--- enter cmd, click OK, and then enter tasklist svc to list which services the current process is occupied by. The principle is actually the same as method 1.

Poisonous, I don't know what you use to kill the virus, it is recommended to kill it with Kaba.

Yes, or is it? If it is a system process, but if it is, it may be the own program of the Dell brand machine, and it is more likely to be a virus! In addition, Li Nao dllhost, do you have IIS installed? Could there be a problem with the IIS performance configuration?

In addition, I will provide you with some ideas: (check the drug first, and then proceed to the following if you can't find it).

1. Check the boot auto-start item, you can use autoruns or sreng, especially the DLL check;

2. Use procexp to check what can be modules inside the two processes currently running, and if so, determine their location so that they can be killed later;

3. When they occupy the CPU at full capacity, they use Procmon (Filemon, Regmon) to monitor what they are doing, and determine the files and registry entries that are related to them, so that they can be killed together afterwards.

4. If you really find out the virus and Trojan program or driver, delete it if you can't delete it, and delete it with force, such as xdelbox or powerrmv, etc. Before deleting, it is best to fix the problematic parts of the registry first, so as not to enter the system after deletion.

Windows is installing an update, and it won't be done after the installation.