Sysnative BSOD Scripts

[jcgriff2]

The Sysnative BSOD Scripts mentioned throughout this site and elsewhere on the Internet, automates much of the mundane Windbg process.

It is rather common for users seeking BSOD help to submit numerous BSOD minidumps, sometimes as many as 50 (Windows 7 default limit).

The Sysnative BSOD Scripts are used by BSOD Analysts at many different forums and easily allows them to process all dump files instead of just a select few dumps via Windbg.

The scripts incorporate the Driver Reference Table (DRT) created by John Carrona, Microsoft MVP, (usasma) to aid in the identifcation and isolation (separate reporting) of 3rd party drivers.

Here is an example of the Sysnative BSOD Scripts in action, processing 6 BSOD minidumps in under 30 seconds:

Best viewed at 720 px. (change the setting)

Each new screen you see opening = 1 dump file being processed.

The current Sysnative BSOD Scripts have undergone many changes and upgrades since I began developing them using batch and VBS in 2008. Several months ago, Richard (niemiro) took over as Project Director and transformed the aging and difficult-to-work-with batch/ VBS modules into C++

For further information on the Sysnative BSOD Scripts or to obtain them, please send me a PM.

 

[jcgriff2]

08-31-2012

Finally, what everyone has been waiting for: Version 2.0.0.0 is ready for release.

This may be confusing to some. Why 2.0.0.0 after 0.9.9.x? Why not 1.0.0.0?

A little background as to why the change was made from 0.9.9.x to 2.0.0.0 instead of 1.0.0.0:

Going back to the jcgriff2 app, the original scripts were developed by John Griffith (jcgriff2), and those scripts ran through .bat and .VBS scripts. Those were designed to obtain relevant information from the kernel debugger analyses. The relevant info chosen included that which John used in his blue screen analyses with the forums he worked in. Richard (niemiro), at John's behest, ported those scripts into a C++ application with the intent that they be available to all analysts. He began and did much of the important development so users had options for the output. Those were developed and used by many here up to version 1.2.0.0.

As some know, I was developing my own app with similar designs. I started the app more as a hobby, and then it became a necessity due to restrictions placed on the ability to obtain the app here on the forums I was initially working on to help users with BSODs. My app grew due to the necessity to train others in BSOD analysis. Eventually, I left those forums and joined here. Some were still using my app here, but from my perspective, it was nowhere near as effective as what John and Richard had accomplished here. There were some features that were different that people liked, though, so I spent a weekend rebuilding it to make it faster, more efficient, and to incorporate more options into it. I went as far as to say the redesign was version 2.0 of my own app (although, it probably still was closer to version 1.0 of the jcgriff2 app).

Due to the features people liked in my app and the features that people liked in the jcgriff2 app, John, Richard, and I discussed a merging of the two apps and called them the Sysnative BSOD Apps. I designed a graphical interface for it, and the version number was dropped down to 0.9.0 since it was in a testing stage. Richard brought up the point that the new apps with all the options and the graphical interface were beyond the 1.2.0.0 jcgriff2 app, so after testing, we both agreed upon the 2.0.0.0 version number. And that is how we end up with the 2.0.0 version number.

 

[jcgriff2]

Current version - https://www.sysnative.com/forums/bs...e-blue-screen-of-death-processing-apps-2.html