Driver issues - Windows drivers showing up in 3rd party driver output

[usasma]

This has been happening for a while, but being lazy I didn't look into it until now (as I've started updating the DRT with the Creators Update (1703) Windows drivers).
And, I have to wonder about why/how Microsoft is changing the details of their drivers - as I still use the old driverlist.exe file to get the data on the drivers.

I also can't recall if I added the Anniversary Update (1607) Windows drivers to the DRT or not - gonna have to go back and check that also.



Several of the Windows drivers show strange date/timestamps. This is the most common one that is also listed in the DRT:

intelppm.sys ***** Invalid 2007 Invalid 2007 Invalid

intelppm.sys is in the DRT, but this driver is showing in the 3rd party driver output of the BSOD Processing App
An example post is here: Mutliple BSOD errors. - Windows Crashes, BSOD, and Hangs Help and Support



The SleepStudyHelper.sys driver is the same - but I haven't added it to the DRT yet.

There are others, but they are all similar to the intellppm.sys problem - and I'll be updating the DRT with the 1703 Windows drivers in the next day or so.



Is there an easy way to fix this so they don't show in the 3rd Party Drivers list?
TIA - and thanks for all the hard work that got us to this point!

 

[jcgriff2]

intelppm.sys is in the DRT, but this driver is showing in the 3rd party driver output of the BSOD Processing App
An example post is here: Mutliple BSOD errors. - Windows Crashes, BSOD, and Hangs Help and Support

intelppm.sys is listed in the DRT as a 3rd party driver - Driver Reference Table - intelppm.sys

I have no idea what they're doing with the timestamps. I've seen 1970, 2037, and many more. Since we don't use them in the DRT, timestamp should not be a problem.

 

[writhziden]

This has been happening for a while, but being lazy I didn't look into it until now (as I've started updating the DRT with the Creators Update (1703) Windows drivers).
And, I have to wonder about why/how Microsoft is changing the details of their drivers - as I still use the old driverlist.exe file to get the data on the drivers.

I also can't recall if I added the Anniversary Update (1607) Windows drivers to the DRT or not - gonna have to go back and check that also.



Several of the Windows drivers show strange date/timestamps. This is the most common one that is also listed in the DRT:

intelppm.sys ***** Invalid 2007 Invalid 2007 Invalid

intelppm.sys is in the DRT, but this driver is showing in the 3rd party driver output of the BSOD Processing App
An example post is here: Mutliple BSOD errors. - Windows Crashes, BSOD, and Hangs Help and Support



The SleepStudyHelper.sys driver is the same - but I haven't added it to the DRT yet.

There are others, but they are all similar to the intellppm.sys problem - and I'll be updating the DRT with the 1703 Windows drivers in the next day or so.



Is there an easy way to fix this so they don't show in the 3rd Party Drivers list?
TIA - and thanks for all the hard work that got us to this point!

Add it to your excluded drivers in the app if you don't want it to show up.

There is nothing I can do about timestamps. Those are an issue with WinDbg and its kernel debugger, the server cache for driver symbols, or both. I know it's not an issue with the actual .sys files since they seem to show up correctly through the syslist text file and msinfo32 data.

 

[usasma]

Brain Cramp! Doh! Sorry, I assumed that intelppm.sys was a Windows driver. My mistake!
Thanks for pointing out that it's not a Windows driver and thanks for taking the time to look at this.

I'm not worried about the timestamps themselves on Windows drivers - there's also several that have dates in the 1980's
And the "fix" for old Windows drivers is simply to run Windows Update.
I blame these things on the rush to get new versions out. In doing so they have less time for QC (Quality Control).