[SOLVED] How to test?

P

Patrick

Sysnative Staff
Joined
Jun 7, 2012
Posts
4,618
Hi guys!

I have set everything up following the instructions, but I want to make sure it's working as intended. How would I go about testing to see if this works? Thanks :)

Also, please forgive my complete ignorance, but I am slightly confused as to what this script does in the first place. John told me not to be afraid to ask questions, so I shall start here :wave:
 
Hello!

Please do keep asking questions! Any and all questions always welcome!

As a test, you could run these dumps here: https://www.sysnative.com/forums/sh...y-processor-quot?p=11167&viewfull=1#post11167

and post the logs, and either John or I will take a quick look to ensure everything is in working order.

As for what the scripts are for, the scripts basically run every single dump given to it, and produce a nice summary output. This means that you only very rarely have to open WinDBG.

The summary outputs provide the information which we believe is most helpful. Many 3rd party drivers can be picked from here. A summary can also be posted to the OP.

$99_dbug.txt saves the entire output, so that you can reference all information, like call stacks, if you so wish/need to.

It basically speeds up and automates the process.

Finally, the program checks against the Driver Reference Table, and generates lists of URLs, including the highlighting in red of old drivers to help you very quickly get OPs updating older drivers.

John knows much more about how the scripts are used than I do, and has been using them for years. I am posting what I do know here and now in the hope that it may help.

Please do not hesitate to ask any more questions.

Richard
 
Hi,

First of all, thank you very much for the explanation. I figured it made our lives easier in one way or another, but I wasn't sure of the specifics. Alright, so I execute $99_dbug from the Kernel folder, typed in my username, and then right click pasted that thread URL. After that, here's what happens:

example.jpg

There's nothing in __processed_BSOD_dumps__ or a log in the main Kernel directory. Not sure why, but I have a feeling this may be directory related or the way in which I extracted the original ZIP attached to the instructions post. In the instructions post, you mention various times a jcgriff2 folder before getting to the other two folders (dbug and Parms_Editor). I right clicked the ZIP with WinRAR, right clicked, selected extract to: C:/Users/BSOD/

After that, there are two folders in my User directory, dbug and Parms_Editor. They are not inside of a jcgriff2 folder.

Oh, and just to give you a little more information, I did download the updated $99_dbug and replaced it.
 
Hello again :)

The directory structure is nearly right. It is that _jcgriff2_ folder which has gone missing, which you noticed yourself. I will see what I can do to improve the instructions on that extraction process.

Can you please create an extra _jcgriff2_ folder, giving a total path of C:\Users\BSOD\_jcgriff2_\dbug\__jcgriff2_parms__ \...\

The _jcgriff2_ folder should contain dbug and Parms_Editor folder, and the dbug folder should contain __Kernel__ and __jcgriff2_parms__ folders.

One other thing. The program is not able to download the dumps for you, given a thread URL. The thread URL is simply used for uploading files to the Driver Reference Table. If you do not upload any drivers to the Driver Reference Table, the thread URL is never used.

To this end, you must manually extract the .dmp files (and any other .txt files from a jcgriff2 report if you want) into the __Kernel__ directory - the same directory $99_dbug.exe resides in.

Once some dump files are in there, the program should work fine.

You are not the first to misunderstand my instructions in this way, which shows that my instructions are inadequate! I intended top correct this earlier, but I completely forgot...

I hope this helps,

Richard
 
Holy crap! THIS SCRIPT IS AMAZING! I literally just run the script and that's it, it's almost doing my analysis job for me. It puts the dumps into such a NEAT stack for easy reference in a topic rather than copying and pasting the entire dump. It even goes ahead and literally takes all 3rd party drivers and links them too. All I have to do is take a look after and give my advice. WOW!

WOW!

WOW!

Wow... just wow. This saves... so much time. Just.. wow.

Thank you for taking the time to explain, it was exactly what we thought it was and all I needed to do was create the jcgriff2 folder.
 
I am very glad that you like them! Thank you for such nice complements. I will pass them on to all who have helped create these scripts. I am sure they will grealy appreciate it.

Any more questions, problems, help or feature requests, bug fixes etc., please don't hesitate to ask.
 

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

Back
Top