Dump Check [Dumpchk.exe] is a command line utility which can be used to verify if the memory.dmp file has been created correctly. Best part you doesn’t need symbols to verify it. If you are analyzing the dump file , its good to ignore this post as this post is dedicated to those people who will send their dump file for analysis.
Some time we get request from tech to re-send the data as it was corrupt. We are not aware whether the data got corrupt over the wire or we have corrupt dump file. Although in most cases we can still get few information from the dump file however we can’t say how reliable it is.
In order to avoid such circumstance, its always better to check if our memory dump file is clean and have no corruption.
I would suggest you to Download and install SDK, yes it’s a little bit time consuming process however trust me you will not get just dumpchk command line tool , but even more than that which we will be discussing later.
Once downloaded and installed , one command prompt with administrative rights and run the command
dumpchk -q [Dump File Location]
You may use below options in place of -q as well :
-? Displays the command syntex
-p Prints the header without validation
-v Specifies the verbose mode.
-q performs a quick test.
If there is an error during any portion of the output displayed above, the dump file is corrupted and analysis cannot be performed.
In my carrier of troubleshooting most of the time for corrupt memory dump, culprit was pagefile. A very simple steps for cleaning the pagefile at shutdown fixes the issue
Steps to Clean the Pagefile at shutdown :
Step 1 : Open regedit with administrative previlage.
Step 2 : Go to the location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management in registry editor.
Step 3 : Change the data value of the ClearPageFileAtShutdown value in the following registry key to a value of 1.
STEP 4 : If the value does not exist, add the following value: Value Name: ClearPageFileAtShutdown Value Type: REG_DWORD Value: 1
STEP 5 : Reboot the machine.
STEP 6 : After reboot , change the value back to 0 .
Step 7 : Reboot the machine. Now you are good to go.