Stack Overflow is an interesting error type. It is handled in the kernel, rather than user mode -- primarily to block bad code (viruses, etc.) from handling the error, and moving on (i.e. keeping themselves hidden).
In this situation, WER does not give the AeDebugger the chance to be involved -- instead it takes the dump directly.
All of the new !black* commands are great to leverage for any hang related analysis. The blackbox secondary streams are added by the hang bugcheck codes (E2, 1C8, etc.). !analyze reads the data to aid decisions.
@Templaar:Yes -- definitely are still alive :) We've got a few shoots in edit now.
RS2 end-game kept me (Andrew) too busy to find time for it, Chad's been flying the world a lot to talk to Partners, and //build/ closed the Channel 9 studios (they do 300+ pre-shoots) for weekly shows.
Keep the show ideas coming - to email@example.com -- after 170+, we're running out of tools that haven't been covered -- and that we can find an expert for.
If you'd like to see re-visits (second deep-dive) of certain tools -- we can do that for sure.
And I'm always up for just showing random debugging tips.