Export (0) Print
Expand All
3 out of 3 rated this helpful - Rate this topic

Configure memory dump files for Server Core installation options of Windows Server 2008

Updated: July 20, 2009

Applies To: Windows Server 2008, Windows Server 2008 R2

This article describes how to configure memory dump files for a Server Core installation of the Windows Server® 2008 operating system. A Server Core installation of Windows Server 2008 provides console-based alternatives to the Control Panel for configuring system failure and recovery options.

This process requires the following steps:

This step enables you to manually configure your system failure and recovery options. This is required to complete the remaining steps.

At the command prompt, run the following command to disable automatic system page file management:

wmic computersystem set AutomaticManagedPagefile=False

Windows Server 2008 does not require the page file to exist on the partition that the operating system is installed on. To put the page file on another partition, you must create a new registry entry named DedicatedDumpFile. You can define the size of the paging file by using the DumpFileSize registry entry. To create the DedicatedDumpFile and DumpFileSize registry entries, follow these steps:

  1. At the command prompt, run the Regedit command. This opens the Registry Editor.

  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

  3. On the Edit menu, point to New, and then click String Value.

  4. Name the new value DedicatedDumpFile, and then press ENTER.

  5. Right-click DedicatedDumpFile, and then click Modify.

  6. In the Value data text box, type <Drive>:\<Dedicateddumpfile.dmp>, and then click OK.

    noteNote
    Replace <Drive> with a drive that has enough disk space for the paging file, and replace <Dedicateddumpfile.dmp> with the full path to the dedicated file.

  7. On the Edit menu, point to New, and then click DWORD Value.

  8. Type DumpFileSize, and then press ENTER.

  9. Right-click DumpFileSize, and then click Modify.

  10. In the Edit DWORD Value dialog box, under Base, click Decimal.

  11. In the Value data text box, type the appropriate value, and then click OK.

    noteNote
    The size of the dump file is in megabytes (MB).

  12. Exit the Registry Editor.

After you determine the partition location of the memory dump, configure the destination path for the page file. To view the current destination path for the page file, run the following command:

wmic RECOVEROS get DebugFilePath

The default destination for DebugFilePath is %systemroot%\memory.dmp. To change the current destination path, run the following command:

wmic RECOVEROS set DebugFilePath = <FilePath>

Set <FilePath> to the destination path. For example, the following command sets the memory dump destination path to C:\WINDOWS\MEMORY.DMP:

wmic RECOVEROS set DebugFilePath = C:\WINDOWS\MEMORY.DMP

Determine the type of memory dump to configure for your server. To view the current memory dump type, run the following command:

wmic RECOVEROS get DebugInfoType

To change the current memory dump type, run the following command:

wmic RECOVEROS set DebugInfoType = <Value>

<Value> can be 0, 1, 2, or 3, as defined below.

  • 0: Disable the removal of a memory dump.

  • 1: Full memory dump. Records all of the contents of system memory when your computer stops unexpectedly. A full memory dump may contain data from processes that were running when the memory dump was collected.

  • 2: Kernel memory dump (default). Records only the kernel memory. This speeds up the process of recording information in a log file when your computer stops unexpectedly.

  • 3: Small memory dump. Records the smallest set of useful information that may help identify why your computer stopped unexpectedly.

For more information on memory dump types, see article 254649 in the Microsoft® Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=156021).

By default, the server automatically restarts after it generates a memory dump. To view the current configuration, run the following command:

wmic RECOVEROS get AutoReboot

If the value for AutoReboot is TRUE, the server will restart automatically after generating a memory dump. No configuration is needed and you can proceed to the next step.

If the value for AutoReboot is FALSE, the server will not restart automatically after generating a memory dump. Configure the server to restart automatically by running the following command:

wmic RECOVEROS set AutoReboot = true

By default, the server overwrites the existing memory dump file when a new one is created. To determine if existing memory dump files are already configured to be overwritten, run the following command:

wmic RECOVEROS get OverwriteExistingDebugFile

If the value for OverwriteExistingDebugFile is 1, the server will overwrite the existing memory dump file. No configuration is needed, and you can proceed to the next step.

If the value for OverwriteExistingDebugFile is 0, the server will not overwrite the existing memory dump file. Configure the server to overwrite the file by running the following command:

wmic RECOVEROS set OverwriteExistingDebugFile = 1

Determine whether an administrative alert is appropriate and set SendAdminAlert accordingly. To view the current value for SendAdminAlert, run the following command:

wmic RECOVEROS get SendAdminAlert

The possible values for SendAdminAlert are:

  • TRUE: Send an administrative alert (default)

  • FALSE: Do not send an administrative alert

To modify the existing SendAdminAlert value to true, run the following command:

wmic RECOVEROS set SendAdminAlert = true

This procedure describes how to set the memory dump’s page file size.

  1. To check current page file settings, run one of the following commands:

    wmic.exe pagefile
    

    or

    wmic.exe pagefile list /format:list
    
  2. The following example demonstrates how to configure the initial and maximum sizes of your page file:

    wmic pagefileset where name="c:\\pagefile.sys" set InitialSize=1000MB,MaximumSize=5000MB
    

    For more information on determining the proper page file size for your server, see article 889654 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=156022).

A Server Core installation of Windows Server 2008 allows you to manually generate a memory dump by using a PS/2 keyboard. This feature is disabled by default, and it is not available for Universal Serial Bus (USB) keyboards.

To enable manual memory dumps by using a PS/2 keyboard, run the following command:

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /v CrashOnCtrlScroll /t REG_DWORD /d 1 /f

To determine if the feature has been enabled properly, run the following command:

Reg query HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ i8042prt \ Parameters / v CrashOnCtrlScroll

You must restart the server for the changes to take effect. You can restart the server by running the following command:

Shutdown / r / t 0

You can generate a manual memory dumps with a PS/2 keyboard that is connected to your server by holding the RIGHT CTRL key while you press the SCROLL LOCK key two times. This will make the computer bug check with error code 0xE2. After you restart the server, a new dump file appears in the destination path that you established in Step 2: Configure the destination path for a memory dump. For more information on generating a memory dump with a PS/2 keyboard, see article 244139 in the Microsoft Knowledge Base (http://go.microsoft/com/fwlink/?LinkId=156023).

To verify that the memory dump files are being created correctly, you can use the dumpchk.exe utility. To use dumpchk.exe, you need access to a computer that is running Windows Server 2003, Windows XP, Windows 2000, Windows NT 4.0, Windows Vista, or an installation of Windows Server 2008 that is not Server Core. Additionally, the debugging tools for Windows products must be installed. You can download the dumpchk.exe utility along with the other debugging tools from Debugging Tools for Windows on the Windows Hardware Developer Central (WHDC) home page (http://go.microsoft.com/fwlink/?LinkId=156024).

The dumpchk.exe utility allows you to transfer the memory dump file from your Server Core installation of Windows Server 2008 to the other computer by using the medium of your choice.

CautionCaution
Page files can be very large, so careful consideration of the transfer method and of the resources that method requires is advised.

For more information about using dumpchk.exe to check a memory file, see article 156280 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=156026).

  • Kernel memory dump files may not be generated on Windows Server 2008-based and Windows Vista SP1-based computers when system memory is larger than the size of the page file. For more information see article 949052 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=156027).

  • Dedicated dump files may be truncated to 4 GB on a computer that is running Windows Server 2008 or Windows Vista and that has more than 4 GB of physical memory. For more information see article 950858 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=156029).

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.