title: Newbie at dotNet dump analysis
body: <p>I am working with a multi-threaded application, which should reguarly be launching a thread, asking about the status of some &quot;cars&quot;.<br />
  As one of the threads is still working (visible in Process Explorer and in the &quot;Threads&quot; part of the memory dump), I believe I'm dealing here with a deadlock.<br />
  In order to investigate this, I have downloaded <code>dotnet-dump</code> and I launched the following command in commandline:</p>
  <pre><code>Prompt&gt; dotnet-dump.exe analyze &quot;Dumpfile.DMP&quot;
  </code></pre>
  <p>Once inside this <code>dotnet-dump</code> session, I have tried launching <code>clrstack -all</code>, as indicated in <a href="https://docs.microsoft.com/en-us/dotnet/core/diagnostics/debug-deadlock?tabs=windows" rel="nofollow noreferrer">this URL</a>.</p>
  <p>This, however, seems not to be working:</p>
  <pre><code>&gt; clrstack -all
  Failed to load data access module, 0x80004002
  Can not load or initialize mscordacwks.dll. The target runtime may not be initialized.
  
  For more information see https://go.microsoft.com/fwlink/?linkid=2135652
  &gt; setsymbolserver -ms
  Added Microsoft public symbol server
  &gt; clrstack -all
  Failed to load data access module, 0x80004002
  Can not load or initialize mscordacwks.dll. The target runtime may not be initialized.
  
  For more information see https://go.microsoft.com/fwlink/?linkid=2135652
  </code></pre>
  <p>I have followed the advise in that webpage but no success.<br />
  In top of this, I have different &quot;mscordacwks.dll&quot; files on my PC. How can I know which one to take?<br />
  Or even better, is there an easier way to investigate a dotNet memory dump for deadlock analysis?</p>
  <p><strong>Edit:</strong> For your understanding: I have the application open in Visual Studio, but I know from previous experience that tools like &quot;Windbg&quot; have commands like <code>!locks</code> which can be used for (dead)lock analysis. While searching on how to investigate (dead)locks in .Net, I stumbled upon the <code>dotnet-dump</code> tool.</p>