Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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're seeing an issue on our production servers where the processor is constantly at 100% utilization (between 2 or 3 w3wp processes). The weird thing is that there are almost no requests to the server, and the application associated with the offending processes is still performing well. By looking at IISPeek, almost nothing is happening on the server, so I'm not sure what else to check. Has anyone run into something like this? Thanks!

share|improve this question
Have you tried using DebugDiag to monitor what's going on? Otherwise, I'd suggest taking a process dump (eg using procdump) and examining it in WinDBG. – Adam Thompson Mar 23 '12 at 15:10
I used this tool (…), and see 'Microsoft.Win32.Win32Native.SetEvent' at the top, but that doesn't really give me any ideas. – Shane Fulmer Mar 23 '12 at 15:19

You should create a process dump and then use either Windbg or Visual Studio to analyse the dump and figure out what the process is doing. Here's a guide.

share|improve this answer

The issue here was related to sending an email from .NET 2.0. We set ServicePoint.MaxIdleTime = 1, which resulted in the connection staying open and consuming CPU in the background.

EDIT: After a little more research, this was actually our exact issue:

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.