urbanriot A driver that makes a system unstable can manifest itself in ways that define themselves as software issues.
To us it may look that way, but depending on the nature of the brokenness of the driver, Microsoft is privy to far more granular information, by virtue of the fact that they can access all of the state of the system, either in real-time or as part of the crash clean-up. I said from the start that it wouldn’t be perfect, but there are some cases where it is so obviously the fault of a particular driver, that they wouldn’t have to do much work to name and shame the vendor and/or associated driver.
Of course there is always the issue of I-know-what-I’m-doing users force-installing incorrect drivers, etc., and that is difficult to work around. However, with proper handling, they could work to point out some of those cases, too. Really, it’s surprising that a company as large as Microsoft has allowed it to get into, and remain in, this state over such a long period of time. If they’d spend a little more time on core security and stability features, rather than unwanted, borderline-useless gimmicks, we’d all be much better off. How much work, time (and therefore money) have been lost to unanticipated system trouble since the introduction of Windows 95? I’m sure the numbers are staggering, yet they haven’t done nearly as much as they could have to create a more resilient system.