A lot of it came down to time - both Chad and I are very busy in our day jobs and it got harder and harder to find the prep time. We also ran out of content that we do day-to-day. The big thing we never want/ed to do is present inaccurate information.
I'm tempted to tape a few episode on just some random dump debugging - for the fun of it. Would you like that?
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.