Taking A Memory Dump In Windows - Hitachi Compute Blade 2500 Getting Started Manual

Taking a memory dump in Windows

This section describes how to take a memory dump when a failure occurs in
Windows.
Triggers for taking a memory dump
When a STOP (error message displayed on a blue screen) error occurs, a
memory dump is taken automatically. Also, when Windows becomes
unresponsive, the management module issues an MNI to take a memory
dump.
While a memory dump is being taken
• In Windows Server 2012 or later, when the percentage displayed in the
upper right corner of the screen reaches "100% complete", the memory
dump is complete.
• In Windows Server 2008 R2, when the figure in the lower part of the
screen reaches "100", the memory dump is complete.
Tip: While a memory dump is being taken, do not issue an MNI. Doing so
may cause Windows to become unresponsive.
When the memory dump is complete, if Windows does not restart
automatically, restart Windows manually.
After a memory dump is taken
After the system restarts, the memory dump that was taken is copied to the
specified output destination. The output destination of the memory dump is
%SystemRoot%\MEMORY.DMP (initial setting
dump is complete, the following event is output to the system event log.
Event ID: 1001
Source: BugCheck
Until the above-mentioned event is output to the system event log, do not
conduct any operations on the memory dump file.
#
After a memory dump has been taken, if there is no memory dump file in
the above-mentioned output destination, the output destination has been
changed from the initial setting. See the following registry information to
check the current output destination.
Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
\CrashControl
Name: DumpFile
B-4
Taking a Memory Dump of the OS Running on a Server Blade
Hitachi Compute Blade 2500 Series Getting Started Guide
#
). When the output of the memory