Configuring Windows 2008 servers for memory dump:

Below are the instructions for configuring Complete Memory dump

As this is Windows Server 2008 SP 1 following hotfixes needs to be installed on the server before
configuring the server for memory dump
960658  Windows Server 2008 systems may generate a truncated dump file if the system
supports Dynamic Hardware Partitioning (DHP) and if memory is hot added
http://support.microsoft.com/default.aspx?scid=kb;EN-US;960658

950904  The system stops responding, and no dump file is generated when a computer that is
running Windows Vista or Windows Server 2008 receives a nonmaskable interrupt
http://support.microsoft.com/default.aspx?scid=kb;EN-US;950904

953533  A computer that is running an x86 version of Windows Vista or of Windows Server 2008
on an IDE/ATA disk does not generate a valid dump file when PAE mode is enabled
http://support.microsoft.com/default.aspx?scid=kb;EN-US;953533

955635  The page file size may become alternately too small or too large when you start
Windows Server 2008 or Windows Vista if there is no available free disk space, and the page file
size is managed by the system
http://support.microsoft.com/default.aspx?scid=kb;EN-US;955635

957517  A dedicated complete memory dump file may not be successfully generated if the
volume that stores the dedicated dump file has insufficient free space
http://support.microsoft.com/default.aspx?scid=kb;EN-US;957517

971284  A hotfix is available to enable CrashOnCtrlScroll support for a USB keyboard on a

computer that is running Windows Vista SP1 or Windows Server 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;971284

Install the above hotfixes and reboot the server.

a.  Click Start , click Run , type Regedit , and then click OK . 
b.  Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl 
c.  On the Edit menu, point to New , and then click String Value . 
d.  In the details pane, type DedicatedDumpFile , and then press ENTER. 
e.  Right-click DedicatedDumpFile , and then click Modify . 
f.  In the Value data box, type <drive>:\<dedicateddumpfile.sys> , and then click OK .
Note <drive> is a placeholder for a drive that has enough disk space for the paging file, and
<dedicateddumpfile.sys> is a placeholder for the dedicated file and the full path. 
g.  On the Edit menu, point to New , and then click DWORD Value . 
h.  Type DumpFileSize , and then press ENTER. 
i.  Right-click DumpFileSize , and then click Modify . 
j.  In the Edit DWORD Value dialog box, click Decimal under Base . 
k.  In the Value data box, type the appropriate value, and then click OK .
Note The size of the dump file is in megabytes. 
l.  Right-click DumpFile , and then click Modify . 
m.  In the Value data box, type <drive>:\<path>\Memory.dmp , and then click OK .

Note When the system crashes, this is the location where the memory dump file is created by
using the dedicated file instead of by using the Pagefile.sys file. 
n.  Exit Registry Editor. 

Step 2: Create a complete memory dump file 1.  Click Start , right-click Computer , and then click
Properties . 
2.  Click Advanced system settings on the System page, and then click the Advanced tab. 
3.  Click Settings under the Writing debugging information area, and then make sure Complete
memory dump is selected. 
Note By default, Complete memory dump is disabled. You can enable the option if your
computer has more than 2 GB of physical RAM.

Note If you want to enable the Complete memory dump option, manually set the
CrashDumpEnabled registry entry under the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

Click Start , click Run , type regedit , and then press ENTER .
1.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters
3. Click Edit , point to New , and then click DWORD Value .
4. Type CrashOnCtrlScroll , and then press ENTER .
5. Click Edit , and then click Modify .
6. Type 1 , and then click OK .
7. Exit Registry Editor.

For the Perfmon I have attached the template to this email.

Go to start  run type “Perfmon” and click on Ok
Expand the data collector set, and right click on User defined and Point to New and Data
collector Set
Give the name of the server and select the first option “Create from a template” and click on
Next.
Now Click on Browse and point it to the Perfmon template and click on next and finish and start
the perfmon.

The next time the issue occurs hold down the right CTRL key and then pressing
the SCROLL LOCK key two times
This will generate the memory dump of the server.

In order to generate the dump using NMI option within ILO, we need to follow steps given in
below link,
 
http://support.microsoft.com/kb/927069/
 
1.       In Registry Editor, locate the following registry subkey:
2.       HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
3.       Right-click CrashControl, point to New, and then click DWORD Value.
4.       Type NMICrashDump, and then press ENTER.
5.       Right-click NMICrashDump, and then click Modify.
6.       In the Value data box, type 1, and then click OK.
7.       Restart the computer.
8.       Hardware vendors, such as HP, IBM, and Dell, may provide an Automatic System Recovery
(ASR) feature. You should disable this feature during troubleshooting. For example, if HP and
Compaq's ASR feature is enabled in the BIOS, disable this feature while you are
troubleshooting to generate a complete memory.dmp file. For the exact steps, contact your
hardware vendor.
9.       Enable the NMI switch in the BIOS or by using the Integrated Lights Out (iLO) Web interface.