I just watched a Channel 9 episode on doing some hard core debugging of blue screens in windows. Not for the faint of heart, but definitely doable if you are a developer and familiar with the Windows memory system. The two tools they used were WinDBG (part of debugging tools for windows) and verifier (comes with windows). If you've read Debugging .NET 2.0 Applications (which if you haven't and you are a .NET programmer, go read it now!), then you should be familiar with WinDBG. It is an excellent tool for user mode debugging of applications. In this episode, they used WinDBG only briefly, to open the dump file, get the bug check code and run !analyze. The !analyze tool returned additional information which pointed them to run verifier. Still working through, will update as I get up to speed more.
To see the episode go to: Channel 9