http://blogs.msdn.com/ntdebugging/archive/2008/05/13/smoking-gun-pool-corruption.aspxHello, my name is Ron Stock and I’m an Escalation Engineer on the Microsoft Platforms Global Escalation Services Team. Today I’m going to talk about pool corruption which manifests itself in various ways. It’s usually hard to track down because the culpriten-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/ntdebugging/archive/2008/05/13/smoking-gun-pool-corruption.aspx#8503678Wed, 14 May 2008 20:16:55 GMT91d46819-8472-40ad-a661-2c78acb4018c:8503678Mike<p>Great Post. Great job explaining the concepts behind the analysis. Thanks.</p>http://blogs.msdn.com/ntdebugging/archive/2008/05/13/smoking-gun-pool-corruption.aspx#8505845Thu, 15 May 2008 04:27:53 GMT91d46819-8472-40ad-a661-2c78acb4018c:8505845nksingh<p>Pretty cool.. I guess you're lucky that the driver was leaving its calling card on the spot where it's corrupting memory. &nbsp;That's pretty rare.</p>http://blogs.msdn.com/ntdebugging/archive/2008/05/13/smoking-gun-pool-corruption.aspx#8518598Mon, 19 May 2008 04:23:05 GMT91d46819-8472-40ad-a661-2c78acb4018c:8518598Ryanman<p>Awesome Blog Post! Keep up the great work!</p>