From 2a7380850fac642e9621c552abb5c68c191e3f3d Mon Sep 17 00:00:00 2001 From: danmatts <82900873+danmatts@users.noreply.github.com> Date: Tue, 20 Apr 2021 12:32:14 -0500 Subject: [PATCH] Added Note clarifying the NMICrashDump key usage. For Windows 8+ and Windows Server 2012+ the NMICrashdump key is not required and no longer has any effect. --- .../generate-kernel-or-complete-crash-dump.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/windows/client-management/generate-kernel-or-complete-crash-dump.md b/windows/client-management/generate-kernel-or-complete-crash-dump.md index ac31619d20..c5746be08c 100644 --- a/windows/client-management/generate-kernel-or-complete-crash-dump.md +++ b/windows/client-management/generate-kernel-or-complete-crash-dump.md @@ -78,6 +78,9 @@ To do this, follow these steps: > [!IMPORTANT] > Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, [back up the registry for restoration](https://support.microsoft.com/help/322756) in case problems occur. + +>[!Note] +> This registry key is not required for clients Windows 8 and newer or servers Windows Server 2012 and newer. Setting this registry key on newer versions of Windows has no effect. 1. In Registry Editor, locate the following registry subkey: @@ -110,4 +113,4 @@ If you want to run NMI in Microsoft Azure using Serial Console, see [Use Serial ### Use Debugger -[Forcing a System Crash from the Debugger](/windows-hardware/drivers/debugger/forcing-a-system-crash-from-the-debugger) \ No newline at end of file +[Forcing a System Crash from the Debugger](/windows-hardware/drivers/debugger/forcing-a-system-crash-from-the-debugger)