Analysing crash dump in windbg

Question

I am using a third party closed source API which throws an exception stating that \"all named pipes are busy\".

I would like to debug this further (rather than just step

Answer 1

This is an excellent resource for using WinDbg to analyze crashes that may be of some use: http://www.networkworld.com/article/3100370/windows/how-to-solve-windows-10-crashes-in-less-than-a-minute.html

The article is for Windows 10, but it contains links to similar information for earlier versions of Windows.