Sometimes during troubleshooting of blue-screen failures, it is necessary to make sure that a complete memory dump is generated on the machine having problems. This document discusses the settings required to make sure this goal is fulfilled.
This article contains information about modifying the registry.
Before you modify the registry, make sure to create a back up of the registry and ensure that you understand how to restore the registry if a problem may occur.
For more information about how to back up, restore, and edit the registry, please review the relevant Microsoft Knowledge Base articles on support.microsoft.com
- In Control Panel, double click the System Applet
- Select the Advanced tab and Click the 'Startup and Recovery' button
- Under the 'Write Debugging Information' section select: 'Complete MemoryDump' from the pulldown menu
- Make sure a check mark is placed on: 'Overwrite any existing file'
- Make sure that there is a paging file (pagefile.sys) on the System
Drive (C:\) and that it is at least RAM + (.5 xRAM).
- Also make sure there is more space on the hard drive than there is physical RAM
- Automatic Restart should be disabled.
- Open Regedit and navigate to
Double-click on 'CrashDumpEnabled' and change value to '1' then click
If the physical memory is more than 2GB then please go by the following action plan to dump 2GB physical memory
- Click on Start --- Run and type in msconfig.exe
- Click on BOOT.INI tab
- Click on Advanced options and check /Maxmem give it a value 2000
- Restart the server
You may want to check that the memory dump generated is valid for analysis by reading it using Microsoft's debugging tools for Windows, which are available from the following link:
After installing the tools, click on File and then Open crash dump, navigate to the directory where your memory dump file is created and load it. It should complain about missing symbol files, but not report that the dump file is corrupted or incomplete.