Suggestions

U

usasma

Retired Admin
Joined
Feb 20, 2012
Posts
2,126
Hi Mike and welcome back!

Could you add Windows 8.1 and Windows 10 in the "Old Driver After" tab?
Maybe also add something so that we can add custom OS's in the future?

The new version wiped out my store of old dumps. Any easy way to stop that in subsequent upgrades?
It also changed the a statement in the User kc commands It used to be !procdumpext.dpx; q, now it's !bugdump (but it appears to run the same command in the user2.txt file)
It left the niemiro extension entries alone.

Finally, it wiped out the path to kd.exe and although a search found it and it worked - it'd be more elegant if it checked for and used any existing path when upgrading (rather than clean installing).

Thanks again for this update!
 
usasma said:
Hi Mike and welcome back!

Could you add Windows 8.1 and Windows 10 in the "Old Driver After" tab?
Maybe also add something so that we can add custom OS's in the future?

The new version wiped out my store of old dumps. Any easy way to stop that in subsequent upgrades?
It also changed the a statement in the User kc commands It used to be !procdumpext.dpx; q, now it's !bugdump (but it appears to run the same command in the user2.txt file)
It left the niemiro extension entries alone.

Finally, it wiped out the path to kd.exe and although a search found it and it worked - it'd be more elegant if it checked for and used any existing path when upgrading (rather than clean installing).

Thanks again for this update!
Click to expand...

Your old dumps may be in your temp directory: C:\Users\usasma\AppData\Local\Temp\SysnativeBSODApps.zdnbak or type %TEMP%\SysnativeBSODApps.zdnbak into your Windows Explorer bar.

I'll look into why other settings changed. They should have remained... :huh:
 
Actually found the dumps here: C:\Sandbox\John\SysNativeBSODApp\user\current\AppData\Local\Temp
Didn't even know that I had a Sandbox!
EDIT: it looks like this was an old copy of the app when I installed sandboxie a long time ago - the dump files all date from 2013 and earlier :(

The one in C:\Users\John\AppData\Local\Temp only contained settings and the installer stuff

I was using Version 2.15.3 (the one that wouldn't run full dumps)
I understand that there was a Version 2.15.6 but I didn't discover this until last week :(
 
Last edited:
usasma said:
Actually found the dumps here: C:\Sandbox\John\SysNativeBSODApp\user\current\AppData\Local\Temp
Didn't even know that I had a Sandbox!
The one in C:\Users\John\AppData\Local\Temp only contained settings and the installer stuff

I was using Version 2.15.3 (the one that wouldn't run full dumps)
I understand that there was a Version 2.15.6 but I didn't discover this until last week :(
Click to expand...
Yeah, I never found the time to get 2.15.6 released as an official version with 2.7.2.1, so that's my fault. I'll also look into giving options for adding other OS support with driver dates. That will likely take a few weeks to put together since it involves a new interface for that tab.
 
usasma said:
Could you add Windows 8.1 and Windows 10 in the "Old Driver After" tab?
Maybe also add something so that we can add custom OS's in the future?
Click to expand...

So I'm looking at this request, and I'm seeing a tremendous undertaking with the current apps layout. We have the Old Driver After tab and the Excluded Drivers listings that would need a major overhaul to accommodate OS additions. It needs to be done since Microsoft isn't slowing down at all on their releases; if anything, they're releasing them more frequently now than ever. Mostly, I wanted to put this out there since it will probably take many weeks for me to make it happen. It's one of those design decisions that I deeply regret doing it the way I did it now...
 
Would it be possible to get the build numbers listed to make this request a bit easier to implement? I forgot how much the apps rely on which operating system the blue screen identifies in order to check driver dates against that system. This is way more work than I expected it to be. :-{

I know the following systems:

Windows 7: Build 7600
Windows 8: Build 9200
Windows 8.1: Build 9600
Windows 10: Build 98** (Build 10000 at release?)​


Any operating system (OS) that is added to the list for driver dates will need to be updated based on its build number since that is what the WinDBG kernel provides us. I will have to add some way for users to input both sets of information when adding a new OS.
 
Win7 will also show 7601
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505

Vista - 6000, 6001, and 6002 (I presume)
Built by: 6002.18533.x86fre.vistasp2_gdr.111025-0338
Built by: 6002.18607.amd64fre.vistasp2_gdr.120402-0336

XP -
Built by: 2600.xpsp_sp3_qfe.130704-0421
 
usasma said:
Win7 will also show 7601
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505

Vista - 6000, 6001, and 6002 (I presume)
Built by: 6002.18533.x86fre.vistasp2_gdr.111025-0338
Built by: 6002.18607.amd64fre.vistasp2_gdr.120402-0336

XP -
Built by: 2600.xpsp_sp3_qfe.130704-0421
Click to expand...

Yeah, I had 7601 for Windows 7 SP1, but it slipped my mind. I am pretty sure I also have the Vista/XP build numbers in the software. I am less familiar with the Windows 8, 8.1, and 10 releases since some of those numbers have changed through testing phases. I saw some calls with 8.1 having builds 9490, as well. Things have gotten confusing with build numbers and alpha/beta/technical previews.
 
You've pretty much got it. Windows 10 final is not and will never be 98** though. **Final** build numbers (minus service pack numbers) are always divisible by 16 since Windows Vista - so that space is left for the service pack numbers in the binary. See here: https://technet.microsoft.com/en-us/magazine/jj663498.aspx

The new windows 10 one will be 10000, 10.0.
 
niemiro said:
You've pretty much got it. Windows 10 final is not and will never be 98** though. **Final** build numbers (minus service pack numbers) are always divisible by 16 since Windows Vista - so that space is left for the service pack numbers in the binary. See here: https://technet.microsoft.com/en-us/magazine/jj663498.aspx

The new windows 10 one will be 10000, 10.0.
Click to expand...

Oh, guess the current build is 9926, so it would be 99** instead of 98**. I was going off memory with a week of lack of sleep. :banghead:
 
I went through my last 20 (approximately) memory dumps and found:

Windows 8: Build 9200 (only 2)
Windows 8.1: Build 9600 (about 17)
Windows 10: Build 9879 (only 1)
 

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

Back
Top