I see all the dedicated app pools that I already have running. But for this PID here is what I get, which is not a lot of help.

W3WP.exe PID: 5908   AppPoolId: ASPNET2

So is there a way to further peek into the ASPNET2 Pool and see what is in there? This doesn't really seem to provide anything more that the Task Manager.

I may just have to start moving every site to a dedicated app pool until one jumps out as being the big consumer. It is just that I have several dozen sites and it will take a little while to see if this will work, in addition to consuming all my RAM by setting up so many app pools. I get I could just move them one at a time out to a dedi pool see if it provides any clues and then move it out of dedi and then move to the next site.

Thanks.

OK, I got the Process ID and associated it with a particular app pool. This is a generic ASPNET2 pool that has about 60 sites it it. Most of these sites have very little activity. But I am sitting here with my CPU between 80 - 99% on this w3wp.exe in task manager. So in IIS I opened up the pool to list the sites and then opened up the sites below it and quickly ran down the line of all the sites in the pool and STOPPED every website. I left them all off as I quickly did this. So now every site in this pool is stopped and I am still pegged at 96% CPU with only about 185MB Memory Usage.

I went back and turned on all of the client sites and still left some of my personal sites off for now.

So what kind of a clue is this. Does it mean that it has to do more with some type of scheduled process that is kicked off and then runs external to the site? Is there a tool that I can use to further peek into the w3wp.exe? 

I am at a loss but this is killing me.

Thanks for any suggestions you all have.

OK Mitch I will try that. I also got a trial of www.iispeek.com to see what it can tell me. It can put out a lot of info, I am not quite sure how to figure out what it all means though. You can get it free for 24 hours, then it is only $30 to purchase if it looks like a useful tool.

Once today I did a full IIS reset and obviously the issue went away for a while and then came back. It is not quite as bad now. It seems to be sticking around 50% CPU. So after I stop all sites and kill the process for that app pool, do I just start back one site at a time. I am not sure that will tell me anything because it may require hitting a certain page on a site to trigger this or for a particular scheduled event to kick off or something.

What is your recommendation after I get a clean worker process? I could start the process of creating additional app pools and then move half the sites to the new one. After doing that a couple of times I might be able to narrow it down a little.