Where are BSOD dump files located

Search, view and analyze BSOD dump files

So you're just about to have your first Blue Screen of Death (BSOD), or maybe your twentieth? Anyway, most people don't know how to fix BSOD problems on their own. If you have someone in your family who is geeky they might be able to fix the problem, but there are a number of situations where you need to send the "dump" files to a technical person so they can determine the source of the problem can .

The dump files are simply the log files that are created when the BSOD occurs. It contains all the information related to the failure and can be analyzed to determine what caused the failure. In this post, I'm going to tell you about a few free programs that will provide the dump files for you and either display them or create a neatly organized folder that you can put in a forum and post in a forum and send to your IT department. Email to a friend, etc. You can always look for the files and try to analyze them yourself, and I've gone through a little of them too.

If you want to try and view the crash reports for yourself, you can try another nifty program called BlueScreenView.

//www.nirsoft.net/utils/blue_screen_view.html

The program will automatically search through all of your minidump files, which are basically useful subsets of the crash dump file, and display information about each crash in a table. The minidump files are meant to be smaller with only essential information so that they can be more easily sent over the Internet.

The cool thing about this program is that it shows the original blue crash screen that Windows shows and a whole bunch of other information including when the crash occurred and the file name / description of each driver that caused the crash.

Overall, BlueScreenView is very good, but sometimes the wrong driver is causing the problem. The reason for this is to assume that the last driver to load before the crash is the cause and therefore Microsoft drivers are much more to blame than third party drivers which are the real culprits.

Windows debugging tools

If you really want to get your hands dirty without becoming a technical guru, you can download the Debugging Tools for Windows which requires the Windows SDK to be downloaded. You also have the option to download a newer debug tool called WinDbg Preview. It has a better front end and is faster than the original WinDbg tool that is in the SDK. You can download WinDbg here:

//docs.microsoft.com/de-de/windows-hardware/drivers/debugger/debugger-download-tools

Otherwise, download the Windows 10 SDK from here:

//developer.microsoft.com/en-US/windows/downloads/windows-10-sdk

When you go to the installation you will see a list of options with check boxes. You just need the Windows Debugging Tools to install. Everything else can be deactivated.

Once installed, you can go to All Programs and see a new folder called Windows Kits that has the debugging tool (WinDbg) in it.

Just start the program and click on File and Open crash dump .

Now all you have to do is search your computer for files that end in * .dmp or * .mdmp. You can find all minidump files here:

% SystemRoot% \ minidump

You need to change your system settings in order to view hidden files and system files. Otherwise they will not be displayed. After opening the dump file, an attempt is made to analyze it and let you know where the problem occurred. It is a good idea to use BlueScreenView and WinDbg to analyze the dump file as it may give different answers.

This is definitely not a comprehensive guide to reading or analyzing dump files, but hopefully it will get you in the right direction depending on what you want to do with the dump files. Enjoy!