Mini Dump Files
Posted 21 August 2011 - 07:46 AM
Posted 24 August 2011 - 06:27 AM
Posted 24 August 2011 - 07:31 PM
Debugging Tools for Windows including WinDbg
Although most of the time its not necessary, you can download the Symbol packages as well as the Debugging Tools so you can read the Minidump logs easier. Once you've downloaded the Debugging Tools for the correct version of Windows and installed them, open the WinDbg program by following these steps.
1) Click on Start
2) Click on All Programs
3) Click on Debugging Tools for Windows group
4) Click on WinDbg to open
Look for the MODULE_NAME and IMAGE_NAME headings. This is the program that caused the error. Sometimes when it's a device driver it means that that device is causing the BSOD and by disabling it or updating the driver your system will run stable. If you don't know what device that name relates to then Google it.
Deciphering the Minidump Files
In the WinDbg program, click on File, then click on Open Crash Dump
Browse to the following directory on your hard drive and open a minidump log. The drive letter will be whichever drive you installed Windows on. In most cases, this is drive C.
After you open a minidump file in WinDbg, scroll to the bottom of the file. You should see a line that says Probably caused by:, followed by a filename. This is the problem file.
You might try this.
Posted 27 August 2011 - 10:22 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users