I assumed that because you were dignosing BSOD events you were aware of the event and how to deal with it. No insult was insinuated or intended.
The Nirsoft program like most things to diagnose errors is intended for use by someone with a knowledge of what you are looking for in the first place. As far as I am aware there is no Click and resolve system currently or historically other than "Dr Watson" an XP based program that not only told you of the event but also the cause, the files affected and so on.
Most BSOD events I have seen as a repair technician over the years as Mr Dog has said are usually events triggered by out of date driver packages or mismanged installation of the packages. Other common places are dodgy Registry keys acting on a bad insert point in some code in a file.
BSOD itself (now discontnued) is intended to lock up your machine due to a bad crash of a file that doesnt work well with the KERNEL part of the system (Kernel being the heart of the running code for your computer) Generally on the screen is a Reference number, taking a picture of it with your phone then tracing the reference number is the only way I know of that will reveal the problem in detail. On rare occasions in my knowledge I have seen a particular file named on the page, but generally the BSOD is a bad driver system compatability with your machine, althoguh thanks to Microsoft this is usually something one of their wonderful updates tends to bring to the for as we all know, Microsaft never make Mistakes (That they will admit too)
If you are getting a BSOD happening regularly, get a picture or write deown the reference number and we will assist in sorting it out with you.