How to Debug Crash Dumps Using WinDbg in Windows 10 If your PC is slowing down or hit by the Blue Screen of Death, don't panic. Windows Debugger can help you get to the root of the problem in minutes. In this video, we'll show you exactly how to use it to diagnose and fix crashes. Before we begin, be sure to subscribe to NinjaOne's IT Video Hub and our YouTube channel for more tech content like this. What Is WinDbg? Windows Debugger—WinDbg for short— is a free diagnostic tool from Microsoft. It lets you analyze crash dump files to figure out exactly which driver or system component caused your PC to crash. It's a favorite among IT pros and developers who need to dig deep into system failures. That said, using it comes with some prerequisites. Prerequisites before Using WinDbg Before you start, make sure you’ve got a Windows 10 PC with administrator rights, at least one crash dump file, internet access, and WinDbg itself. Installing WinDbg There are two ways to install WinDbg. Option one: through the Microsoft Store. Simply open the store, search for “WinDbg Preview,” and click Install. Option two: via the Windows 10 SDK installer. Download the installer, run it, and select only Debugging Tools for Windows. Setting Up WinDbg Once WinDbg is installed, let’s set it up. Right-click the app and choose Run as administrator. Go to File and then Symbol File Path and enter this path... Lastly, click OK to save your changes. Opening a Crash Dump To analyze a crash, just go to File, followed by Open Crash Dump. Navigate to your dump files—mini or full— and open one. Analyzing the Crash Dump With the dump loaded, type this in the command bar— !analyze -v and press Enter. WinDbg will process the file and show a detailed report with the bug check code, faulty mobile or driver, call stack, and likely root cause. Interpreting the Results As you interpret the results of the crash report, pay attention to these sections: BUGCHECK_STR for the crash name; Probably caused by for the likely culprit; IMAGE_NAME for the filename of the faulting module; and Stack text for a call trace of the crash sequence. WinDbg may look intimidating, but with just a few commands you can trace, most system crashes right back to their source. It's an essential tool for anyone who wants to keep their system stable and reliable. For more information, check out our official blog post on How to Debug Crash Dumps Using WinDbg in Windows 10, linked in the description below. Be sure to subscribe to NinjaOne's IT Video Hub and our YouTube channel for more tech content like this.