For more information on using this feature, refer to the article Windows feature lets you generate a memory dump file by using the keyboard. You can configure values under the following registry subkeys for different keyboard shortcut sequences to generate the memory dump file:.
Dump1Keys The Dump1Keys registry value is a bit map of the first hot key to use. Note You can assign Dump1Keys a value that enables one or more keys as the first key used in the keyboard shortcut sequence.
For example, assign Dump1Keys a value of 0x11 to define both the rightmost and leftmost SHIFT keys as the first key in the keyboard shortcut sequence. Dump2Key The Dump2Key registry value is the index into the scancode table for the keyboard layout of the target computer. The following is the actual table in the driver.
Note Index sysreq is a special case because an key keyboard has a different scan code. It is possible for a system to freeze in such a way that the keyboard shortcut sequence will not work. However, this should be a very rare occurrence.
Typically this would be triggered using a hardware level remote management interface. Essentially you set the NMICrashDump registry value and then use the hardware specific remote management interface to trigger the crash. Where the heck is Scroll Lock on my tiny tablet keyboard?
Fortunately you can change the magic keys. Be careful. If the original hang was blocking boot or logon you may have to use an alternative boot path such as Safe Mode to get there. In case you decide to have a go at debugging it using windbg. You triggered it manually. I stress this because many debugging tools or guides e. Instead your goal is to use the memory dump to find the cause of the unresponsiveness which began prior to the crash.
This is going to involve looking for locks, IRPs, critical sections, hung threads, etc. If only there were a cheat code…. You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Products 72 Special Topics 41 Video Hub Most Active Hubs Microsoft Teams. Security, Compliance and Identity. Microsoft Edge Insider. Select Advanced system settings , and then select the Advanced tab.
Make sure that Kernel memory dump or Complete memory dump is selected under Writing Debugging Information. You can change the dump file path by edit the Dump file field.
When the computer crashes and restarts, the contents of physical RAM are written to the paging file that is located on the partition on which the operating system is installed. Depending on the speed of the hard disk on which Windows is installed, dumping more than 2 gigabytes GB of memory may take a long time. Even in a best case scenario, if the dump file is configured to reside on another local hard drive, a significant amount of data will be read and written to the hard disks.
This can cause a prolonged server outage. Use this method to generate complete memory dump files with caution. Ideally, you should do this only when you are explicitly requested to by the Microsoft Support engineer. Any kernel or complete memory dump file debugging should be the last resort after all standard troubleshooting methods have been completely exhausted. If you can log on while the problem is occurring, you can use the Microsoft Sysinternals NotMyFault tool.
To do this, follow these steps:. Download the NotMyFault tool. On some computers, you cannot use keyboard to generate a crash dump file. A keyboard is not attached to the HP BladeSystem server. 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. Follow the steps in this section carefully.
0コメント