From fee27e5eecc58608dd79c87db32a3f9f505cc0b3 Mon Sep 17 00:00:00 2001 From: Lovina Saldanha <69782111+Lovina-Saldanha@users.noreply.github.com> Date: Wed, 10 Mar 2021 18:39:11 +0530 Subject: [PATCH] Update troubleshoot-stop-errors.md To fix suggestions --- 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 db3002bb91..4d9ecb90f5 100644 --- a/windows/client-management/troubleshoot-stop-errors.md +++ b/windows/client-management/troubleshoot-stop-errors.md @@ -146,7 +146,7 @@ You can use the tools such as Windows Software Development KIT (SDK) and Symbols a. If the computer is connected to the Internet, enter the [Microsoft public symbol server](/windows-hardware/drivers/debugger/microsoft-public-symbols) (https://msdl.microsoft.com/download/symbols) and click **OK**. This is the recommended method.
b. If the computer is not connected to the Internet, you must specify a local [symbol path](/windows-hardware/drivers/debugger/symbol-path). 6. Click on **Open Crash Dump**, and then open the memory.dmp file that you copied. See the example below. - ![WinDbg](images/windbg.png) + ![WinDbg img](images/windbg.png) 7. There should be a link that says **!analyze -v** under **Bugcheck Analysis**. Click that link. This will enter the command !analyze -v in the prompt at the bottom of the page. 8. A detailed bugcheck analysis will appear. See the example below. ![Bugcheck analysis](images/bugcheck-analysis.png) @@ -576,4 +576,4 @@ ReadVirtual: 812d1248 not properly sign extended ## References -[Bug Check Code Reference](/windows-hardware/drivers/debugger/bug-check-code-reference2) \ No newline at end of file +[Bug Check Code Reference](/windows-hardware/drivers/debugger/bug-check-code-reference2)