6.2.9200.16384 - I remember that this version is slower, but AFAIK this is the latest one.
When running SysnativeBSODApps - kd.exe, but when using my tool - cdb.exe (from PowerDbg)
I do use your app and love this tool. Whenever I can, I write my suggestions (vide my previous posts). I knew that I have to wait for the output from the tool, but few days ago I had to analyze ~20 dumps having not to much time, so I had to do some analysis 'manually' and decided to see if I can speed up a bit by parallelizing the app. This is why I created this simple app... I didn't want to upset you, sorry for that.
Forget about PowerDbg. I used it, because it was the simplest solution for me and I don't think it's better in any way comparing to your approach.
You may try my app, where I changed a bit PowerDbg.psm1 and provided some sample .dmps. Steps:
1. Download the tool [CLICK] and unpack to any folder (but please, full path shouldn't contain spaces);
2. Run PowerShell (x86) (and (x64)) and Set-ExecutionPolicy Unrestricted;
3. If you don't have _NT_SYMBOL_PATH, the symbols will be downloaded to the \symbols directory - first run should be longer.
4. I hardcoded x64 version of the tools (Tools\DbgTools\x64), but feel free to put there x86 files if you use x86 OS;
5. Run cmd, cd to the dir containing the app and simply run the DumpInterpreter.exe.
The tool should create 20 threads and spawn cdb (6.2.9200.16384) for each dump and collect results in .dmp.txt files. Please, treat this app as a PoC and test tool, so exceptions may appear. The app is written in .NET, so feel free to use any .NET disasm to see what's going on inside.
m.g.
