It'll take a lot of explaining to see why we use this rather than other methods.
The first is experience. Experience is needed to filter the drivers and see what may/may not be a problem.
For example, the MBfilt64.sys from Realtek is older, yet it's known to be a good driver despite the date. The only way that I know this is from having run hundreds/thousands of memory dumps - and have seen that the driver isn't causing the crashes (based on feedback from users). There's also numerous problems with a driver that starts with MpKsl - and it may date anywhere from 1989 to 2015. It turns out, after much research, that this is a dynamically generated driver from Windows Defender - and the date appears to be either a glitch or a faulty construct. I've been able to verify this on several systems that are having BSOD's - but find that this isn't the problem (after disabling Windows Defender). Finally, I'm aware that the LMI module is the latest version - yet I still don't have sufficient data to convince me that it's a good driver. As such, I still recommend uninstalling it "just in case". This decision is also based on the ease of which one can get another copy of LogMeIn to reinstall if they so desire (after having tested the system without it).
I am the owner of the carrona DRT database. The intent of the DRT (Driver Reference Table) is simply to help people find out where to get the latest drivers from - not to fix drivers.
If you're able to look up the drivers (at the manufacturer's website), then you can find the latest version at the website of the manufacturer.
BUT, what if the drivers have been modified by other manufacturer's/developers? Most of the major OEM's modify drivers for their own uses.
We started the DRT back around 2009 and have had many people involved in the development. While some of the older helpers still have access to the DRT, there's only 3 people that are currently involved in maintaining the DRT. And of those 3, I am the most active - and I don't have a bunch of free time. I've had to cut back on my other analysis task (such as comparing all of the Windows drivers from XP to W10. I stopped doing this after W10 first came out - but the table still resides at http://www.carrona.org/dvrcomp.html if you're interested.
Right now I'm limited to adding drivers:
- that are submitted by users (via the Suggest A Driver page)
- that are any drivers found frequently in memory dumps
- that are Windows drivers found in memory dumps (I do ALL that I find):
I also do the BSOD Index: http://www.carrona.org/bsodindx.html
Shortly after the Creators Update came out - we found a problem with the Windows debugger that affected my system.
As such, I had to revert to the previous version of the debugger.
But to find the new versions of the Windows drivers, the new error lists, and the new BSOD's, I have to install the latest version of the Windows Software and Driver kits (which would break my debugger again).
So I tried to install the Fall Creators Update in a VM. And, much to my dismay, I couldn't make it work on my system
After much work I was finally able to get the VM to work and install the Fall Creators Update.
At this point I decided to limit myself to updating the BSOD's and the other error code listings. The Windows drivers were growing faster than I could keep up with - and not all of them were installed on my system. In view of this, I gave up updating the other pages with Windows drivers - leaving the DRT to hold those that we find in memory dumps.
Right now I'm trying to find the time to update the error tables that are linked to on this page: http://www.carrona.org/bsod.html
and to add all the information for the 14 new BSOD's to the http://www.carrona.org/bsodindx.html page.
Well, I could keep typing about this stuff for hours more - but I hope that I got the gist of it across.
Good luck to you!