Tracking down orphaned critical sections in ASP.NEThttp://blogs.msdn.com/tom/archive/2008/01/18/tracking-down-orphaned-critical-sections-in-asp-net.aspxRecently we have seen quite a few issues where the problem turned out to be an orphaned critical section.&#160; When you have a dump with this problem you can run the following commands to see this: 0:000&gt; !locks CritSec +2b1bbac at 02b1bbac WaiterWokenen-USCommunityServer 2.1 SP1 (Build: 61025.2)Interesting Finds: January 19, 2008http://blogs.msdn.com/tom/archive/2008/01/18/tracking-down-orphaned-critical-sections-in-asp-net.aspx#7162601Sat, 19 Jan 2008 19:59:28 GMT91d46819-8472-40ad-a661-2c78acb4018c:7162601Jason HaleyInteresting Finds: 2008.01.20http://blogs.msdn.com/tom/archive/2008/01/18/tracking-down-orphaned-critical-sections-in-asp-net.aspx#8015376Tue, 04 Mar 2008 04:47:40 GMT91d46819-8472-40ad-a661-2c78acb4018c:8015376gOODiDEA<p>.NET: AnImplementationofSystemMonitor</p> <p>FxCop:WritingYourOwnCustomRules</p> <p>WCFWebProgra...</p>