Page File too low to generate crash dump?

Hey everyone, I have interesting issue here that I'm hoping you can help with.  I currently have a server running WS 2008 R2 SP1 with 130 GB of memory installed.  I have the crash settings configured to capture a kernel dump followed by a reboot.  Recently, the server crashed and no dump was generated, I can see in the event logs when the crash occurred but there is no reference to the dump / why it may not have generated.

The ONLY thing I can think of here is that the PF may not be large enough to accommodate the dump, as it is currently set to ~8 GB.  However, I could see that being more of an issue if it were set to get a full dump instead of a kernel.  

Any thoughts on this and whether it might be the issue?  Alternatively, is there anything I can check (without having to crash the server) to see that things are configured correctly under the covers?

Thanks in advance
blinkme323Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Michael DyerSenior Systems Support AnalystCommented:
Microsoft does provide instructions on forcing a memory dump for testing at this page:  http://support.microsoft.com/default.aspx?scid=kb;EN-US;244139

you might want to try this after hours just to confirm your settings are correct.
0
marsiliesCommented:
For a full dump you'd need at least 130GB + 128MB sized page file.

For a kernel dump, the required page file size is a bit trickier.

From:
http://blogs.technet.com/b/askperf/archive/2008/01/08/understanding-crash-dump-files.aspx
Remember that the size of the kernel memory dumps will vary depending on the amount of kernel-mode memory allocated and the drivers loaded.  On systems with more RAM, it is reasonable to expect that the dump file will be larger.  There is no way to predict the exact size of a kernel memory dump.  When you configure kernel memory dumps the system checks to see if the page file is large enough.  There are some guidelines for the minimum page file size needed for kernel memory dumps, however given that the size of kernel mode memory will vary, there is no accurate measure for the maximum.

If the server is 32-bit, the kernel dump can't exceed 2GB. However, a 64-bit server could have a kernel dump that's the full size of the RAM. From:
http://support.microsoft.com/kb/889654
Therefore, a Windows Server 2003 x64 SP1-based server in 64-bit mode with 32GB of RAM could have a 32 GB kernel memory dump file, where you would expect only a 1 to 2 GB dump file in 32-bit mode. This behavior occurs because of the greatly increased memory pools.

This link mentions making the page file RAM size + 257MB for header info. It also suggests the alternative of creating a dedicated dump file, which is a feature Windows Server 2008 R2 has:
http://support.microsoft.com/kb/2860880
A dedicated dump file is a page file that is not used for paging. Instead, it is “dedicated” to back a system crash dump file (memory.dmp) when a system crash occurs. Dedicated dump files can be put on any disk volume that can support a page file. We recommend that you use a dedicated dump file when you want a system crash dump but you do not want a page file.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
blinkme323Author Commented:
Thank you both for the follow up.  So I guess in short, the size of the kernel dump is wholly dependent on the amount of resident kernel memory at that time?  If so, would anything have hit the logs indicating that the dump could not be written?
0
marsiliesCommented:
http://support.microsoft.com/kb/949052
Kernel memory dump files may not be generated on Windows Server 2008-based or Windows Vista Service Pack 1 (SP1)-based computers.

You may also notice the following event is logged in the System event log:
Event ID: 49
Event Type: Error
Event Source: volmgr
Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

Cause:
This behavior occurs when more physical memory (RAM) is installed than the initial size that is set for the page file. If a STOP error occurs when the system is configured to generate a kernel or complete memory dump, no memory dump file will be generated

I think this error may show up at boot.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.