Windows 10 How to Read Dump File
How to Utilize a Minidump File to Fix Your Windows BSOD
Information technology finally happened. Out of the blue, you're enjoying a game, watching a moving picture, or merely reading on the internet, when your operating system decides it doesn't want to cooperate and suddenly yous're facing down a BSOD or Blue Screen of Death. A BSOD is something that no Windows user wants to run into, because information technology means that your system has crashed, costing you fourth dimension and perhaps even resulting in data loss.
Perchance the worst thing about getting a Blue Screen of Expiry is that it could exist the consequence of whatever number of problems, from a faulty piece of hardware to a commuter error to having a page fault in a non-paged expanse (a result of a file not being found in retentiveness). However, all isn't lost and we're going to show y'all how to enable and use a minidump log file to diagnose the problem.
Why You Need a Minidump File to Diagnose Your BSOD
In earlier versions of Windows, the BSOD showed yous some error codes that were at least a picayune fleck helpful. Still, in Windows 10, the screen gives y'all a terminate lawmaking you can write down and research and a QR code you can use with your phone. However, this only sends you to the Microsoft website and provides a clarification of certain error codes.
What nosotros find useful is configuring Windows to save a file that contains lots of information regarding the BSOD and how nosotros tin can go nearly fixing the error. This is called a minidump file.
How to Configure Windows to Salve a Minidump File.
By default, the choice to create a minidump file is not enabled so you'll demand to turn it on. Practice this now, even if you don't have a BSOD problem, because otherwise you lot won't take a log when the crash happens.
ane. Navigate to the System Properties Command Panel menu. Y'all can get there by typing "sysdm.cpl" into the Windows search box. Or by going to Settings->System->Most and clicking Avant-garde arrangement settings.
2. Select the Advanced tab.
3. Enable the following options:
● Write an event to the system log
● Automatically restart
● Writing debugging data -> Small memory dump (256kb).
With this enabled, whenever Windows crashes, the minidump file will be created under "%SystemRoot%\Minidump". Y'all can also change this location if you lot choose to. Withal, if you do, keep in mind that most programs to troubleshoot the minidump logs are set up to look for this location by default. So it'south best to leave information technology equally it is. This besides translates to C:\Windows\Minidump.
How to Read the Minidump, See What Acquired Your BSOD
Now that the minidump is configured, you'll need to download an application that can read the file and provide useful data. A tool called BlueScreenView comes recommended for doing only this.
You can download BlueScreenView by going to the official website and selecting either the 32-bit or 64-bit version of the application.
After downloading the tool, you lot'll demand to excerpt it to a location, so it can be run.
Once the tool is extracted to a directory, double click the "BlueScreenView" icon to get started. BlueScreenView volition then look at the default minidump location and volition expect through the electric current logs that have been created. If you've experienced a number of issues or haven't removed older minidump files, you lot'll need to be mindful of the dates associated with the logs.
Using BlueScreenView to Empathise Minidump Files
When you first utilise BlueScreenView, it will provide you with several pieces of information and at first, information technology may seem disruptive. However, the format is straightforward and it does highlight the important information to get y'all started.
The files or applications that caused the crash will exist highlighted in red, giving you lot a good idea of where to start correcting the event.
In this screenshot, we tin encounter that on this specific minidump, at that place was an result detected that affected three files; dxgmms2.sys, ntoskrnl.exe and watchdog.sys.
Further on the upper panel, we tin meet in the right column that there's a section that tells us what acquired the crash. In this image, we tin come across that the watchdog.sys acquired the problem. This is a good starting point as you can now check Google or Bing, to meet how this could go a trouble and possible solutions.
Nosotros know that watchdog.sys is the potential cause, but what almost dxgmms2.sys and ntoskrnel.exe? As those were the afflicted files, we need to observe out what those are too. Then those will also need to be looked into. Doing a quick cheque on Google, we can see that dxgmms2.sys is related to the Windows DirectX drivers, while ntoskrnl.exe is the operating system kernel executable - responsible for keeping the operating system running.
Using this view of the Windows minidump file, we can deduce that the BSOD was likely caused by a graphics driver issue, which can typically exist corrected past installing a newer version of the driver or reinstalling the current commuter.
What If The Minidump File Shows A Hardware Fault?
While driver issues are commonly easily stock-still, a BSOD that is a result of failed hardware is a different story. Such an example is the FAULTY_HARDWARE_CORRUPTED_PAGE fault. Hither, you would however utilise an application such equally BlueSceenWindow to find the cause of the fault. Notwithstanding, when a hardware error occurs, in that location's non a magical fix that will correct this. For this specific error, we're going to say that the effect of this mistake was due to an installed retention module.
To figure out if this is the actual crusade, nosotros'd have to test the memory. There are several ways to practice this; using a hardware memory checker or an application. Seeing how most people don't accept access to a physical memory checker, we'll opt for the application road. Thankfully, Microsoft has included a memory diagnostics tool that has been included dating back to Windows 7. To use this, open upward a run prompt and type "mdsched".
Y'all'll take two options to choose from; Restart Now or Check for problems the next time you start my calculator. If you choose the beginning choice, be sure to save your work equally Windows will close out.
Once your computer restarts, the memory checker volition load and outset checking your retentivity. Depending on how much retentivity you lot have installed, the procedure tin take a while. While the exam is running, you lot'll come across a progress bar and an overall status. Any errors that may be encountered volition exist displayed under the status section.
Once the test is completed, the retention test will boot into Windows. If at that place are no errors, you can conclude that your retentivity is not at mistake.
Source: https://www.tomshardware.com/how-to/minidump-fix-blue-screen-of-death
0 Response to "Windows 10 How to Read Dump File"
Post a Comment