http://blogs.msdn.com/b/ntdebugging/archive/2010/04/02/how-to-use-the-dedicateddumpfile-registry-value-to-overcome-space-limitations-on-the-system-drive-when-capturing-a-system-memory-dump.aspx
Page file configuration are not so necessary and with the disk space issues foreseen on these servers.
Memory Dump = Pagefile = Size of RAM + free disk space equal to the size of the RAM present on the disk
or
Memory Dump = Dedicated Crash Dump file .
This would be good idea for troubleshooting the systems which has the very large RAM .
By Default the Crash dump always write the files to %systemroot% memory.dmp if you have choosen an alternative location this will be writing to that file after the server reboots.
So you should also consider the free space on that destination drive..
Page file configuration are not so necessary and with the disk space issues foreseen on these servers.
Memory Dump = Pagefile = Size of RAM + free disk space equal to the size of the RAM present on the disk
or
Memory Dump = Dedicated Crash Dump file .
This would be good idea for troubleshooting the systems which has the very large RAM .
By Default the Crash dump always write the files to %systemroot% memory.dmp if you have choosen an alternative location this will be writing to that file after the server reboots.
So you should also consider the free space on that destination drive..
