title: Analysing crash dump in windbg
body: <p>I am using a third party closed source API which throws an exception stating that "all named pipes are busy".</p>
  
  <p>I would like to debug this further (rather than just stepping through) so I can actually learn what is happening under the covers.</p>
  
  <p>I have taken a dump of this process using WinDbg. What commands should I now use to analyse this dump?</p>
  
  <p>Thanks</p>