<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Crash Dump Analysis Patterns (Part 13c)</title>
	<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/</link>
	<description>Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics</description>
	<pubDate>Sat, 16 May 2026 13:25:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-621113</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Fri, 30 Nov 2012 14:18:02 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-621113</guid>
		<description>!poolused 5 produces the same level of detail for paged pool as !poolused 3 for nonpaged pool</description>
		<content:encoded><![CDATA[<p>!poolused 5 produces the same level of detail for paged pool as !poolused 3 for nonpaged pool</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-373244</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Wed, 16 Nov 2011 17:18:50 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-373244</guid>
		<description>False positive excessive nonpaged pool memory usage messages: http://support.microsoft.com/kb/2509968</description>
		<content:encoded><![CDATA[<p>False positive excessive nonpaged pool memory usage messages: <a href="http://support.microsoft.com/kb/2509968" rel="nofollow">http://support.microsoft.com/kb/2509968</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry Vostokov</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-287241</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Mon, 30 May 2011 11:19:40 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-287241</guid>
		<description>To see session pool usage you need to switch to a session process first:

&lt;p align="left"&gt;&lt;code&gt;1: kd&gt; !sprocess 3 
[...]
PROCESS 88b0dd88  SessionId: 3  Cid: 1b90    Peb: 7ffde000  ParentCid: 1b84
    DirBase: 4072d000  ObjectTable: d8651450  HandleCount: 414.
    Image: ApplicationA.exe
[...]&lt;/code&gt;

&lt;p align="left"&gt;&lt;code&gt;1: kd&gt; .process /r /p 88b0dd88
Implicit process is now 88b0dd88
Loading User Symbols&lt;/code&gt;

&lt;p align="left"&gt;&lt;code&gt;1: kd&gt; !poolused 8
   Sorting by Session Tag
[...]&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>To see session pool usage you need to switch to a session process first:</p>
<p align="left"><code>1: kd> !sprocess 3<br />
[...]<br />
PROCESS 88b0dd88  SessionId: 3  Cid: 1b90    Peb: 7ffde000  ParentCid: 1b84<br />
    DirBase: 4072d000  ObjectTable: d8651450  HandleCount: 414.<br />
    Image: ApplicationA.exe<br />
[...]</code></p>
<p align="left"><code>1: kd> .process /r /p 88b0dd88<br />
Implicit process is now 88b0dd88<br />
Loading User Symbols</code></p>
<p align="left"><code>1: kd> !poolused 8<br />
   Sorting by Session Tag<br />
[...]</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Insufficient kernel pool memory, spiking thread and data contents locality: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-184991</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Insufficient kernel pool memory, spiking thread and data contents locality: pattern cooperation</dc:creator>
		<pubDate>Sat, 18 Sep 2010 23:30:04 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-184991</guid>
		<description>[...] Debugging Experts Magazine Online A complete memory dump was generated from a totally unresponsive frozen system. Looking at its virtual memory stats we see the shortage of nonpaged pool (insufficient kernel pool memory pattern): [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Debugging Experts Magazine Online A complete memory dump was generated from a totally unresponsive frozen system. Looking at its virtual memory stats we see the shortage of nonpaged pool (insufficient kernel pool memory pattern): [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Reflecting on 2008 (Part 1)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-159020</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Reflecting on 2008 (Part 1)</dc:creator>
		<pubDate>Thu, 17 Jun 2010 14:11:34 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-159020</guid>
		<description>[...] system_thread_exception_not_handled system_thread_exception_not_handled (7e) windbg command pool allocations have failed receivelotsacalls trap frame vista dr watson bios disassembly ninjutsu uncovered citrix tools at [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] system_thread_exception_not_handled system_thread_exception_not_handled (7e) windbg command pool allocations have failed receivelotsacalls trap frame vista dr watson bios disassembly ninjutsu uncovered citrix tools at [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 24)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-144306</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Icons for Memory Dump Analysis Patterns (Part 24)</dc:creator>
		<pubDate>Wed, 14 Apr 2010 13:39:26 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-144306</guid>
		<description>[...] Today we introduce an icon for Insufficient Memory (kernel pool) pattern: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Today we introduce an icon for Insufficient Memory (kernel pool) pattern: [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Invalid pointer, incorrect stack trace, multiple exceptions, insufficient memory and memory leak: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-78611</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Invalid pointer, incorrect stack trace, multiple exceptions, insufficient memory and memory leak: pattern cooperation</dc:creator>
		<pubDate>Wed, 10 Jun 2009 13:59:42 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-78611</guid>
		<description>[...] suspect that users cannot connect because of the lack of kernel pool resources and see the shortage of paged pool along with session pool shortage for one [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] suspect that users cannot connect because of the lack of kernel pool resources and see the shortage of paged pool along with session pool shortage for one [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Insufficient memory, handle leak, process factory, high contention and busy system: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-65266</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Insufficient memory, handle leak, process factory, high contention and busy system: pattern cooperation</dc:creator>
		<pubDate>Mon, 16 Feb 2009 12:20:44 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-65266</guid>
		<description>[...] dump was generated for analysis. Usual !vm 4 command shows pool allocation errors and particularly insufficient session pool memory for user session [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] dump was generated for analysis. Usual !vm 4 command shows pool allocation errors and particularly insufficient session pool memory for user session [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crash Dump Analysis &#187; Blog Archive &#187; Insufficient memory, handle leak, wait chain, deadlock, inconsistent dump and overaged system: pattern cooperation</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-60341</link>
		<dc:creator>Crash Dump Analysis &#187; Blog Archive &#187; Insufficient memory, handle leak, wait chain, deadlock, inconsistent dump and overaged system: pattern cooperation</dc:creator>
		<pubDate>Wed, 24 Dec 2008 16:00:15 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-60341</guid>
		<description>[...] 2009 (0x7D9) - The Year of DebuggingIn one complete memory dump taken from the system refusing user connections but not hung completely we can see the signs of past pool allocation failures (see Insufficient Memory): [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 2009 (0&#215;7D9) - The Year of DebuggingIn one complete memory dump taken from the system refusing user connections but not hung completely we can see the signs of past pool allocation failures (see Insufficient Memory): [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: !analyze -v : Crash Dump Analysis Patterns (Part 13c)</title>
		<link>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-43201</link>
		<dc:creator>!analyze -v : Crash Dump Analysis Patterns (Part 13c)</dc:creator>
		<pubDate>Thu, 18 Sep 2008 08:37:29 +0000</pubDate>
		<guid>https://www.dumpanalysis.org/blog/index.php/2007/11/02/crash-dump-analysis-patterns-part-13c/#comment-43201</guid>
		<description>[...] Crash Dump Analysis Patterns (Part 13c) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Crash Dump Analysis Patterns (Part 13c) [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
