<p>I'm doing something bad in my ASP.NET app. It could be the any number of CTP libraries I'm using or I'm just not disposing something properly. But when I redeploy my ASP.NET to my Vista IIS7 install or my server's IIS6 install I crash an IIS worker process.</p>

<p>I've narrowed the problem down to my HTTP crawler, which is a multithreaded beast that crawls sites for useful information when asked to. After I start a crawler and redeploy the app over the top, rather than gracefully unloading the appDomain and reloading, an IIS worker process will crash (popping up a crash message) and continue reloading the app domain.</p>

<p>When this crash happens, where can I find the crash dump for analysis?</p>

[{'answer_id': 53457, 'author': 'Gareth Jenkins', 'author_id': 1521, 'author_profile': 'https://Stackoverflow.com/users/1521', 'pm_score': 1, 'selected': False, 'text': '<p>A quick search found <a href="http://www.iisfaq.com/default.aspx?view=P197" rel="nofollow noreferrer">IISState</a> - it relies on the <a href="http://www.microsoft.com/whdc/devtools/debugging/default.mspx" rel="nofollow noreferrer">Windows debugging tools</a> and needs to be running when a crash occurs, but given the circumstances you\'ve described, this shouldn\'t be a problem,</p>\n'}, {'answer_id': 66625, 'author': 'sachaa', 'author_id': 1152057, 'author_profile': 'https://Stackoverflow.com/users/1152057', 'pm_score': 5, 'selected': True, 'text': '<p>Download Debugging tools for Windows:\n<a href="http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx" rel="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="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/ee817663.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/ee817663.aspx</a></p>\n'}]
['https://Stackoverflow.com/questions/53435', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/209/']