Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Download Debugging tools for Windows: <a href="http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx" rel="noreferrer">http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx</a></p> <p>Debugging Tools for Windows has has a script (ADPLUS) that allows you to create dumps when a process CRASHES: <a href="http://support.microsoft.com/kb/286350" rel="noreferrer">http://support.microsoft.com/kb/286350</a></p> <p>The command should be something like (if you are using IIS6):</p> <pre><code>cscript adplus.vbs -crash -pn w3wp.exe </code></pre> <p>This command will attach the debugger to the worker process. When the crash occurs it will generate a dump (a *.DMP file).</p> <p>You can open it in WinDBG (also included in the Debugging Tools for Windows). File > Open Crash dump...</p> <p>By default, WinDBG will show you (next to the command line) the thread were the process crashed.</p> <p>The first thing you need to do in WinDBG is to load the .NET Framework extensions:</p> <pre><code>.loadby sos mscorwks </code></pre> <p>then, you will display the managed callstack:</p> <pre><code>!clrstack </code></pre> <p>if the thread was not running managed code, then you'll need to check the native stack:</p> <pre><code>kpn 200 </code></pre> <p>This should give you some ideas. To continue troubleshooting I recommend you read the following article:</p> <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>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload