Windows 10: Install and Configure WinDBG for BSOD Analysis

Don't use PowerShell.....use CMD.

 

Use a Command Prompt as suggestd. Also enclose the path in double quotes as it contains a blank:

cd "C:\Program Files (x86)\Windows Kits\10\Debuggers\x64" (space between CD and first ".

 

Used administrative command prompt and was able to complete the step.
The administrative command prompt location on the the left lower corner windows menu had changed to administrative power shell when version 1607 was upgraded to 1703. I did not realize that it had only moved its position on the menu. For step 4 when the zip file is downloaded using the firefox browser what should be the open with source if you have not installed a third party program? Will all the files have to be saved in a file on the computer or will the minidump files be able to opened and analyzed without saving? If a third party software is needed which one is recommended?

 

After installing 7 zip I was able to see that Firefox had downloaded files. When I clicked on them there was a flash on the screen and there was no new window. There was no new information. It did not open. The web page was then moved from Firefox to Chrome. The download when clicked opened and the debugger analyzed the first dmp file. I then repeated for each dmp file. How do you fix Firefox so that it does not just flash and actually opens the file like in Chrome?

When you view the "probably caused by" how do you determine the application or hardware related to the result? For example:
any *.sys
What happens if it is *.exe instead of *.sys?
What is the significance of GetContextState failed

 

If it is .exe it is guaranteed a file of Windows, there are no drivers from 3rd party using .exe extension.

An issue with the newest Windbg, I reverted to an earlier version of Windbg to get rid of it.

Determining if an issue is hardware requires experience, experience you get by trial and error, the best way to go through trial and error is research and asking. Not only asking others, but also asking yourself how something happened and/or why, which is best done when you're more familiar with Windows in-depth.