This is what worked for me: Download the following DLLs: clr.dll mscordacwks.dll SOS.dll from this folder on the machine that generated the dump: C:\Windows\Microsoft.NET\Framework64\v4.0.30319 Run the following command. The path to SOS.DLL should be without quotes, unescaped path delimiters: .load path to downloaded SOS.DLL I think a new WinDbg session is required for this to … Read more
My favorite is the command .cmdtree <file> (undocumented, but referenced in previous release notes). This can assist in bringing up another window (that can be docked) to display helpful or commonly used commands. This can help make the user much more productive using the tool. Initially talked about here, with an example for the <file> … Read more
Here are some general steps that will get you on your way: First, you must change your compiler’s settings so that it creates PDB files, even for release builds. Later versions of the Visual C++ compiler do this by default, but in many versions of Visual C++ you must do this yourself. Create program database … Read more
There’s a few excellent blogs out there that help to gain windbg proficiency on an everyday basis: Dr. Debugalov Nynaeve Advanced Windows Debugging Debugging Toolbox Debugging Tricks Oleg Starodumov List of posts from/to Ivan Brugiolo Windbg by Volker von Einem I, personally, just started using windbg for all my debugging tasks and soon enough there … Read more
Start WinDbg from the command line using the -logo option: windbg.exe -logo logfile.txt That will get everything done logged to the file specified. You can find more details of the command line options here. Or, if you are already in a debugging session, you can use the .logopen command to start logging. For more info … Read more
Symbols can be set up correctly in various different ways. WARNING: The examples here use \\server\symbols which is typically a network storage that is not available. Adapt it to your local server or leave that part out completely if you don’t have one. A non-existent server may cause delays etc. TLDR version for 80% of … Read more
If you are wondering why you should use windbg over Visual Studio, then you need to read Advanced Windows Debugging. Any time you need to debug a truly ugly problem windbg has better technology to do it with than Visual Studio. Windbg has a more powerful scripting language and allows you to write DLLs to … Read more
Doing this by hand needs bravery 😉 Please check this Official MS DebugDiag 2.2: https://www.microsoft.com/en-us/download/details.aspx?id=49924 it has come with analyzer so you don’t have to do with your hand. With DebugDiag, I think you will find your problem faster then ever…
I spoke to an AMD engineer at the Microsoft Build conference about this error, and showed him my repro. He emailed me this morning: We have investigated and found that this is due to a known errata in the Llano APU family. It can be fixed via a BIOS update depending on the OEM – … Read more
I don’t have the tool now, but as far as I remember it should be Ctrl+Break.