Mike's got an interesting piece up today about using WinDbg to find the actual call stack of an unmanaged (or managed for that matter) exception.  It's this kind of power debugging technique that makes WinDbg my all time favorite debugger.