Install and Configure WinDBG for BSOD Analysis  

Thanks Rich.

I've tried it both ways. Actually I usually don't extract zip, just open and click on .dmp file. So then I decided I should extract and try.

I seem to be over the symbol issue, not sure how... but still does not produce that initial Bugcheck analysis that it shows in tutorial or way I use to get. Stops at "For analysis of this file.... "

Example:



Going to try zbook's suggestion although I don't think I had that installed before as he noted, it is not part of tutorial.

Edit: Tried preview, interesting. Runs one line longer but still does not produce the initial Bugcheck analysis box. I guess I can always click on the !analyse -v link.

Wish I could relate change I made that caused this change.

If anyone knows of parameter to kick off initial bugcheck analysis if they could post.

Thank you guys

zbook said:

There are two main options for symbols:
a) store on the computer
b) use the live Microsoft database

Windbg preview is not in the tutorial.

See if you can download and install: Windbg preview
https://docs.microsoft.com/en-us/win...download-tools

Usually you use Microsoft's servers to store the symbols on your computer, that is what this tutorial is about after all.
Considering the symbol issues many have run into lately, and possibly will run into again in the future, I'd say make sure your configurations are correct as that will save trouble.

Thanks Axe0.

I seem to be over symbol issue. When I use to start analysis I would get that Bugcheck analysis box, now I don't. Is this a setting I haven't enabled?

There is no such setting, what version of Windbg are you currently using?

What I assume is near the latest.

​

using 1809 Windows Pro

This quick analysis. The box that says Bugcheck analysis and the four lines of text.




I just open another dump and got "The system cannot find the file specified. Seems to always happen on

NTOSKRNL



Thank you zbook.

As it happens there still appears to be symbol issues, currently I would say those errors are expected until Microsoft fixes the symbols problem.

Thanks axe0.

Figured it was me.