Understanding Crash Dump Files

Microsoft Product's — Wed, 09 Jan 2008 19:32:52 GMT

At the end of 2007 we talked about Bugchecks and why they happen . Today we're going to talk about

re: Understanding Crash Dump Files

Norman — Thu, 17 Jan 2008 01:40:10 GMT

Thanks for this insightful post. I was wondering if you know whether the 2GB limit for complete memory dump applies to Vista and Server 2008?

re: Understanding Crash Dump Files

Shawn — Fri, 15 Feb 2008 01:58:02 GMT

Norman: I'm unsure about Vista, but Server 2008 runs strictly on 64-bit hardware. This would remove the 2GB limit imposed by its 32-bit predecessor.

As I understand it, this is a hardware limitation, and would likely extend to a 32-bit version of Vista.

re: Understanding Crash Dump Files

CC Hameed — Fri, 15 Feb 2008 15:14:26 GMT

Shawn: Windows Server 2008 is available in both 32-bit and 64-bit flavors (see http://www.microsoft.com/windowsserver2008/en/us/system-requirements.aspx for the system requirements page which does list a 32-bit OS version)

Norman: the Complete Memory Dump option is not available via the GUI if there is more than 2GB of RAM visible to the system. This is true for both x86 and x64 versions of the OS - see http://support.microsoft.com/kb/274598 for additional details.

re: Understanding Crash Dump Files

Marcus — Thu, 20 Nov 2008 20:02:29 GMT

Hi I was just wondering... My computer does a crash dump once in a while, when this happends the whold computer restarts can I do something about this? I have windows vista 64bit.

please email me at marcus_jordebrandt@hotmail.com

re: Understanding Crash Dump Files

CC Hameed — Thu, 20 Nov 2008 21:15:36 GMT

Marcus -

There are many things that might be causing your bugcheck situation (see http://blogs.technet.com/askperf/archive/2007/12/18/understanding-bugchecks.aspx). I would strongly recommend opening a case with Microsoft and have one of the Support Engineers examine the dump file to find out what might be causing the problem. Depending on the bugcheck itself, you might try opening up the dump file using the WinDBG (in the Debugging Tools for Windows) and running the command "!analyze - v" (without the quotes). That may point you to a specific driver that could be causing the issue ...

- CC

re: Understanding Crash Dump Files

Matt — Tue, 09 Dec 2008 00:05:30 GMT

Can you force a dump to an alternate disk. My OS partition is on a disk connected to an PCI-E RAID controller and the BSOD does not write the memory.dmp. I suspect the RAID driver is the problem. Can I get Server 2008 to dump to a SAS disk (non-system partition) that is directly connected to the mobo instead of the RAID card?

re: Understanding Crash Dump Files

Rajesh — Wed, 28 Jan 2009 03:28:23 GMT

Server: x86

OS: Windows Server 2003 Ent Edition SP1

Total RAM: 16GB Page File on C: 4GB , Pagefile on D: 20GB, Free Space on C: 22GB, Free Space on D: 20GB

Server is configured to Write the Memory.dmp to the D:

I have a server on which I'm hosting a SAP, sometime ago I ran into a Non-Paged pool related issues, the server was hung. I initiated the NMI Crash dump (All the registry keys are in place.). However, once the server was back, I dont see the dump file being generated.

Any help on this is much appreciated.

Thanks,

Rajesh

re: Understanding Crash Dump Files

Anil — Wed, 12 Aug 2009 06:49:58 GMT

hi,

i am in very initial stages of troubleshooting performance issues so my question might be the stupid question.

in one of the situation the domain controller was unresponsive "hard hang" state which got resolved with a reboot

is it possible to investigate what has caused the server to be unresponsive after the reboot.