REVIEW Seeing occasional but recurring partial machine hangs in Windows 7, apparently related to the network layer. Basic UI elements continue working, it responds to ping, but the machine is unusable. Most processes (including Explorer) hang within seconds. Full report:
https://www.mail-archive.com/[email protected]/msg09319.html LATEST I have successfully created a couple crash dumps of a hung system using CrashOnCtrlScroll. These are kernel dumps (not full, not mini). I've installed Microsoft's currently recommended debugging tools. Visual Studio Express 2013 just says "Debugging older format crashdumps is not supported". WinDbg loads the crash dump, but I'm unsure on what to do next. The regular STOP/BugCheck/BSOD analysis steps don't help, because I forced the crash manually. The current process and call stack trace show stuff about the keyboard driver (which originated the BugCheck). I presume none of that is helpful. I found http://msdn.microsoft.com/en-us/library/windows/hardware/ff538042%28v=vs.85%29.aspx and have been trying things it suggests. !process lists processes, lm lists modules, !memusage lists memory usage, and so on, but that's not revealing anything to me. !errlog says the error log is empty. !locks lists several resources, several of which have several threads waiting, and then says "13898 total locks, 10 locks currently held". Trying the "dt" command on any resource seems to just yield "Symbol not found at address" messages. I do have the symbol server configured, and files are appearing in C:\SYMBOLS\SYMSRV\, and stack traces show symbolic names, so I think symbols are working in the general case. Do I need a full dump to get names for resources? I've turned that option on now, but will have to wait until the next crash. The !thread command on any thread listed by !locks appears to work -- I get a stack trace and such -- but don't know what to look for. I extracted all the stack traces if that helps: http://pastebin.com/hKLxhZ1g I note that "rdbss" shows up in all of them. I gather that's the network file caching subsystem. That might corroborate my theory that the hang is related to the Microsoft SMB/CIFS client. But for all I know, that's what a running system normally looks like. Suggestions welcome. RTFM welcome if pointers to applicable M can be provided. -- Ben
