Tell me about the issue and I’ll help you find the solution you need.
Windows feature lets you generate a memory dump file by using the keyboard
Content provided by Microsoft
Applies to: Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based SystemsMicrosoft Windows Server 2003, Enterprise Edition for Itanium-based SystemsMicrosoft Windows Server 2003, Datacenter x64 EditionMicrosoft Windows Server 2003, Enterprise x64 EditionMicrosoft Windows Server 2003, Standard x64 EditionMicrosoft Windows Server 2003, Datacenter Edition (32-bit x86)Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)Microsoft Windows Server 2003, Standard Edition (32-bit x86)Microsoft Windows Server 2003, Web EditionWindows Vista Service Pack 1Windows Server 2008 for Itanium-Based SystemsWindows Server 2008 DatacenterWindows Server 2008 EnterpriseWindows Server 2008 StandardWindows Web Server 2008More
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.
After you enable the feature, you can generate a memory dump file by holding down the right CTRL key and pressing the SCROLL LOCK key two times. The feature is available for both PS/2 and universal serial bus (USB) keyboards. PS/2 keyboards use the i8042prt.sys driver that is included with the keyboard. However, for USB keyboards that are attached to Windows Server 2003-based systems, you must install a hotfix for the Kbdhid.sys driver.For more information about this hotfix, see the resolution in the "More Information" section.
Note There is a limitation with the Kbdhid.sys driver that allows for you to generate the memory dump process by using a USB keyboard. The CTRL+SCROLL LOCK+SCROLL LOCK keyboard shortcut does not work if the computer stops responding at a high interrupt request level (IRQL). This limitation exists because the Kbdhid.sys driver operates at a lower IRQL than the i8042prt.sys driver.
For more information on how to resolve this issue visit the following Microsoft Web site: