Sometimes, when you use the CTRL+SCROLL LOCK+SCROLL LOCK keyboard shortcut to generate a crash dump file, the operation might not function correctly. This shortcut may be useful in debugging the cause of a server that has stopped responding (hangs) when typical live debugging is not possible.
For more information, click the following article number to view the article in the Microsoft Knowledge Base: However, Hewlett Packard (HP) BladeSystem servers from the Hewlett-Packard Development Company are managed by using a browser-based graphical user interface (GUI). A keyboard is not attached to the HP BladeSystem server. Therefore, you cannot use this keyboard shortcut to generate a crash dump file. In these cases, you must generate a complete or kernel crash dump file by using the Non-Maskable Interrupt (NMI) switch that causes an NMI on the system processor. This article describes how to generate a complete or kernel crash dump file by using an NMI switch.

Note Use this method to generate complete memory dump files with caution. Ideally, you should only do this only when you are explicitly requested to by the Microsoft Customer Support Services Engineer. Any kernel or complete memory dump file debugging should be the last resort when all the typical methods of troubleshooting have been completely exhausted.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Before you continue, look in the hardware BIOS reference manual or contact your hardware vendor to determine whether the server is equipped with an NMI switch. To enable complete memory dump files on your server, follow these steps:

1.	Set up the page file to generate a complete memory dump file. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 108393 (http://support.microsoft.com/kb/108393/) The /maxmem switch in the Windows Boot.ini file Note On a server that is running Windows Server 2003 Enterprise Edition with PAE, you should increase the page file size to 128 gigabytes (GB).
2.	Right-click My Computer, and then click Properties.
3.	Click the Advanced tab.
4.	Under Startup and Recovery, click Settings.
5.	Make sure that Kernel memory dump or Complete memory dump is selected under Writing Debugging Information.
6.	You can change the location of the memory dump file to a different local partition if you do not have sufficient room on the partition where the operating system is installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 886429 (http://support.microsoft.com/kb/886429/) What to consider when you configure a new location for memory dump files in Windows Server 2003 For more information, click the following article number to view the article in the Microsoft Knowledge Base: 885117 (http://support.microsoft.com/kb/885117/) "Kernel Memory Dump" is displayed in Startup and Recovery, but a complete memory dump is performed in Windows 2000 or in Windows Server 2003
7.	In Registry Editor, locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
8.	Right-click CrashControl, point to New, and then click DWORD Value.
9.	Type NMICrashDump, and then press ENTER.
10.	Right-click NMICrashDump, and then click Modify.
11.	In the Value data box, type 1, and then click OK.
12.	Restart the computer.
13.	If the hardware has a feature such as HP/Compaq's Automatic System Recovery (ASR) turned on in the BIOS, disable this feature while you are troubleshooting to generate a complete memory.dmp file.
14.	Enable the NMI switch in the BIOS or by using the Integrated Lights Out (iLO) Web interface. Note For the exact steps, see your BIOS reference manual or contact your hardware vendor.
15.	Test this method on the server by using the NMI switch to generate a dump file. You will see a STOP 0x00000080 hardware malfunction.
16.	Wait for the problem to reoccur.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.