Step 1: Check the Page File Settings
When a blue screen crash occurs, it will write the contents of system memory to the page file. The page file needs to be bigger than the amount of available memory.
- In Windows, navigate to Start > Control Panel > System > Advanced system settings. The System Properties window appears
- In the Advanced tab, under Performance, click Settings
- Click the Advanced tab
- Under Virtual Memory, click Change
- Ensure that the page file on the boot drive is large enough to store the entire contents of the computer's memory, plus one megabyte. For example, if the computer has 1 gigabyte of memory (1024 megabytes), the "Initial size" field should be at least 1025 (memory size plus 1 MB). Adjust the page file size if necessary
- Click Set
- Click OK
- Dismiss any "reboot required" dialog boxes; you will restart later
- Click OK
- Leave the System Properties window open and proceed to the next section
Step 2: Enable Complete Memory Dumps
Memory dumps represent the entire contents of all system memory written to disk. The standard rule of thumb to ensure that there is enough free disk space to capture a full memory dump is:
Free Disk Space = All of Physical Memory + 1 MB
If the computer itselt cannot provide enough free disk space, you can attach an NTFS formatted USB drive that has enough free disk space
To enable complete memory dumps:
- Open Control Panel and navigate to System and Security > System > Advanced System Settings
- Alternatively: Run > SystemPropertiesAdvanced
- Under Startup and Recovery, click Settings.
- From the Write debugging information drop-down menu, select Complete memory dump
- Check Overwrite any existing file
- Click OK
- A message about pagefile requirements may appear; if it does, click Yes
- Click OK
Note: If the Complete memory dump option is missing from the drop-down menu, you can enable it through the registry instead. See How to generate a kernel or a complete memory dump file in Windows Server on Microsoft.com for more information.
Optional: Force a Crash
You may need to initiate the memory dump as an administrator if the issue under investigation does not cause the system to crash. There are three commonly accepted methodologies for causing a computer to generate a memory dump:
- Keyboard initiated dump
- This Windows feature lets you generate a memory dump file by using the keyboard.
- Usage:
- NotmyFault
- Sysinternal Crash on Demand Utility
- Usage:
- NotMyFault64.exe /crash then press enter. For x86 systems, use NotMyFault.exe
- See NotMyFault
- BANG!
- Crash on Demand Utility
- Usage:
bang [-s] : where -s indicates to automatically crash the system
Step 3: Collecting the .DMP
- If applicable, write down the Stop Code displayed on-screen.
- Legacy Operating Systems:
- Upon restarting, a process called savedump.exe copies the contents from the page file to the MEMORY.DMP file on disk. Do not interrupt the savedump.exe process while it is running; otherwise the MEMORY.DMP file will be truncated and possibly corrupted.
- To confirm that the memory dump process is finished, watch the process in Task Manager until it is completed, to ensure the memory dump is completely written.
- Compress the file:
- The resulting MEMORY.DMP file can be quite large. However most of the contents are zeroed memory, so it should compress to a much smaller size. A one gigabyte memory dump will usually compress down to 100-300 megabytes, which will allow for much easier transfer across the network.
- Some zip compression routines have been known to corrupt the original file if it is over 2GB in size. For original files over 2GB in size, Broadcom recommends RAR compressions.