Windows feature lets you generate a memory dump file by using the keyboard (244139)



The information in this article applies to:

  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Datacenter Edition
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-based Systems

This article was previously published under Q244139
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SUMMARY

Windows includes a feature that you can use to cause the system to stop responding and to generate a memory dump file (Memory.dmp). When you do this, you receive a Stop error message that resembles the following:
*** STOP: 0x000000E2 (0x00000000,0x00000000,0x00000000,0x00000000)
The end-user manually generated the crashdump.
Note You cannot use a keyboard shortcut to generate a memory dump file if the following conditions are true:
  • The computer is running Microsoft Windows Server 2003.
  • The computer was not upgraded from an earlier operating system.
  • The computer uses only a universal serial bus (USB) keyboard.
You expect to generate a memory dump file by holding down the right CTRL key and pressing the SCROLL LOCK key two times. To resolve this issue in Microsoft Windows Server 2003, see the "Windows Server 2003 resolution" subsection at the end of the "More Information" section.

MORE INFORMATION

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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
By default, this feature is disabled. To enable this feature, modify the registry as indicated in this article, and then restart the computer. After you restart the computer, you can generate a Memory.dmp file by holding down the right CTRL key and pressing the SCROLL LOCK key two times. You must use the CTRL key on the right side of the spacebar.

Note The following steps do not work on legacy-free computers except computers that are running Windows Server 2003. For example, the following steps do not work on a computer that exclusively uses a USB keyboard. In Windows Server 2003, the Kbdhid.sys driver supports USB keyboards. However, this driver has a limitation that the i8042prt.sys driver does not have. When you use the Kbdhid.sys driver, the CTRL+SCROLL LOCK+SCROLL LOCK shortcut does not work if the computer stops responding at a high interrupt request level (IRQL). This limitation occurs because the Kbdhid.sys driver operates at a lower IRQL than the i8042prt.sys driver does. The i8042prt.sys driver is for the standard 101/102-key keyboard and the Microsoft Natural PS/2 keyboard.

For the computer to stop responding, the CTRL+SCROLL LOCK+SCROLL LOCK shortcut must be received and processed by the i8042prt.sys driver. These steps also do not work in a Virtual PC session that has VM Additions installed. If you uninstall VM Additions, this procedure works as expected. VM Additions replaces the standard driver with the Vpc_8042.sys driver. The Vpc_8042.sys driver is the driver for the VM Additions PC/AT Enhanced PS/2 keyboard [101/102-Key]. In a Virtual PC session that has VM Additions installed, you must attach a debugger.

To attach a debugger, follow these steps:
  1. Start Registry Editor.
  2. Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters

  3. On the Edit menu, click Add Value, and then add the following registry entry:

    Name: CrashOnCtrlScroll
    Data Type: REG_DWORD
    Value: 1

  4. Exit Registry Editor, and then restart the computer.

How to select memory dump file options

Three types of memory dump files can be generated. Choose one before you manually trigger the dump file. To do this, follow these steps:
  1. Right-click My Computer, and then click Properties.
  2. Click the Advanced tab, and then click the Startup and Recovery button.
  3. Click Write Debugging Information, and then click to select either Complete Memory Dump, Kernel Memory Dump, or Small Memory Dump.
For more information about memory dump file options, click the following article number to view the article in the Microsoft Knowledge Base:

254649 Overview of memory dump file options for Windows Server 2003, Windows XP, and Windows 2000

Note If the server has a feature such as the Automatic System Restart (ASR) feature that is found in some Compaq computers, disable the feature. It can interrupt the dump process. On a Compaq computer, you can disable the ASR feature by modifying the basic input/output system (BIOS) settings.

Note Complete memory dumps may not be available on a computer that has 2 or more gigabytes (GB) of RAM. To limit the memory that Windows 2000 can access, add the <MaxMem=2000> parameter to the Boot.ini file.

If you have installed the security update that is described in article 835732 in the Microsoft Knowledge Base, or you have installed a service pack that contains this security update, view the following Microsoft Knowledge Base article:

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

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

835732 MS04-011: Security Update for Microsoft Windows

Windows Server 2003 resolution

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.PrerequisitesNo prerequisites are required.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File information The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003, 32-bit versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Kbdhid.sys5.2.3790.49316,89628-Feb-200600:03x86NoneRTMQFE
Kbdhid.sys5.2.3790.264917,40828-Feb-200603:11x86SP1SP1QFE
Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Kbdhid.sys5.2.3790.264924,57613-Apr-200615:59x64
Windows Server 2003, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Kbdhid.sys5.2.3790.49347,10413-Apr-200615:54IA-64NoneRTMQFE
Kbdhid.sys5.2.3790.264949,66413-Apr-200615:59IA-64SP1SP1QFE
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.

Modification Type:MajorLast Reviewed:10/13/2006
Keywords:kbWinServ2003preSP2fix kbBug kbfix kbQFE kbhotfixserver kbpubtypekc KB244139 kbAudITPRO