Suggestion(s) [color driver output based on timestamp]

jcgriff2 · Oct 25, 2012

Thanks, Mike.

It was quite a few versions ago that the ms-drivers txt file caused me some trouble. 1 file is great!

AceInfinity · Oct 25, 2012

Pretty easy with the .NET BCL Interfaces. You could have an IComparer, or IEqualityComparer to evaluate the dates, and sort or color based on the results. Interfaces would be the ideal way to go for validation here. I'd build an entire class for it to boot, then you work off of that class.

writhziden · Oct 25, 2012

Not sure I follow. Remember, I'm new to the .NET framework, despite appearances that may suggest otherwise.

Laxer · Oct 26, 2012

I wasn't saying a new DB I was saying a new table or column for that need.

Anyway, if you need me to make any tweaks to the DRT let me know.

writhziden · Oct 26, 2012

All capability added as requested: BETA Sysnative BSOD Processing Apps 2.2.2.4

writhziden · Oct 26, 2012

Laxer said:
I wasn't saying a new DB I was saying a new table or column for that need.

Anyway, if you need me to make any tweaks to the DRT let me know.

Thanks Geoff. I don't see any reason yet, but maybe when 8 becomes more popular and we need more BSOD descriptions for 8 and 7, we can look into it further.

usasma · Oct 26, 2012

72 total that say "known issues with Win7"

Holy Smokes!!! I missed a few!

Just FYI - most of those 72 are sptd.sys variants and we've discussed removing them from the DRT. I'll leave them alone until we decide.

See this topic for some examples: https://www.sysnative.com/forums/sh...hat-consistently-cause-BSOD-s-in-many-systems
But with the other searches that you did, I'm going to have to add "BSOD" to them in the DRT in order to make them consistent.

I searched for "known" and for "issues" and replaced a 10 or 12.
Did see that the descriptions of BSOD issues will need some fine tuning (date and OS affected)

jcgriff2 · Oct 26, 2012

The magic of CTRL-F in IE !!

You're right, just checked - they are the sp??.sys drivers, but they are not the dynamically allocated ones AFAIK. Those usually begin with "A".

writhziden · Oct 26, 2012

With the latest version of the apps, you will need to go into the Excluded Drivers tab and put an x in each list item under the Windows OS that the driver date applies to. Here is how mine appears:

[IMG3]https://www.sysnative.com/forums/attachment.php?attachmentid=2284&d=1351254960[/IMG3]

usasma · Oct 26, 2012

From the list here: https://www.sysnative.com/forums/sh...hat-consistently-cause-BSOD-s-in-many-systems
I'd say that they all have problems with Win7. I don't note any problems with Vista or XP at this time.
Win8 remains to be seen, but I'll keep the Win7 one's for Win8 until we see if the BSOD's stop.

Still trying to figure out how to add wireless USB network adapters to the list.

usasma · Oct 29, 2012

I'm getting confused with all the changes, I hope that this is the right topic for this question.

This driver is highlighted RED in the template.txt
ASACPI.sys Wed Jul 15 23:31:29 2009 (4A5E9F11)

I have it listed in the Excluded drivers section using the above date
How do I get the app to not mark it in RED, but continue to mark earlier versions in RED?

writhziden · Oct 29, 2012

What you have done should work. There may be a bug in the apps or something in the settings that is interfering.

Would you mind uploading a .zdn file of your settings that are not working along with the .dmp(s) you had problems with?

I can probably determine where the problem is with those files.

usasma · Oct 29, 2012

Mistake #1 - date in Excluded drivers is actually May 13, 2009 (I thought that I remembered it from looking at it earlier)

Excluded drivers list looks funny - there are 2 numbers surrounded by curly brackets in each column - one for the driver and one for the following driver.

writhziden · Oct 29, 2012

Sounds like the excluded drivers list was corrupted somewhere along the way. The easiest way for that to happen is if an entry is deleted and the line break is deleted with it. The line break deletion is not always detectable, so then when the apps run the next time and load, they think the {#} and following driver are on the same line.

Do you need help cleaning up the corruption?

usasma · Oct 30, 2012

Thanks! We lost power at 5pm EDT yesterday and don't know when it'll be back on (it's about 5 am now). I'll reply back as soon as I am able

writhziden · Oct 30, 2012

No worries. I'm re-designing the apps so the corruption cannot occur again.

Hope the power comes back fast this time for you.

Search

Search

Suggestion(s) [color driver output based on timestamp]

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

AceInfinity

Emeritus, Contributor

writhziden

Administrator, .NET/UWP Developer

Laxer

Co-Founder
Senior Administrator

writhziden

Administrator, .NET/UWP Developer

writhziden

Administrator, .NET/UWP Developer

usasma

Retired Admin

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

writhziden

Administrator, .NET/UWP Developer

usasma

Retired Admin

usasma

Retired Admin

writhziden

Administrator, .NET/UWP Developer

usasma

Retired Admin

writhziden

Administrator, .NET/UWP Developer

usasma

Retired Admin

writhziden

Administrator, .NET/UWP Developer

Suggestion(s) [color driver output based on timestamp]

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Emeritus, Contributor

Administrator, .NET/UWP Developer

Co-FounderSenior Administrator

Administrator, .NET/UWP Developer

Administrator, .NET/UWP Developer

Retired Admin

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Administrator, .NET/UWP Developer

Retired Admin

Retired Admin

Administrator, .NET/UWP Developer

Retired Admin

Administrator, .NET/UWP Developer

Retired Admin

Administrator, .NET/UWP Developer

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder
Senior Administrator

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)