If you work with .NET ,best place to learn all common scenarios like hang,crash,high memory are Debugging Demos https://blogs.msdn.microsoft.com/tess/2008/02/04/net-debuggi...

Many troubleshooting steps in that blog also covers DebugDiag .DebugDiag is an amazing tool which can help you collect dumps automatically for crash,high memory,IIS slow response etc.

Another tool which can help you profile your applications easily is PerfView https://channel9.msdn.com/Series/PerfView-Tutorial .

Perfview is built on the (Windows Event tracing) ETW infrastructure windows have .You can think of it as Lttng or perf_events linux equivalent but built into everything windows have. I think process monitor is also built on ETW. After debugging ( which is not required for lot of scenarios) the most powerfull thing in troubleshooting any issues in Windows is ETW traces IMHO.So understanding and analyzing ETW will help you troubleshoot a lot of issues.

https://blogs.msdn.microsoft.com/ntdebugging/2009/08/27/part...

XPERF is built to consume ETW traces https://blogs.msdn.microsoft.com/ntdebugging/tag/XPERF/ https://blogs.technet.microsoft.com/askpfeplat/2013/03/22/tr...

Also Advanced Windows debugging[1] and Advanced .NET debugging[2] to be very good for learning debugging in windows land.

[1] http://www.amazon.in/Advanced-Debugging-Addison-Wesley-Micro... [2]https://www.amazon.com/Advanced-NET-Debugging-Mario-Hewardt/...

If you're working with .net code that uses finalizers (especially if those sections were written by people unlikely to read articles like this, though good programmers screw this up too), chances are that there are latent issues in your application that will manifest as sudden application crashes with little to no debugging information.

I found myself in such a situation. Books like Advanced .NET Debugging [1] will help you regain your sanity.

[1] http://www.amazon.com/Advanced-NET-Debugging-Mario-Hewardt/d...