There are a lot of different ways to troubleshoot ASP.NET issues.  I have gone over most of the things you can do with a dump that has been captured from the process.  But there is another way to get useful information out of a process and that is by using a profiler. There are a number of profilers that are available for .NET applications.  Some of the more popular ones include (most come from Brads post and there is a good list here as well): Traditional Performance and/or Memory Profilers AutomatedQA AQTime: http://www.automatedqa.com/products/aqtime/index.asp (evaluation version available) Borland Optimizeit: http://www.borland.com/opt_profiler/ (evaluation version available) Compuware DevPartner: http://www.compuware.com…(read more)