From 46c9450f3d459912431513c6c0a086b496a391d4 Mon Sep 17 00:00:00 2001 From: Bruce Dawson Date: Tue, 30 Mar 2021 14:15:44 -0700 Subject: [PATCH] Update windows/client-management/troubleshoot-stop-errors.md Avoid redundant 'Note' Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/troubleshoot-stop-errors.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/client-management/troubleshoot-stop-errors.md b/windows/client-management/troubleshoot-stop-errors.md index 8d70fe9ea9..c177b5826e 100644 --- a/windows/client-management/troubleshoot-stop-errors.md +++ b/windows/client-management/troubleshoot-stop-errors.md @@ -35,8 +35,8 @@ Our analysis of the root causes of crashes indicates the following: - 5 percent are caused by Microsoft code - 15 percent have unknown causes (because the memory is too corrupted to analyze) ->[!NOTE] ->Note that the root cause of Stop errors is never a user-mode process. While a user-mode process (such as Notepad or Slack) may trigger a Stop error, it is merely exposing the underlying bug which is always in a driver, hardware, or the OS. +> [!NOTE] +> The root cause of Stop errors is never a user-mode process. While a user-mode process (such as Notepad or Slack) may trigger a Stop error, it is merely exposing the underlying bug which is always in a driver, hardware, or the OS. ## General troubleshooting steps