Connecting windbg and looking at stack trace shows this:
0: kd> kn
ChildEBP RetAddr
00 818f1ca8 818d69f4 nt!RtlpBreakWithStatusInstruction
01 818f1cb0 818285e5 nt!KdCheckForDebugBreak+0x22
02 818f1cd0 8189056d nt!KeUpdateRunTime+0x270
03 818f1cd0 81bb42a6 nt!KeUpdateSystemTime+0xed
WARNING: Frame IP not in any known module. Following frames may be wrong.
04 818f1d50 81891272 0x81bb42a6
05 818f1d54 00000000 nt!KiIdleLoop+0xa
The current workaround to get across this hang has been to hit a “g”, kill
windbg and restart fresh windbg session. “Just hitting go” doesnt seem to
help.
Has anyone see similar problem? Does anyone know the problem/solution apart
from this workaround?
Regards,
-Praveen