<p>I am working on an ASP.NET web application, it seems to be working properly when I try to debug it in Visual Studio. However when I emulate heavy load, IIS crashes without any trace -- log entry in the system journal is very generic, "The World Wide Web Publishing service terminated unexpectedly. It has done this 4 time(s)."
How is it possible to get more information from IIS to troubleshoot this problem?</p>

[{'answer_id': 62732, 'author': 'Joel Coehoorn', 'author_id': 3043, 'author_profile': 'https://Stackoverflow.com/users/3043', 'pm_score': 0, 'selected': False, 'text': '<p>The key is <em>"without any trace"</em>.  You need to put your own trace logging in to create some chatter.  Then you\'ll be able to spot where the chatter stops.</p>\n'}, {'answer_id': 62741, 'author': 'Gulzar Nazim', 'author_id': 4337, 'author_profile': 'https://Stackoverflow.com/users/4337', 'pm_score': 2, 'selected': False, 'text': '<p>Crash dump of <a href="http://blogs.msdn.com/tess/archive/tags/ASP.NET/default.aspx" rel="nofollow noreferrer">asp.net process</a> should give you <a href="http://blogs.msdn.com/tess/pages/net-debugging-demos-information-and-setup-instructions.aspx" rel="nofollow noreferrer">tons of info</a>..If you want to quickly get some info on why the process got recycled, <a href="http://weblogs.asp.net/scottgu/archive/2005/12/14/433194.aspx" rel="nofollow noreferrer">try this tip from Scott Gu</a>..\n<a href="http://odetocode.com/Blogs/scott/archive/2005/11/01/2402.aspx" rel="nofollow noreferrer">Health monitoring</a> feature of asp.net 2.0 is also worth looking at..</p>\n'}, {'answer_id': 65553, 'author': 'sachaa', 'author_id': 1152057, 'author_profile': 'https://Stackoverflow.com/users/1152057', 'pm_score': 2, 'selected': False, 'text': '<p>Download Debugging tools for Windows:\n<a href="http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx" rel="nofollow noreferrer">http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx</a></p>\n\n<p>Debugging Tools for Windows has has a script (ADPLUS) that allows you to create dumps when a process CRASHES:\n<a href="http://support.microsoft.com/kb/286350" rel="nofollow noreferrer">http://support.microsoft.com/kb/286350</a></p>\n\n<p>The command should be something like (if you are using IIS6):</p>\n\n<pre><code>cscript adplus.vbs -crash -pn w3wp.exe\n</code></pre>\n\n<p>This command will attach the debugger to the worker process. When the crash occurs it will generate a dump (a *.DMP file).</p>\n\n<p>You can open it in WinDBG (also included in the Debugging Tools for Windows). File > Open Crash dump...</p>\n\n<p>By default, WinDBG will show you (next to the command line) the thread were the process crashed.</p>\n\n<p>The first thing you need to do in WinDBG is to load the .NET Framework extensions:</p>\n\n<pre><code>.loadby sos mscorwks\n</code></pre>\n\n<p>then, you will display the managed callstack:</p>\n\n<pre><code>!clrstack\n</code></pre>\n\n<p>if the thread was not running managed code, then you\'ll need to check the native stack:</p>\n\n<pre><code>kpn 200\n</code></pre>\n\n<p>This should give you some ideas. To continue troubleshooting I recommend you read the following article:</p>\n\n<p><a href="http://msdn.microsoft.com/en-us/library/ms954594.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms954594.aspx</a></p>\n'}]
['https://Stackoverflow.com/questions/62720', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/6954/']