Windows 10: Install and Configure WinDBG for BSOD Analysis

Note added. *Smile

 

I am having problems with Step #3 Start>all apps>Window Kits> etc... I am not typing this into the command panel, correct? Based on how it's displayed, i'm clicking on each description beginning with Start. I do not have an "all apps" icon. Do I just literally click every single app?

I apologize for what probably seems like a silly question. I am a complete novice and I am attempting debugging with no programming knowledge. I am a normal user attempting to figure if I have corrupt files.

 

No, you are going to programs from the start button in the bottom left. Right click and run as Administrator.





However, if you have no experience, you would be better off to start a thread in the BSOD section BSOD Crashes and Debugging - Windows 10 Forums

 

`

There is no All Apps or All Programs unless you are using something like Classic Shell or Start10.
You click Start, scroll down to Windows Kits, expand it and click on the appropriate WinDbg.

 

Hi, very good your post and thank you for such information, i followed all the steps but i got this message when trying to set the path for the symbols.

please help, thanks!!

 

You're simply missing the right symbols.
Load the dump a few times (open, load and close) so Windbg can download the right symbols.

 

Thanks Gav smooth as silk so same sort of use as in 7? a stupid question I know but just want to know beofr I do anything that will annoy people*Think

 

Ok Colin sorry about the name I was working from Gavs tutorial and hav got it set on both my main and small laptop now and one to go.

NB Posting problem I think is fixed.

 

Hello all

Thank you to the author for providing such a succinct tutorial.
I am having an issue with symbols, where when I open a Memory.dmp file, an error occurs in analysis:
Code: ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\SymCache*Symbol information Symbol search path is: SRV*C:\SymCache*Symbol information Executable search path is: *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows 10 Kernel Version 15063 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 15063.0.amd64fre.rs2_release.170317-1834 Machine Name: Kernel base = 0xfffff802`1a200000 PsLoadedModuleList = 0xfffff802`1a54c5a0 Debug session time: Tue May 16 20:22:37.672 2017 (UTC + 8:00) System Uptime: 0 days 0:18:28.312 *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Loading Kernel Symbols[/quote] Granted the dump file is around 2GB (is this big?). I have run the analysis a few times in the hope that symbols may be downloaded eventually, but still an issue it seems.

Can anybody see something in the text above to indicate where I may have gone wrong?

Richard

 

Everyone is having the same problem with symbols for the 15063 build. The fix is for Microsoft to do, nothing you or I or anyone else can do about it.

It's been reported multiple time but no resolution from Microsoft yet.

 

Thank you Ztruker, I must have missed that information.

 

In setting up the software to debug I was able to download and install. However I was not able to configure per page 1.

1. Download the WinDBG sdksetup.exe setup file.
2. Run sdksetup.exe, and specify the installation location (this example uses the default location):
2. Copy the highlighted text below, and paste it into the command prompt window using Ctrl+V and hit enter to change directory to the installation location path.

cd\Program Files (x86)\Windows Kits\10\Debuggers\x64\






The operating system is windows 10 version 1703 (OS Build 15063.296) x64 based PC.
Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> cd\Program Files (x86)\Windows Kits\10\Debuggers\x64\
x86 : The term 'x86' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:19
+ cd\Program Files (x86)\Windows Kits\10\Debuggers\x64\
+ ~~~
+ CategoryInfo : ObjectNotFound: (x86:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\Windows\system32>


How do you associate the .dmp files with WinDBG when the above copy paste command does not work?
Are there any other commands that may need modification?

 

I suggest to try it in phases, like cd 1 or 2 folders at a time.

 

Please explain....stuck on step #2.......Windows 10 Forums what should be copied and pasted now that the above does not work and how do you check the progress?

 

Cd per folder:
Code: cd\Program Files (x86)\ cd\Windows Kits\ cd\10\ cd\Debuggers\ cd\x64\[/quote]