More dump forensics, understanding !locks, in this case a filter driver problemhttp://blogs.msdn.com/ntdebugging/archive/2008/04/17/more-dump-forensics-understanding-locks-in-this-case-a-filter-driver-problem.aspxWritten by Jeff Dailey: Hello NTDebuggers, one of the most important things to understand in kernel debugging hung servers is the output of !locks. There can be a lot of data and it’s not always clear what is going on. One of the things I like to do inen-USCommunityServer 2.1 SP1 (Build: 61025.2)Microsoft news and tips &raquo; More dump forensics, understanding !locks, in this case a filter driver problemhttp://blogs.msdn.com/ntdebugging/archive/2008/04/17/more-dump-forensics-understanding-locks-in-this-case-a-filter-driver-problem.aspx#8404636Thu, 17 Apr 2008 23:55:55 GMT91d46819-8472-40ad-a661-2c78acb4018c:8404636Microsoft news and tips &raquo; More dump forensics, understanding !locks, in this case a filter driver problem<p>PingBack from <a rel="nofollow" target="_new" href="http://microsoftnews.askpcdoc.com/?p=3106">http://microsoftnews.askpcdoc.com/?p=3106</a></p> re: More dump forensics, understanding !locks, in this case a filter driver problemhttp://blogs.msdn.com/ntdebugging/archive/2008/04/17/more-dump-forensics-understanding-locks-in-this-case-a-filter-driver-problem.aspx#8407626Fri, 18 Apr 2008 14:37:57 GMT91d46819-8472-40ad-a661-2c78acb4018c:8407626Jeroen Mostert<p>Is this particular scenario (mass blocking on a bogus lock) the sort of thing &quot;!analyze -hang&quot; would find out for you without manual decoding? (Not that it's not useful to understand &quot;!locks&quot;, mind you.)</p>