<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Memory dump files vs Paging in Windows Server 2003</title>
    <link>https://community.hpe.com/t5/windows-server-2003/memory-dump-files-vs-paging/m-p/4448348#M5652</link>
    <description>One more thing... if the server is 32-bit you cannot use the complete memory dump. This is not supported for 32-bit systems with more than 2GB RAM.</description>
    <pubDate>Thu, 02 Jul 2009 17:16:28 GMT</pubDate>
    <dc:creator>WFHC-WI</dc:creator>
    <dc:date>2009-07-02T17:16:28Z</dc:date>
    <item>
      <title>Memory dump files vs Paging</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-dump-files-vs-paging/m-p/4448345#M5649</link>
      <description>I have my Paging file split on C and E drive.&lt;BR /&gt;Will this be a reason for not generating a memory dump file.&lt;BR /&gt;&lt;BR /&gt;Paging on C drive 4GB&lt;BR /&gt;Paging on E drive 4GB&lt;BR /&gt;RAM is 7.75 GB&lt;BR /&gt;&lt;BR /&gt;C drive: 30GB and presently has 17.5GB free space&lt;BR /&gt;E drive : 20GB and 7GB is free&lt;BR /&gt;&lt;BR /&gt;1. I want to make ensure memory dump is created whenever the system does bug check.&lt;BR /&gt;2. If I split paging file on C and E drive in the above case, will the memory dump file be created.&lt;BR /&gt;3. What is the best solution to ensure memory dump is created and I resolve the issue of low paging&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 27 Jun 2009 05:23:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-dump-files-vs-paging/m-p/4448345#M5649</guid>
      <dc:creator>Mandar Patil</dc:creator>
      <dc:date>2009-06-27T05:23:20Z</dc:date>
    </item>
    <item>
      <title>Re: Memory dump files vs Paging</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-dump-files-vs-paging/m-p/4448346#M5650</link>
      <description>In most cases you don't need complete memory dump.&lt;BR /&gt;You can choose "Kernel memory dump" or even&lt;BR /&gt;"Small memory dump" options (we use "small memory dump" option on our servers)&lt;BR /&gt;With Kernel or small memory dump you can split page files between drives and have only small page file on drive C&lt;BR /&gt;For example, on server with 32 GB RAM you can define page file with 1 GB size&lt;BR /&gt;&lt;BR /&gt;Overview of memory dump file options for Windows Vista, Windows Server 2008, Windows Server 2003, Windows XP, and Windows 2000&lt;BR /&gt;&lt;A href="http://support.microsoft.com/kb/254649" target="_blank"&gt;http://support.microsoft.com/kb/254649&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Understanding Crash Dump Files &lt;BR /&gt;&lt;A href="http://blogs.technet.com/askperf/archive/2008/01/08/understanding-crash-dump-files.aspx" target="_blank"&gt;http://blogs.technet.com/askperf/archive/2008/01/08/understanding-crash-dump-files.aspx&lt;/A&gt;</description>
      <pubDate>Sat, 27 Jun 2009 07:57:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-dump-files-vs-paging/m-p/4448346#M5650</guid>
      <dc:creator>Igor Karasik</dc:creator>
      <dc:date>2009-06-27T07:57:43Z</dc:date>
    </item>
    <item>
      <title>Re: Memory dump files vs Paging</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-dump-files-vs-paging/m-p/4448347#M5651</link>
      <description>Hi Mandar,&lt;BR /&gt;&lt;BR /&gt;It has been some time since I last reported on page file best practices but here is what I remember.&lt;BR /&gt;&lt;BR /&gt;If you have mulitple page files you will not be able to generate a complete memory dump. There is a 4096MB limit on page file sizes but this can be addressed by either using page files on multiple drives (as you have) or by editing the PagingFiles value in the registry key HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management&lt;BR /&gt;&lt;BR /&gt;This value is a MULTI_SZ so you can enter multiple lines into it in this fashion:&lt;BR /&gt;&lt;FULL path="" to="" pagefile="" 1=""&gt; &lt;INITIAL size=""&gt; &lt;MAXIMUM size=""&gt;&lt;BR /&gt;&lt;FULL path="" to="" pagefile="" 2=""&gt; &lt;INITIAL size=""&gt; &lt;MAXIMUM size=""&gt;&lt;BR /&gt;etc.&lt;BR /&gt;&lt;BR /&gt;In my opinion I am surprised that the systm would require a paging file that large with 8GB RAM. You should test performance with a single 4GB pagefile to ensure your complete memory dump will be available.&lt;BR /&gt;&lt;BR /&gt;Good luck!&lt;/MAXIMUM&gt;&lt;/INITIAL&gt;&lt;/FULL&gt;&lt;/MAXIMUM&gt;&lt;/INITIAL&gt;&lt;/FULL&gt;</description>
      <pubDate>Thu, 02 Jul 2009 17:14:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-dump-files-vs-paging/m-p/4448347#M5651</guid>
      <dc:creator>WFHC-WI</dc:creator>
      <dc:date>2009-07-02T17:14:33Z</dc:date>
    </item>
    <item>
      <title>Re: Memory dump files vs Paging</title>
      <link>https://community.hpe.com/t5/windows-server-2003/memory-dump-files-vs-paging/m-p/4448348#M5652</link>
      <description>One more thing... if the server is 32-bit you cannot use the complete memory dump. This is not supported for 32-bit systems with more than 2GB RAM.</description>
      <pubDate>Thu, 02 Jul 2009 17:16:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/memory-dump-files-vs-paging/m-p/4448348#M5652</guid>
      <dc:creator>WFHC-WI</dc:creator>
      <dc:date>2009-07-02T17:16:28Z</dc:date>
    </item>
  </channel>
</rss>

