Don’t bother looking at any dump files derived from a BSOD. You won’t make heads or tails of it anyway because the dumps are formatted for use by Microsoft and are basically not readable by the average user.
In addition, trapping a BSOD is simply a matter of pressing F8 during the bootup process at the proper time and selecting the option to pause when BSOD’s are displayed. I have this set up on my system(s) just in case, but I don’t go into those boot options (F8) often enough to remember exactly how it’s phrased. Nevertheless, it’s there among the options and if you select it, then any time that you get a BSOD it will stop (pause) until you press the appropriate key to continue. Yes, it may be related to drivers, but it usually related to the application of drivers by your system that either produce an error or are corrupted/incompatible with the hardware to which they are linked. The most common BSOD is a memory issue. The next most common BSOD usually has to do with audio devices and/or video issues.
Regardless, there’s no point in belaboring trying to figure out what caused your BSOD unless it is persistent and unresolvable by normal reboot. There may be software that makes a dump file more intelligible, but the dump is a proprietary Microsoft form and no matter what it tells you, unless you understand the relationship between the error and your system, it’s worthless anyway. The best way of dealing with a persistent BSOD is to invoke the pause and write down the error, then go to Microsoft’s support webpages and/or to the MSDN (Microsoft Developers Network) pages and look up the error. You can spin your wheels for days trying to figure out how to resolve a BSOD and I’m not sure that for the average user is worth it.Chucker2013-11-23 09:42:35