How to generate a complete crash dump file or a kernel crash dump file by using an NMI on a Windows-based system

Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows.

INTRODUCTION

Sometimes, when you use the CTRL+SCROLL LOCK+SCROLL LOCK keyboard shortcut to generate a crash dump file, the operation does not function correctly. This shortcut may be useful in debugging a problem that causes a server to stop responding or crash. You would typically use this shortcut only when standard live debugging is not an option.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

303021 How to generate a memory dump file when a server stops responding (hangs)

This method does not work for all systems. For example, Hewlett-Packard (HP) BladeSystem servers from the Hewlett-Packard Development Company are managed through 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 crash dump file or a 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 crash dump file or a 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 standard troubleshooting methods have been completely exhausted.

More Information

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
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 The /maxmem switch in the Windows Boot.ini file

  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 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 "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. 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.
  14. Enable the NMI switch in the BIOS or by using the Integrated Lights Out (iLO) Web interface.

    Note For the exact steps, see the 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 recur.
For information about how to contact your hardware vendor, visit the following Microsoft Web site: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.


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.

خصائص

رقم الموضوع: 927069 - آخر مراجعة: 08‏/06‏/2011 - المراجعة: 1

تعليقات