<?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>Save Support Dollars by Checking Your Memory Dump before Calling Support</title><link>http://blogs.msdn.com/b/ntdebugging/archive/2009/06/12/save-support-dollars-by-checking-your-memory-dump-before-calling-support.aspx</link><description>Hello, I am East with a quick review of what to do with your memory dumps before opening a support case. It's not uncommon for an entity to open a Microsoft support case with the intent of having a dump file examined by the escalation team. In some cases</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Save Support Dollars by Checking Your Memory Dump before Calling Support</title><link>http://blogs.msdn.com/b/ntdebugging/archive/2009/06/12/save-support-dollars-by-checking-your-memory-dump-before-calling-support.aspx#9817347</link><pubDate>Sat, 04 Jul 2009 09:59:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9817347</guid><dc:creator>refactorme</dc:creator><description>&lt;p&gt;That was really great info..!!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9817347" width="1" height="1"&gt;</description></item><item><title>re: Save Support Dollars by Checking Your Memory Dump before Calling Support</title><link>http://blogs.msdn.com/b/ntdebugging/archive/2009/06/12/save-support-dollars-by-checking-your-memory-dump-before-calling-support.aspx#9802364</link><pubDate>Thu, 25 Jun 2009 01:50:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9802364</guid><dc:creator>taehwa lee</dc:creator><description>&lt;P&gt;It is great article. Thank you.&lt;/P&gt;
&lt;P&gt;I have a question as blow.&lt;/P&gt;
&lt;P&gt;Sometimes kernel dump file is corrupted with blow setting.&lt;/P&gt;
&lt;P&gt;More than 4GB RAM such as 8GB, 16GB, 32GB.&lt;/P&gt;
&lt;P&gt;Dump type : Kernel dump&lt;/P&gt;
&lt;P&gt;Page file size : 2048&lt;/P&gt;
&lt;P&gt;CPU : x86&lt;/P&gt;
&lt;P&gt;A lot of people said that 2GB page files size was enough to made a kernel dump in x86 system due to kernel memory couldn’t larger than 2GB in x86, 32Bit, system.&lt;/P&gt;
&lt;P&gt;But I saw that corrupted kernel dump in above environment.&lt;/P&gt;
&lt;P&gt;What size is best in x86 system which has large memory?&lt;/P&gt;
&lt;DIV class=commentowner&gt;[Keeping it to the default is my recommendation 2048+1mb. You may be getting a corrupt dump because of something else.]&lt;/DIV&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9802364" width="1" height="1"&gt;</description></item><item><title> Ntdebugging Blog Save Support Dollars by Checking Your Memory Dump | debt settlement program</title><link>http://blogs.msdn.com/b/ntdebugging/archive/2009/06/12/save-support-dollars-by-checking-your-memory-dump-before-calling-support.aspx#9753898</link><pubDate>Mon, 15 Jun 2009 20:03:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9753898</guid><dc:creator> Ntdebugging Blog Save Support Dollars by Checking Your Memory Dump | debt settlement program</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://edebtsettlementprogram.info/story.php?id=23060"&gt;http://edebtsettlementprogram.info/story.php?id=23060&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9753898" width="1" height="1"&gt;</description></item></channel></rss>