Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 223
  • Last Modified:

Server failing to create memory dump memory.dmp after a blue screen BSOD

Hi,

Strange one here:

We have a server that blue screens every now and again, and we have been trying to work out why by looking through the memory dumps. Recently however the server has crashed twice and not created or replaced the dump file.

Nothing has changed in that the pagefile has not been moved, and the server is not losing power and rebooting because of that. We are presuming it is bluescreening and rebooting as it has been doing in the past.

Anybody any ideas?

I cannot stop it performing the autoreboot so I can definately confirm it is blue screening, as getting the server back up and running is more important as this is a 24/7 manufacturing site and the crash is more likely to occur when I am out of the office than in.

The existing memory.dmp file that was there from the last creation did not appear to be corrupt and I even deleted it prior to the last crash in case it was a problem with overwriting it.

500 pts as it has me stumped, and that's not a good thing to tell the application owner..

Cheers

Matt

0
matthewcapstick
Asked:
matthewcapstick
  • 3
  • 2
  • 2
  • +2
1 Solution
 
jkrCommented:
Check your registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl - is 'CrashDumpEnabled' set to '1' and 'Overwrite' also?
0
 
rindiCommented:
Also make sure there is enough space on the partition for the dump. If your making a full dump (and not the minidump, although that should normally be enough) you will need at least the same amount of free space as your RAM size. I'm not sure, but the drive may also have to be defragged.
0
 
ShanidarCommented:
If I remember correctly, you have to have a swap file on the boot/system partition, for the dump to be created.  Even if it is only the minimum size 2Mb swapfile.  Did that setting get changed after your last successful dump?

Check it out.

Good Luck

0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
matthewcapstickAuthor Commented:
Thanks to both of you.

Have checked everything and all is OK. The registry settings are OK and the disk space available is plenty. The settings for the pagefile are OK too and not been changed.

We had a crash last night at 2am too and the same has happened. No memory.dmp :(
0
 
rindiCommented:
Have you checked the startup and recovery of your system properties, maybe the folder which is set in there to take your memory.dmp doesn't exist?
0
 
matthewcapstickAuthor Commented:
Thanks again.

Yes that is all OK and exists. The strange thing is that it was all working OK but suddenly stopped working.

Thanks
0
 
dcliveCommented:
Can you confirm your VM swapfile is, say, 800MB or so or highter, confirm it IS on drive C: (same volume as your OS), and the dump style is set to kernel memory dump?  

What's the error in the eventlog?

0
 
matthewcapstickAuthor Commented:
Yes all that is correct.

Saldy there is no event log error. Just the usual message to say the system has restarted. Have checked to ensure there are no power failures. The power feeds to the server are from different supplies and neither show any failures.
0
 
ShanidarCommented:
You say it all stopped working suddenly.
What took place aorund that time?
Do you have automatic updates turned on?  Was some "patch" installed in preceding weeks?  How common are your crashes?  You might take a look at what updates were supplied between you last successful dump, and the first crash w/o a dump.

You might even run a search and specify dates of changed files, to find out what all got changed.

0
 
dcliveCommented:
http://www.winguides.com/registry/display.php/856/

Use that to enable C-SL-SL forcing a dump, then reboot, then try to force the dump....can you generate a memory dump?

In any event, if no log entries say that a bluescreen took place, it's most likely you have a hardware problem, so I'd suggest running hardware diagnostics.  Windows will bluescreen the box (and write to the eventlog) if it has control if the hardware.  If it doesn't, nothing happens, nothing gets written - the box just reboots.

0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now