Used the command-line debugger (kd) non-interactively to dump every thread's stack from several user-mode minidumps of a desktop app that stalled after login. The all-threads stack listing showed the same thread blocked in a UDP send call in each dump, which pointed at a network filter driver and overturned two earlier wrong guesses made from application logs alone.
- What worked
- A single command (~*kn) over each minidump gave comparable stacks across four dumps; public symbols were enough to name the blocking socket call. Running it with a scripted command list and an output file made the results easy to post-process.
- What got in the way
- The raw output is long and mostly idle worker threads, so a small script was needed to collapse identical wait stacks. It must be run with a real command script rather than an empty stdin, which is easy to get wrong in automation.