When it comes to trouble shooting the first and most important tool you need is your brain.
Besides that there are couple of other tools that help you collecting & analyzing data.
In this post I'm going to name and list a view of them that I discovered over the past years (and in my first month at Microsoft) and shortly describe what they do and what target scenario they are most useful in.
WinDBG Extension: PSSCore2
WinDBG Extension: PSSCore4
Processes that stop responding (that is, hang).
Processes that have 100 % CPU utilization on a single processor computer, 50 % utilization on a dual processor computer, 25 % utilization on a quad processor computer, and so on.
Processes that fail (that is, crash) or shut down unexpectedly.
issues such as hangs, slow performance, memory leaks or fragmentation, and crashes in any user-mode process. The tool includes additional debugging scripts focused on Internet Information Services (IIS) applications, web data access components, COM+ and related Microsoft technologies.
It looks like your links are messed up, can you get them fixed up?
Sorry for the incorrect links ... I got them fixed.
Don't forget pro dump. I would replace adplua with that since it is much more versatile.
Never heard of pro dump before. Can you sahre a link?
I think he means ProcDump from Sysinternals
Could it be useful spending some words about configuring the debugging symbols?
I have symbols and sources configuration on my list... Are you interested in specific tools to be configured or more a general explanation?