0

Last night we had a critical server go down. Running Windows 2012R2. It appears to have been a random blue screen but we can't find much in the logs. We do not seem to have a dump file. Investigating, I found this:

"To take advantage of the dump file feature, your paging file must be on the boot volume. If you have moved the paging file to another volume, you must move it back to the boot volume before you use this feature." https://docs.microsoft.com/en-us/windows/client-management/system-failure-recovery-options

Our paging file is on it's own drive. I had always thought this was best practice. This server has 320GB RAM. The paging drive is 640GB. The page file is set to "system managed size" on this drive.

current page settings

If I also set C: to "system managed size" will that get me a dump file if this happens again? What is the best practice in a scenario like this?

Luke Johnson
  • 1

1 Answers1

0

Anything other than a small memory dump isn't likely to be any more useful, and is likely to be cumbersome (at best) to analyze.

Leave your existing pagefile settings as is and create a small pagefile on the boot volume and set the memory dump setting to small memory dump.

https://docs.microsoft.com/en-us/troubleshoot/windows-server/performance/memory-dump-file-options

If a dump occurs, you can use WinDbg to analyze the dump file.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools

joeqwerty
  • 109,901
  • 6
  • 81
  • 172