?Bug - missing driver in Template/98, present in 99

I'll take a look toward the end of the week if nothing comes up in that time. I'm currently recovering from surgery.
 
Holy smokes! There's a lot of surgery going around!
I hope that you all are doing well and that you recover rapidly and comfortably after the surgery.

I'm able to access the link.
 
usasma said:
Ref: Blue screen after every full night shutdown. | Page 8 | Windows Forum

I ran the latest memory dump with the latest version of the BSOD app.

xusb22.sys shows up in the list in lmtsmn output in the 99 file - yet it's not present in the driver output of the Template or the 98 files
Unfortunately, this driver is blamed for the BSOD :(
Click to expand...

Alright, this is strange. The driver showed up in your previous template analysis, #119, but it did not show up in the template analysis I did of the 18th of May dump file.

Update: I found the issue and should have a new version uploaded shortly.
 
Last edited:
I just got around to installing the latest version and the requested changes work great!
Unfortunately, it appears that the app now highlights all drivers in red in my template

I've turned the red off for now, but it still lists a lot of drivers in the <3rd Party Drivers><date><descriptions><timestamp>
I'm still working on trying to figure out why they are there (some are BSOD prone, others are old, but there's a few that are newer (but may be just outside the screening dates).
 
Looks like I've also been deprived of the ability to edit posts :(

Oh well, a bit of further work suggests that this is actually the fix you implemented - and the system actually scanning for outdated drivers.
I had gotten used to not seeing older drivers in the results and didn't even know that that was a problem!
I'll check the next time I run a few dumps - as most of my work is W10 right now (so many drivers are "old")
 

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

Back
Top