Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a webserver that's reacting slowly. It seems that a DLLHost.exe is the problem (taking ~100% Processor). How do we tell which dll in DLLHost is causing the problem. We've seen which ones are loaded with Process Explorer, but the list is 100 DLLs long. What tool or technique can we use to isolate the problem?

share|improve this question
up vote 1 down vote accepted

There's an excellent article on debugging high CPU usage of IIS. If you follow this you should be able to create a dump file that may help in determining which DLL is causing the problem.

Once you have determined what DLL is causing the problem its then a case of trying to find out what its doing, and what's causing an issue. Quite often, at least with DLL's written for custom software its because the code is stuck in a loop.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.