Been seeing that Windbg 6.11.1.402 has not been very stable on resume from Sleep using Vista32. Does not happen every time, but often enough to be an issue.
Once the error below is hit, if I close Windbg and try to reopen it and select the 1394 port I was using, Windbg immediately exits. i.e. once you get into the state below on resume from S3, you are out of luck. Any ideas, or have others been seeing this?
From the Command Window:
HAL: Delta : 22b9290
Assertion failure - code c0000420 (first chance)
Unable to read KTHREAD address a532aa58
nt!KeUpdateRunTime+0x152:
820d12ef cd2c int 2Ch
Unable to read KTHREAD address a532aa58
Unable to read KTHREAD address a532aa58
Unable to read KTHREAD address a532aa58
Unable to read KTHREAD address a532aa58
0: kd> kv
GetContextState failed, 0x80070038
Unable to get current machine context, Win32 error 0n56
GetContextState failed, 0x80070038
Unable to get current machine context, Win32 error 0n56
^ Illegal thread error in ‘kv’
0: kd> !reload
Debugger can’t get KD version information, Win32 error 0n56
Unable to read KTHREAD address a532aa58
**************************************************************************
Unable to read debugger data block header
**************************************************************************
Unable to read KTHREAD address a532aa58
Unable to read PsLoadedModuleList
Unable to read KTHREAD address a532aa58
**************************************************************************
Unable to read debugger data block header
**************************************************************************
Unable to read KTHREAD address a532aa58
Unable to read KTHREAD address a532aa58
Unable to read KTHREAD address a532aa58
Unable to read KTHREAD address a532aa58
Loading Kernel Symbols
Unable to read KTHREAD address a532aa58
Unable to read PsLoadedModuleList
Unable to read KTHREAD address a532aa58
…
** If I close WinDbg and try to reopen it on the same 1394 port, it exits immediately from this point on - until I reboot the debug system.