Title: - Points to remember while collecting memory dump.
Symptoms: -
Ø No dump file
Ø Corrupt dump file
Cause: -
Ø No Paging file
Ø Paging file on a different drive
Ø Page file size not appropriate
Ø No space on the C drive
Ø ASR Software
Ø Old SCSI drivers
Solution: -
Ø Set the path of the dump to C drive
Ø Page file should exist. In case it doesn’t then the dump will not be generated.
Ø The size of the page file should be more than the physical RAM.
Ø The recommended size is 1.5 times more than the physical RAM
Ø Enough space for the dump file on the C drive
Ø A complete memory dump is almost equal to the size of the physical RAM
Ø ASR (Automatic Server Recovery) software can cause an issue when we try to get a dump file
Ø They should be turned OFF in scenario’s where we face an issue collecting the dump
Ø Old SCSI drivers are also responsible for the non creation of dump
Ø Microsoft has a tool namely Dumpchk.exe which checks whether the dump is GOOD.
Ø Dumpchk.exe is a command-line utility you can use to verify that a memory dump file has been created correctly.
Ø Dumpchk.exe does not require access to symbols.
Ø You can download debugging tools for Windows products from the following Microsoft Web site:
http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx (http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx)