new BSOD app, can I get some help?

P

Patrick

Sysnative Staff
Joined
Jun 7, 2012
Posts
4,618
Alright, so I've been messing around every now & then with the BSOD app. Currently, I'm on the version in which there's a _jcgriff2_ folder in my User's directory, and inside that we'd replace the .exe every time there was a new version. Well I've had some gripes with it, such as having to constantly remove all of the unnecessary font types, etc.. and that slowed down analysis tons for me, so I put off using it. Well, this latest 0.9.7 release I can see adds a lot of great features, so I want to try it out again.. however, I am confused.

So first off, I downloaded 0.9.3, made a new folder and extracted the contents into that folder just to keep it tidy in case there were a lot of files. I read the readme and it said to run the install.bat to setup the directory structure. I ran it, it went quick, and then it closed. Now what? I'm assuming the folder it created is the folder named "SysnativeBSODApps" in my User directory, is that correct?

If so, what is my next step? I'm a little confused and I don't want to read over anything, so I'd appreciate if someone can dumb down the instructions for me, lol!

Thanks :)
 
Last edited:
Alright, if you have your parms all set up in the _jcgriff2_ folder, everything should load into the SysnativeBSODApps page. You can choose which files you want to output. To keep things simple, I would recommend starting only with the files that the jcgriff2 app output. Those files can be selected by scrolling down in the first list in the upper left of the first tab of the apps. You'll see a bunch of .txt files, and the ones that the _jcgriff2_ app used to output are the _99-debug.txt, _98-debug.txt, _97-debug.txt, _95-debug.txt, and _88-debug.txt.

It is probably best to leave all selected for the Output Options for now. The Formatting options probably won't affect you unless you are posting at Microsoft Answers or Technet and do not want the BBCode, i.e. bold and underling code, that is used for forums like Sysnative, SevenForums, TSF, etc. If you do post at a place that does not require BBCode, you can turn it off with the last option in that area. [B]test[/B] = test for instance is a BBCode method.

If you want to participate in updating the DRT with missing drivers, enter your username and the link for the thread you are helping in within the username: and Originating Post: areas respectively.

Symbols: is where you want to enter your symbols path. If you use local symbols, enter the path on your system to where they are stored. If you use online symbols, use the local path and online path via the SRV* path to the msdl symbols site. If you want to use a combination of the two, enter your local path on your system, i.e. c:\symbols

Symbos Option: If you want to use a combination of local and online symbols, type "online" in the box. That will cause the apps to download symbols using the first and last .dmp in the set you are analyzing. It will then use local symbols for all the .dmps; this works well 95% of the time and no symbol issues arise.

Symbos Option: If you want to use the symbols path that you typed into the Symbols: input, you can just leave the input to this area blank after filling in your Symbols path in the previous input.


The URL Path: is the path to the DRT individual site you want to link to, i.e. http://www.carrona.org/drivers/driver.php?id=

Link Seen by User: will be how you want the user to see the link. I used to just put the driver name here, in which case leaving it blank would suffice. If you want to have the default work, it will look like http://www.carrona.org/drivers/driver.php?id=<driver name>
or
https://www.sysnative.com/drivers/driver.php?id=<driver name>

You can enter your kd.exe path in the tab for kd.exe Path:
"C:\Program Files\Debugging Tools for Windows (x64)\kd.exe"​
or
"C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\kd.exe"​


The second tab is for formatting, i.e. FormatOptions. You can set up your header, footer, signature, 3rd party driver header, etc.

The Code Box Begin: and Code Box End: are probably where the font formatting areas are that you speak of, so check there first if you want to remove font formatting.


By the way, much of the information above can be found by clicking Help from the Help menu in the upper left portion of the apps.

SysnativeBSODApps.PNG
 
Last edited:
Thanks a lot for the quick responses! :)

Please forgive me though, still a little confused. The SysnatveBSODApps folder is in my Users folder, and I have downloaded the latest version (0.9.7) and replaced the .chm help file. Currently, the SysnativeBSODApps.exe is in my downloads folder, and it actually runs from there. I was able to see the window with all of the options you mentioned, Mike.. but I'm just confused on whether or not that .exe is actually supposed to go somewhere, or if I can just leave it. Would it be okay if I put that .exe into the SysnativeBSODApps folder, or do I have to leave it in downloads?

Regards,

Patrick
 
You can place SysnativeBSODApps.exe in any folder containing .dmps. One of the reasons for the new application design is to have more freedom as to where the apps are run from. You can run them from anywhere, but the output will be blank unless they are run from a directory that also contains .dmp or .DMP files.
 
Got it, so I'll just keep the .exe in my downloads folder as that's where I've always saved any .dmp's I analyze. I've also changed a few options, thanks for your explanations and help so far, Mike! If you still have the time, can you help me setup my Format Options page?

First off, I don't want any font changes, I'd just like to take all of that out.

* for reference, I am putting spaces between the bbcode to show what I mean *

For the header:

BSOD BUGCHECK SUMMARY[ /U]

For the footer:

I don't exactly understand what role the footer plays in this, mostly due to the notepad files being a little bit jumbled of code at first glance. Is it necessary, and if so, what should I put there since I don't want any font changes?

For the signature:

Currently, it's - .............................. parm $sig1

Code: 
[font=lucida console]

I have no idea what parm $sig1 means, do I have to leave that there, and should I removed the font bbcode part?

For the driver update header:

I guess I can change it from ^^ to  - 3rd party drivers that require update - or something like that?

For code box begin / end:

Do I leave that blank since I don't want the font changes?

Again, apologize for the what may be really stupid and silly question.. I just want to make sure before I do it that it'll work, because I don't know if some of these things are really important to the output of the dump files, etc.

Regards,

Patrick
 
You can change the parm $sig1 to anthing you want... even an empty file. I use it to put my signature at the end of the Summary info.

You can also blank out the CODE and FONT if you wish. It can always be put back again.

Any parm file changes must be done in the old jcgriff2 parms folder as they are copied to the new.
 
jcgriff2 said:
You can change the parm $sig1 to anthing you want... even an empty file. I use it to put my signature at the end of the Summary info.

You can also blank out the CODE and FONT if you wish. It can always be put back again.

Any parm file changes must be done in the old jcgriff2 parms folder as they are copied to the new.
Click to expand...

Or you can change those within the FormatOptions tab in the GUI. The program will determine where to save the new parms info based on your setup.
 
That's okay John. I think everyone is still learning it. That is why I am adding input anywhere I can to help the learning process go a little smoother. :smile9:
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top