<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Tracking down MmSt paged pool usage</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/05/08/tracking-down-mmst-paged-pool-usage.aspx</link><description>A trend that I’ve noticed recently are cases involving paged pool depletion with high MmSt tag usage that remains after trying KB304101 (PoolUsageMaximum) . These pool allocations are used by the memory manager for section object prototype PTEs. There</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Tracking down MmSt paged pool usage</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/05/08/tracking-down-mmst-paged-pool-usage.aspx#8500349</link><pubDate>Tue, 13 May 2008 17:07:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8500349</guid><dc:creator>Sushant</dc:creator><description>&lt;p&gt;This is an awesome explanation. &lt;/p&gt;</description></item><item><title>re: Tracking down MmSt paged pool usage</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/05/08/tracking-down-mmst-paged-pool-usage.aspx#8707741</link><pubDate>Tue, 08 Jul 2008 13:32:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8707741</guid><dc:creator>Rehan</dc:creator><description>&lt;p&gt;Hi Bryan, &lt;/p&gt;
&lt;p&gt;A very interesting post to say the least. I'm confused about some of the details however.&lt;/p&gt;
&lt;p&gt;I attempted to follow the above instructions to find the total MmSt size and total PTE's and believe it worked. &lt;/p&gt;
&lt;p&gt;What I don't understand is the size of MmSt reported seems to be abnormally high, &lt;/p&gt;
&lt;p&gt;like in your example.. &lt;/p&gt;
&lt;p&gt;MmSt size &amp;nbsp;: 502321952 bytes&lt;/p&gt;
&lt;p&gt;That's close to 500MB! Which certainly can't correspond to the poolmon paged pool size corresponding to MmSt (unless your on x64 ?). &lt;/p&gt;
&lt;p&gt;Could you please clarify what this size actually corresponds to ? And how we can track the size reported under paged pool in poolmon for the MmSt tag.&lt;/p&gt;</description></item><item><title>re: Tracking down MmSt paged pool usage</title><link>http://blogs.msdn.com/ntdebugging/archive/2008/05/08/tracking-down-mmst-paged-pool-usage.aspx#8935941</link><pubDate>Tue, 09 Sep 2008 09:10:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8935941</guid><dc:creator>Ram Satendra</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The mmst tag is related to the pool paged memory, and PTE is related to nonpaged pool memory, if mmst tag is consuming lot of memory then the paged pool is not recycled, this could be most common in windows 2000, all you have to do is trim the memory by making an entry in the registry you can make it at 60%, so that after reaching the maximum memory the paged pool will be recycled&lt;/p&gt;</description></item></channel></rss>