Memory Dump File Not Being Generated on Provisioned Target

Description

While attempting to configure a Windows 2008 target server created by Citrix Provisioning Services to generate a complete memory dump, it was observed that the memory dump file was not being created properly.

Following CTX123642 – How to Recover Windows Kernel Level Dump Files from Provisioned Target allowed a DedicatedDumpfile.sys file to be generated in the expected location, but conversion to a memory.dmp file was not occurring. An event ID 49 entry was found in the system event log:

Log Name:      System
Source:        volmgr
Date:          12/19/2010 10:24:01 PM
Event ID:      49
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server1
Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

The system drive on the server did not have enough space to allow the memory dump to be generated, so the server was configured per CTX123642 – How to Recover Windows Kernel Level Dump Files from Provisioned Target to place the dedicateddumpfile.sys file and memory.dmp file on the local D:\ drive which had enough space.

To verify the dump file settings, you can examine the following registry values under HKLM\SYSTEM\CurrentControlSet\Control\CrashControl:
DumpFile
DedicatedDumpFile

Note: In a Provisioning Services environment, the memory dump file and dedicateddumpfile.sys file must be located on a local storage device.

For example, if the DedicatedDumpFile value is E:\dedicateddumpfile.sys, then you must have the DumpFile value set for the E:\ drive as well (such as E:\memory.dmp).

The server had 24 gigabytes of memory and there was not enough disk space on the system drive to create a complete memory dump there, so the system was configured to place the dump file on the local D: drive of the server.

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Resolution

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

Complete the following steps to resolve the issue:

Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:
HKLM\SYSTEM\CurrentControlSet\Control\CrashControl
On the Edit menu, point to New, and then click DWORD Value.
Type IgnorePagefileSize, and then press Enter.
Right-click IgnorePagefileSize, and then click Modify.
In the Value data box, type 1, and then click OK.
Exit Registry Editor and reboot the server.

Then test the change using a manual system dump process such as NotMyFault or SystemDump (see Additional Resources section for download links) to verify that a proper memory.dmp file is created.