WinDbg 6.11.1.402 versus WinDbg 6.2.8229.0 Huge Time Disparity

[writhziden]

6.11.0001.402 and 6.11.0001.404 run the six .dmps from my local cache in ~7.288 seconds.

Read More:

7.221 seconds to run the kd command on .dmp 1 of 6
10.14 seconds to run the kd command on .dmp 2 of 6
7.393 seconds to run the kd command on .dmp 3 of 6
4.334 seconds to run the kd command on .dmp 4 of 6
3.126 seconds to run the kd command on .dmp 5 of 6
7.319 seconds to run the kd command on .dmp 6 of 6

6.2.8229.0 and 6.2.9200.xxxx run the six .dmps from my local cache in ~39.533 seconds

Read More:

1.282 seconds to run the kd command on .dmp 1 of 6
1.285 seconds to run the kd command on .dmp 2 of 6
1.239 seconds to run the kd command on .dmp 3 of 6
1.264 seconds to run the kd command on .dmp 4 of 6
0.849 seconds to run the kd command on .dmp 5 of 6
1.369 seconds to run the kd command on .dmp 6 of 6

6.12.0002.633 runs the six .dmps from my local cache in ~26.407 seconds

Read More:

5.428 seconds to run the kd command on .dmp 1 of 6
5.92 seconds to run the kd command on .dmp 2 of 6
5.196 seconds to run the kd command on .dmp 3 of 6
2.142 seconds to run the kd command on .dmp 4 of 6
2.366 seconds to run the kd command on .dmp 5 of 6
5.355 seconds to run the kd command on .dmp 6 of 6

Commands used: "!analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q"


Most of the problem seems to stem from getting the module timestamps. If I run with lm, 6.2.xxxx.xxxx runs each .dmp in ~3 seconds. If I run with lmt, 6.2.xxxx.xxxx runs each .dmp in ~8 seconds.

Even 3 seconds is about 4-6 times longer than it runs in 6.11.xxxx.xxx...

I cannot find a way to optimize this. Why does 6.2.xxxx.xxxx take so much longer to run than 6.11.0001.402 and 6.11.0001.404 ?

 

[jcgriff2]

A good question.

I have noticed the time differences for a while now and 1st thought it was due to slower DSL Internet speed - downloading symbols, but obviously not.

 

[zigzag3143]

On some DMPS it is even worse. To get any sort of benchmark I have picked a random set of DMPs and use them for all comparisons. Ever try running a full memory DMP?

 

[writhziden]

I had not tried a full .DMP; I'll have to see if I can find my .DMP from when I was running a trial of Avast! on my system and it kept crashing due to scanning a backup of my Application Data junction.

 

[usasma]

Just my 2¢ - but things are whizzing along for me (kd.exe version 6.2.8400) now that the Symbols and Symbols Options fields have those check boxes!

I'd suggest that we post a "stickie" with a standard group of minidumps - and a kernel dump or two (depends on what John can allow to be stored).
Also will need a standard group of settings so that all are using the exact same options (when testing) - but will be able to easily revert to any customized settings that we may have.

That way we can use them as "reference" groups - and I'd like to see some with the win32k.sys issues also, as I'm still trying to get something done for that.

 

[writhziden]

Are you talking about a standard group of settings in the apps, or in WinDbg?

If we want a standard set of settings in the apps, that can be easily accomplished by saving a .zdn file of your settings through File -> Save As and uploading it to a sticky. Not saying you have to do it; just letting you and others know how it would be done.

 

[usasma]

I'm looking at a standard set - the apps, WinDbg, the dump files, etc.
Can you upload a .zdn file of the default settings (I've changed mine too much already)?

 

[writhziden]

defaultNoLoss.zdn will not overwrite your headers, footers, signatures, or template files with the defaults.

default.zdn will overwrite all files with the defaults.


Make sure to save your current settings to a .zdn file if you want to revert back to your current use of the apps.

 

[jcgriff2]

It may be beneficial to list system specs here as well.

[table="width: 888, class: wikigrid, align: left"]
[TR]
[TD]

User​

[/TD]
[TD]

OS​

[/TD]
[TD]

Windbg/
KD Version​

[/TD]
[TD]

System Mfr
Model Num​

[/TD]
[TD]

CPU​

[/TD]
[TD]

RAM​

[/TD]
[TD]

HDD​

[/TD]
[TD][/TD]
[/TR]
[TR]
[TD]JaidynM[/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]jcgriff2
[/TD]
[TD]Windows 7 x64 SP1
[/TD]
[TD]6.11, 6.12, 6.2
[/TD]
[TD]HP dv7-1020us
[/TD]
[TD]Intel P7350
Core2 Duo @ 2 GHz
[/TD]
[TD]4 GB
DDR2
[/TD]
[TD]500 GB SATA
@ 5400 rpm
[/TD]
[TD][/TD]
[/TR]
[TR]
[TD]Shintaro[/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]usasma
[/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]writhziden
[/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]zigzag3143
[/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]

[/TABLE]

 

[writhziden]

[TABLE="class: wikigrid, width: 888, align: left"]
[TR]
[TD]

User​

[/TD]
[TD]

OS​

[/TD]
[TD]

Windbg/
KD Version​

[/TD]
[TD]

System Mfr
Model Num​

[/TD]
[TD]

CPU​

[/TD]
[TD]

RAM​

[/TD]
[TD]

HDD​

[/TD]
[TD][/TD]
[/TR]
[TR]
[TD]JaidynM[/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]jcgriff2[/TD]
[TD]Windows 7 x64 SP1[/TD]
[TD]6.11, 6.12, 6.2[/TD]
[TD]HP dv7-1020us[/TD]
[TD]Intel P7350
Core2 Duo @ 2 GHz[/TD]
[TD]4 GB
DDR2[/TD]
[TD]500 GB SATA
@ 5400 rpm[/TD]
[TD][/TD]
[/TR]
[TR]
[TD]Shintaro[/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]usasma[/TD]
[TD]Windows 8 Release Preview x64[/TD]
[TD]6.2.8400.0[/TD]
[TD]Asus P6T Deluxe v2 mobo[/TD]
[TD]Intel Core i7-920 (1st gen)
@ 2.67GHz
[/TD]
[TD]12 gB DDR2[/TD]
[TD]W-D Velociraptor (300 gB SATA) @ 10,000 rpm[/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]Windows 7 x64 SP1[/TD]
[TD]6.11, 6.12, 6.2[/TD]
[TD]VAIO
VPCF232FX/B[/TD]
[TD]Intel Core i7-2670QM
CPU @ 2.20GHz[/TD]
[TD]8 GB
DDR3[/TD]
[TD]500 GB
SATA
@ 7200 rpm[/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]zigzag3143[/TD]
[TD]Win 8 PRO RTM
[/TD]
[TD]6.2.9200.16384
[/TD]
[TD]HP DV-7 4010TX
[/TD]
[TD]Intel Core i7-920 (1st gen)
@ 2.67GHz
[/TD]
[TD]8 Gigs
[/TD]
[TD]500@7200
32gig SSD
[/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[/TABLE]

 

[usasma]

Edited my info into writhziden's post....
Will be updating to Win8 RTM as soon as I get some free time!

 

[zigzag3143]

Also added specs into writhzidens post. Similar results to what he has experienced.

 

[jcgriff2]

I simply listed a few names when creating the table; many are missing.

Please feel free to provide system info & we'll add it.

[TABLE="class: wikigrid, width: 555, align: left"]
[TR]
[TD]

User​

[/TD]
[TD]

OS​

[/TD]
[TD]

Windbg/
KD Version​

[/TD]
[TD]

System Mfr
Model Num​

[/TD]
[TD]

CPU​

[/TD]
[TD]

RAM​

[/TD]
[TD]

HDD​

[/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[/TABLE]

https://www.sysnative.com/forums/sh...e-Time-Disparity?p=25906&viewfull=1#post25906

Thanks!

 

[usasma]

Suggest that we stabilize testing on a certain version of the app.

Then, let's set up a procedure for testing.
Y'know:

Step 1 - Save your settings to a zdn file
Step 2 - Import writhziden's default zdn file
Step 3 - Run these dumps (groups of 10, 30, and 100?) <attachment goes here>
Step 4 - Post back with times for 10, 30, and 100 dumps in seconds
Step 5 - Import your saved zdn file to return to your usual work style

 

[writhziden]

I would suggest standardizing with BETA: Sysnative BSOD Apps 2.0.0.6 since all the save and load functionality is working properly by that version.

   Note

The select all / deselect all misses the last three items in Output Options in all of the versions released to this point. This will be fixed in a later release.

A link to 10, 30, and 100 as well as a kernel .DMP: Mike P's SkyDrive Public Folder.

 

[writhziden]

Procedure:

1. Place the .dmps in the folder with the SysnativeBSODApps.exe application file.
2. Run SysnativeBSODApps.exe
3. When finished, hit OK to exit out; do not record the time given by the apps since it will be erroneous due to error/warning messages that pop up.
4. Open outputDmps\<this set's timestamp>\SysnativeBSODApps\dmpOptions\timeBetweenRuns.txt
5. Scroll down or search for "seconds to runDmps()".
6. Copy and paste that line into your table.

I will be adding my table to this post when I am finished running all five versions I have to test.

Also, you may want to run through all the .dmps once with one of the versions to get the symbols set up for the test run.

[TABLE="width: 1139"]
[TR]
[TD][TABLE="class: grid, width: 1000, align: left"]
[TR]
[TD]Username[/TD]
[TD]Windbg/kd.exe Version[/TD]
[TD]10 dmps[/TD]
[TD]30 dmps[/TD]
[TD]100 dmps[/TD]
[TD]1 Kernel DMP[/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]6.11.0001.402[/TD]
[TD]63.662 seconds to runDmps()[/TD]
[TD]157.306 seconds to runDmps()[/TD]
[TD]225.593 seconds to runDmps()[/TD]
[TD]3.944 seconds to runDmps()[/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]6.11.0001.404[/TD]
[TD]61.571 seconds to runDmps()[/TD]
[TD]150.951 seconds to runDmps()[/TD]
[TD]227.752 seconds to runDmps()[/TD]
[TD]2.549 seconds to runDmps()[/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]6.12.0002.633[/TD]
[TD]108.673 seconds to runDmps()[/TD]
[TD]361.733 seconds to runDmps()[/TD]
[TD]754.292 seconds to runDmps()[/TD]
[TD]3.487 seconds to runDmps()[/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]6.2.8229.0[/TD]
[TD]109.81 seconds to runDmps()[/TD]
[TD]350.586 seconds to runDmps()[/TD]
[TD]797.359 seconds to runDmps()[/TD]
[TD]4.14 seconds to runDmps()[/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]6.2.9200.16384[/TD]
[TD]116.966 seconds to runDmps()[/TD]
[TD]350.712 seconds to runDmps()[/TD]
[TD]778.028 seconds to runDmps()[/TD]
[TD]4.812 seconds to runDmps()[/TD]
[/TR]
[/TABLE]
[/TD]
[/TR]
[/TABLE]



Another interesting one: This is with the following kd command:

kd -c "q" -z "<pathToDmpFile>"

All it does is open the .dmp through the kernel debugger to see if it is a .dmp; no real commands are run other than to quit after opening the .dmp, but it is much slower in 6.2 than previous versions...
[TABLE="width: 1139"]
[TR]
[TD][TABLE="class: grid, width: 1000, align: left"]
[TR]
[TD]Username[/TD]
[TD]Windbg/kd.exe Version[/TD]
[TD]10 dmps[/TD]
[TD]30 dmps[/TD]
[TD]100 dmps[/TD]
[TD]1 Kernel DMP[/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]6.11.0001.402[/TD]
[TD]1.994 seconds to getDmpsList()[/TD]
[TD]1.621 seconds to getDmpsList()[/TD]
[TD]1.578 seconds to getDmpsList()[/TD]
[TD]1.648 seconds to getDmpsList()[/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]6.11.0001.404[/TD]
[TD]1.826 seconds to getDmpsList()[/TD]
[TD]1.651 seconds to getDmpsList()[/TD]
[TD]1.939 seconds to getDmpsList()[/TD]
[TD]1.815 seconds to getDmpsList()[/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]6.12.0002.633[/TD]
[TD]2.826 seconds to getDmpsList()[/TD]
[TD]1.782 seconds to getDmpsList()[/TD]
[TD]2.168 seconds to getDmpsList()[/TD]
[TD]2.26 seconds to getDmpsList()[/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]6.2.8229.0[/TD]
[TD]14.402 seconds to getDmpsList()[/TD]
[TD]14.731 seconds to getDmpsList()[/TD]
[TD]15.126 seconds to getDmpsList()[/TD]
[TD]12.896 seconds to getDmpsList()[/TD]
[/TR]
[TR]
[TD]writhziden[/TD]
[TD]6.2.9200.16384[/TD]
[TD]12.514 seconds to getDmpsList()[/TD]
[TD]11.826 seconds to getDmpsList()[/TD]
[TD]12.701 seconds to getDmpsList()[/TD]
[TD]11.953 seconds to getDmpsList()[/TD]
[/TR]
[/TABLE]
[/TD]
[/TR]
[/TABLE]

 

[Tekno Venus]

I have typed up an Excel spreadsheet to use. It has areas for user system specs and for dmp processing time. This excel sheet can be filtered and sorted to make life easier at the end. I will let Mike decide what app version and settings to use. If you need the file in another format, (open office, Excel 2003, .csv etc,) please ask.

Stephen

 

[Tekno Venus]

And Mike just posted some other steps as I composed my post... Feel free to use my table in your steps Mike.

 

[niemiro]

Just in case I do any testing. I started off with some profiling yesterday, although I have yet to track down anything concrete.

niemiro
Windows 7 x64 SP1
6.11.1.404, 6.12, 6.2.8229.0
Self built
Intel Core i7 2600k @ 3.4GHz
16GB DDR3 1600MHz
64GB Crucial M4 SSD
1TB Western Digital Caviar Black (Sata III)

 

[writhziden]

Can we re-open this discussion? I have been running 6.2 due to using an older system that requires me to use 32-bit Windows, and I do not have a 32-bit version of 6.11 to run.

6.2 has been driving me nuts.

1. it sees "symbol file could not be found for win32k.sys" so the apps think the symbols are wrong, but never find the right ones because the win32k.sys issue is always there even using online symbols. I much prefer the message that the timestamp could not be verified since that implies the downloaded .dmp has an issue rather than the local symbols are missing in most cases. I cannot change the apps because then they would fail for 0x124 BugChecks if symbol files could not be found.
   
   
2. The good .dmps still take ~twice as long, and the win32k.sys issue causes them to take up to 13 times as long... Ludicrous...
   
   • Why is the newest version of the kernel debugger so much slower than the old 6.11 version?
     
     
   • Why does it take so much longer to sort the driver list by timestamp?
     
     
   • Why does it take so long just to open a .dmp to see if it is a .dmp without running a command?
   
   All questions that need to be asked...