From 8dabf0996a9766e591826b966eee55c7fb34118d Mon Sep 17 00:00:00 2001 From: Aaron Czechowski Date: Tue, 3 May 2022 12:00:38 -0700 Subject: [PATCH] fix issues from review --- windows/client-management/troubleshoot-stop-errors.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/windows/client-management/troubleshoot-stop-errors.md b/windows/client-management/troubleshoot-stop-errors.md index 120223fa8d..76abcad710 100644 --- a/windows/client-management/troubleshoot-stop-errors.md +++ b/windows/client-management/troubleshoot-stop-errors.md @@ -29,10 +29,10 @@ There's no simple explanation for the cause of stop errors (also known as blue s Our analysis of the root causes of crashes indicates that: -- 70% are caused by third-party driver code -- 10% are caused by hardware issues -- 5% are caused by Microsoft code -- 15% have unknown causes, because the memory is too corrupted to analyze +- 70% are caused by third-party driver code. +- 10% are caused by hardware issues. +- 5% are caused by Microsoft code. +- 15% have unknown causes, because the memory is too corrupted to analyze. > [!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. @@ -243,9 +243,6 @@ This section doesn't contain a list of all error codes, but since many error cod The following sections list general troubleshooting procedures for common stop error codes. -Stop error message and code | Mitigation ---- | --- - ### VIDEO_ENGINE_TIMEOUT_DETECTED or VIDEO_TDR_TIMEOUT_DETECTED Stop error code 0x00000141, or 0x00000117