WinDbg 6.11.1.402 versus WinDbg 6.2.8229.0 Huge Time Disparity

Are you using kd or dumpchk to check files?

IDK if it makes a difference or not - time.
 
jcgriff2 said:
Are you using kd or dumpchk to check files?

IDK if it makes a difference or not - time.
Click to expand...

kd. Doubt dumpchk would be faster, but I'll check.

EDIT: 2 seconds faster for less info, still takes 12 seconds per .dmp with online symbols. If I remember correctly, 6.11 takes 3-4 seconds per .dmp with online symbols with my internet.


jcgriff2 said:
niemiro said:
Do you want a copy of x86 WinDBG 6.11?

You can get it here: http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi
Click to expand...


Thank you! :thumbsup2:

How did you know that?
Click to expand...

Yes, Richard, how did you find that? THANK YOU!!!

I was able to find more with a Google search thanks to your genius: http://www.google.com/#q=site:msdl....24fb5637e33ac3&bpcl=35466521&biw=1440&bih=666
 
Last edited:
Found this WER file from 8/14 - Windbg 6.2.8229.0 crashed

Just listing the WER file here as it gives us a glimpse at the other drivers used -

Read More:
 
I'll revive this discussion a minute. Found WinDbg 6.11 x64 and downloaded it. Wow, it's much faster. Ran two sets of identical dumps with identical settings with the app version 2.4.8.0. Significant difference. This needs to be investigated further. I've attached the output folders so you can see the difference and the settings, dumps used etc.

6.11 X64 -
Code: 
0.005 seconds to EnableVisualStyles()
0 seconds to SetCompatibleTextRenderingDefault(false)
1.274 seconds to get today's date
17.112 seconds to Run(gcnew Form1())
0 seconds to create output object
0.364 seconds to setUpDirectoryStructure()
0.432 seconds to getDmpOptions()

5.545 seconds to downloadDumpFile()
0.172 seconds to cleanUpDriverList()
0.082 seconds to getDriverList()
0.004 seconds to prepare the kd command 1 of 17
2.067 seconds to run the kd command on .dmp 1 of 17
0.002 seconds to check the kd output for module errors 1 of 17
0.012 seconds to save the kd output 1 of 17
2.087 seconds to run Kernel Debug on .dmp 1 of 17
0.005 seconds to prepare the kd command 2 of 17
1.331 seconds to run the kd command on .dmp 2 of 17
0.002 seconds to check the kd output for module errors 2 of 17
0.011 seconds to save the kd output 2 of 17
1.351 seconds to run Kernel Debug on .dmp 2 of 17
0.005 seconds to prepare the kd command 3 of 17
1.214 seconds to run the kd command on .dmp 3 of 17
0.002 seconds to check the kd output for module errors 3 of 17
0.012 seconds to save the kd output 3 of 17
1.235 seconds to run Kernel Debug on .dmp 3 of 17
0.005 seconds to prepare the kd command 4 of 17
1.204 seconds to run the kd command on .dmp 4 of 17
0.001 seconds to check the kd output for module errors 4 of 17
0.011 seconds to save the kd output 4 of 17
1.223 seconds to run Kernel Debug on .dmp 4 of 17
0.005 seconds to prepare the kd command 5 of 17
1.213 seconds to run the kd command on .dmp 5 of 17
0.002 seconds to check the kd output for module errors 5 of 17
0.012 seconds to save the kd output 5 of 17
1.233 seconds to run Kernel Debug on .dmp 5 of 17
0.005 seconds to prepare the kd command 6 of 17
1.239 seconds to run the kd command on .dmp 6 of 17
0.001 seconds to check the kd output for module errors 6 of 17
0.012 seconds to save the kd output 6 of 17
1.259 seconds to run Kernel Debug on .dmp 6 of 17
0.005 seconds to prepare the kd command 7 of 17
1.198 seconds to run the kd command on .dmp 7 of 17
0.001 seconds to check the kd output for module errors 7 of 17
0.011 seconds to save the kd output 7 of 17
1.218 seconds to run Kernel Debug on .dmp 7 of 17
0.005 seconds to prepare the kd command 8 of 17
1.196 seconds to run the kd command on .dmp 8 of 17
0.001 seconds to check the kd output for module errors 8 of 17
0.011 seconds to save the kd output 8 of 17
1.216 seconds to run Kernel Debug on .dmp 8 of 17
0.005 seconds to prepare the kd command 9 of 17
1.206 seconds to run the kd command on .dmp 9 of 17
0.002 seconds to check the kd output for module errors 9 of 17
0.012 seconds to save the kd output 9 of 17
1.225 seconds to run Kernel Debug on .dmp 9 of 17
0.005 seconds to prepare the kd command 10 of 17
1.196 seconds to run the kd command on .dmp 10 of 17
0.002 seconds to check the kd output for module errors 10 of 17
0.011 seconds to save the kd output 10 of 17
1.215 seconds to run Kernel Debug on .dmp 10 of 17
0.005 seconds to prepare the kd command 11 of 17
1.19 seconds to run the kd command on .dmp 11 of 17
0.002 seconds to check the kd output for module errors 11 of 17
0.012 seconds to save the kd output 11 of 17
1.211 seconds to run Kernel Debug on .dmp 11 of 17
0.005 seconds to prepare the kd command 12 of 17
1.196 seconds to run the kd command on .dmp 12 of 17
0.002 seconds to check the kd output for module errors 12 of 17
0.011 seconds to save the kd output 12 of 17
1.216 seconds to run Kernel Debug on .dmp 12 of 17
0.005 seconds to prepare the kd command 13 of 17
1.261 seconds to run the kd command on .dmp 13 of 17
0.002 seconds to check the kd output for module errors 13 of 17
0.011 seconds to save the kd output 13 of 17
1.28 seconds to run Kernel Debug on .dmp 13 of 17
0.005 seconds to prepare the kd command 14 of 17
1.187 seconds to run the kd command on .dmp 14 of 17
0.002 seconds to check the kd output for module errors 14 of 17
0.012 seconds to save the kd output 14 of 17
1.206 seconds to run Kernel Debug on .dmp 14 of 17
0.005 seconds to prepare the kd command 15 of 17
1.201 seconds to run the kd command on .dmp 15 of 17
0.001 seconds to check the kd output for module errors 15 of 17
0.011 seconds to save the kd output 15 of 17
1.22 seconds to run Kernel Debug on .dmp 15 of 17
0.005 seconds to prepare the kd command 16 of 17
1.178 seconds to run the kd command on .dmp 16 of 17
0.002 seconds to check the kd output for module errors 16 of 17
0.012 seconds to save the kd output 16 of 17
1.198 seconds to run Kernel Debug on .dmp 16 of 17
0.005 seconds to prepare the kd command 17 of 17
1.196 seconds to run the kd command on .dmp 17 of 17
0.002 seconds to check the kd output for module errors 17 of 17
0.011 seconds to save the kd output 17 of 17
1.216 seconds to run Kernel Debug on .dmp 17 of 17
0.206 seconds to getImportantInfo()
0.113 seconds to getDriverInfo()
0.068 seconds to outputFullDriverList()
0.535 seconds to get third party info and DRT info
0.001 seconds to store 3rd party info and DRT info
0.548 seconds to outputThirdPartyNames()
0.015 seconds to outputThirdPartyDates()
0.748 seconds to getDriverLists()
29.16 seconds to getInputData()
0.074 seconds to outputCSV()
0.05 seconds to outputThirdPartyDriversDate()
0.051 seconds to outputImportantInfo()
0.107 seconds to outputMissingFromDRT()
0.063 seconds to getEightyEight()
0.086 seconds to outputTemplate()
0.093 seconds to outputNinetyNine()
0.049 seconds to outputNinetyFive()
0.095 seconds to outputNinetyEight()
0.051 seconds to outputEightyEight()

WinDbg 6.2.9200
Code: 
0.004 seconds to EnableVisualStyles()
0.001 seconds to SetCompatibleTextRenderingDefault(false)
1.213 seconds to get today's date
38.262 seconds to Run(gcnew Form1())
0 seconds to create output object
0.378 seconds to setUpDirectoryStructure()
0.473 seconds to getDmpOptions()

2.853 seconds to downloadDumpFile()
0.177 seconds to cleanUpDriverList()
0.08 seconds to getDriverList()
0.005 seconds to prepare the kd command 1 of 17
9.747 seconds to run the kd command on .dmp 1 of 17
0.002 seconds to check the kd output for module errors 1 of 17
0.012 seconds to save the kd output 1 of 17
9.767 seconds to run Kernel Debug on .dmp 1 of 17
0.005 seconds to prepare the kd command 2 of 17
8.973 seconds to run the kd command on .dmp 2 of 17
0.001 seconds to check the kd output for module errors 2 of 17
0.012 seconds to save the kd output 2 of 17
8.993 seconds to run Kernel Debug on .dmp 2 of 17
0.005 seconds to prepare the kd command 3 of 17
8.899 seconds to run the kd command on .dmp 3 of 17
0.002 seconds to check the kd output for module errors 3 of 17
0.012 seconds to save the kd output 3 of 17
8.919 seconds to run Kernel Debug on .dmp 3 of 17
0.005 seconds to prepare the kd command 4 of 17
8.6 seconds to run the kd command on .dmp 4 of 17
0.002 seconds to check the kd output for module errors 4 of 17
0.011 seconds to save the kd output 4 of 17
8.62 seconds to run Kernel Debug on .dmp 4 of 17
0.006 seconds to prepare the kd command 5 of 17
8.241 seconds to run the kd command on .dmp 5 of 17
0.002 seconds to check the kd output for module errors 5 of 17
0.012 seconds to save the kd output 5 of 17
8.262 seconds to run Kernel Debug on .dmp 5 of 17
0.006 seconds to prepare the kd command 6 of 17
6.708 seconds to run the kd command on .dmp 6 of 17
0.002 seconds to check the kd output for module errors 6 of 17
0.011 seconds to save the kd output 6 of 17
6.729 seconds to run Kernel Debug on .dmp 6 of 17
0.005 seconds to prepare the kd command 7 of 17
6.926 seconds to run the kd command on .dmp 7 of 17
0.002 seconds to check the kd output for module errors 7 of 17
0.012 seconds to save the kd output 7 of 17
6.947 seconds to run Kernel Debug on .dmp 7 of 17
0.007 seconds to prepare the kd command 8 of 17
6.753 seconds to run the kd command on .dmp 8 of 17
0.002 seconds to check the kd output for module errors 8 of 17
0.011 seconds to save the kd output 8 of 17
6.775 seconds to run Kernel Debug on .dmp 8 of 17
0.005 seconds to prepare the kd command 9 of 17
7.21 seconds to run the kd command on .dmp 9 of 17
0.002 seconds to check the kd output for module errors 9 of 17
0.011 seconds to save the kd output 9 of 17
7.229 seconds to run Kernel Debug on .dmp 9 of 17
0.005 seconds to prepare the kd command 10 of 17
7.415 seconds to run the kd command on .dmp 10 of 17
0.002 seconds to check the kd output for module errors 10 of 17
0.012 seconds to save the kd output 10 of 17
7.435 seconds to run Kernel Debug on .dmp 10 of 17
0.005 seconds to prepare the kd command 11 of 17
7.678 seconds to run the kd command on .dmp 11 of 17
0.002 seconds to check the kd output for module errors 11 of 17
0.013 seconds to save the kd output 11 of 17
7.699 seconds to run Kernel Debug on .dmp 11 of 17
0.004 seconds to prepare the kd command 12 of 17
7.715 seconds to run the kd command on .dmp 12 of 17
0.002 seconds to check the kd output for module errors 12 of 17
0.012 seconds to save the kd output 12 of 17
7.735 seconds to run Kernel Debug on .dmp 12 of 17
0.005 seconds to prepare the kd command 13 of 17
8.448 seconds to run the kd command on .dmp 13 of 17
0.001 seconds to check the kd output for module errors 13 of 17
0.012 seconds to save the kd output 13 of 17
8.468 seconds to run Kernel Debug on .dmp 13 of 17
0.005 seconds to prepare the kd command 14 of 17
7.753 seconds to run the kd command on .dmp 14 of 17
0.002 seconds to check the kd output for module errors 14 of 17
0.012 seconds to save the kd output 14 of 17
7.773 seconds to run Kernel Debug on .dmp 14 of 17
0.006 seconds to prepare the kd command 15 of 17
7.288 seconds to run the kd command on .dmp 15 of 17
0.001 seconds to check the kd output for module errors 15 of 17
0.012 seconds to save the kd output 15 of 17
7.31 seconds to run Kernel Debug on .dmp 15 of 17
0.005 seconds to prepare the kd command 16 of 17
6.608 seconds to run the kd command on .dmp 16 of 17
0.002 seconds to check the kd output for module errors 16 of 17
0.012 seconds to save the kd output 16 of 17
6.629 seconds to run Kernel Debug on .dmp 16 of 17
0.005 seconds to prepare the kd command 17 of 17
6.479 seconds to run the kd command on .dmp 17 of 17
0.003 seconds to check the kd output for module errors 17 of 17
0.016 seconds to save the kd output 17 of 17
6.507 seconds to run Kernel Debug on .dmp 17 of 17
0.266 seconds to getImportantInfo()
0.138 seconds to getDriverInfo()
0.071 seconds to outputFullDriverList()
0.537 seconds to get third party info and DRT info
0.001 seconds to store 3rd party info and DRT info
0.553 seconds to outputThirdPartyNames()
0.015 seconds to outputThirdPartyDates()
0.782 seconds to getDriverLists()
136.57 seconds to getInputData()
0.07 seconds to outputCSV()
0.05 seconds to outputThirdPartyDriversDate()
0.101 seconds to outputImportantInfo()
0.065 seconds to outputMissingFromDRT()
0.069 seconds to getEightyEight()
0.078 seconds to outputTemplate()
0.094 seconds to outputNinetyNine()
0.048 seconds to outputNinetyFive()
0.097 seconds to outputNinetyEight()
0.051 seconds to outputEightyEight()
 

Attachments

Right, just emailed the WinDBG Product Team about this. They keep asking for bug reports, so I asked about this in the same place. It isn't exactly a bug, and I didn't classify it as such at this stage, just sent them an email enquiring about it. I used lots of the evidence posted here, so thank you all for that.

We shall see...
 
niemiro said:
Right, just emailed the WinDBG Product Team about this. They keep asking for bug reports, so I asked about this in the same place. It isn't exactly a bug, and I didn't classify it as such at this stage, just sent them an email enquiring about it. I used lots of the evidence posted here, so thank you all for that.

We shall see...
Click to expand...

Thanks Richard, good idea!

We'll see, only time will tell....
 
Thanks Stephen and Richard.

I'm running 6.2 more now due to the links to carrona.org BugCheck info being more robust with it, so I would love to see the kernel debugger developers speed it up.
 
I also notice that runDmps time output is missing... I have fixed that in the next release now. :-}
 
jcgriff2 said:
Just to note:

6.11 did not list storahci.sys as probable cause - https://www.sysnative.com/forums/showthread.php/4584-Watchdog-Errors?p=34104#post34104

6.11 -
Code: 
Probably caused by : [COLOR=#ff0000]ntkrnlmp.exe[/COLOR] ( nt! ?? ::FNODOBFM::`string'+13ca8 )

6.2.8229 -
Code: 
Probably caused by : [COLOR=#ff0000]storahci.sys[/COLOR] ( storahci!P_NotRunning+e7 )
Click to expand...

Yes.... 6.11 doesn't do a good job on the new 0x133 bugcheck.

I'll let them know about that later (and some of the other issues we have had on 6.2, such as symbol issues also).

So far, however, a deadly silence on my email to them about speed. Not even a confirmation. I think I got the right email address.

Anyway, it has only been a few days. No need to be concerned yet.
 

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

Back
Top