Remember the tangle of troubleshooting-use windbg to solve the windbg hang Problem

This morning, the customer sent an hang dump and was eager to see it. As a result, windbg will hold the hang every time it clicks open crash dump in the menu.

• Retry. The result is the same.
• Restart windbg. The result is the same.
• Restart the machine. The result is the same.
• Uninstall and reinstall windbg. The result is the same.
• If you suspect that debug diag 1.2 is faulty, uninstall it and the result is the same.
• The default symbol path is modified, and the result is the same.

I am so angry that I have no idea. I have to use big moves and use task manager to capture a windbg hang dump.

Find a colleague to check the dump machine. Use windbg to open the dump and find that windbg is hang on the following thread.

 

 

It seems that windbg wants to access resources on a certain network.

So I unplugged the network cable and tried again. The problem disappears.

Plug in the network cable to reproduce the problem.

It seems that windbg is trying to open the dump that it opened last time, but it seems that it cannot be found, so it is hang.

 

Solution

======================

1. Disconnect the network and force windbg to open the open crash dump dialog box normally.

2. Select a dump on the local machine to open it.

3. Disable windbg.

4. connect to the network and try again. Solve the problem.