Comment Re:BSoD was an indicator (Score 1) 20
BSoD was telling you what was going on, but they made it difficult to understand what to do.
The BSoD only ever gave you enough information to tell you what driver crashed. Or a simple error code. It still does. That hasn't changed.
Error logs and crash reports could tell you a lot if you knew how to get to them. But since MS didnt make it easy or help the end user, it turned into its an MS problem and MS sucks.
Be careful what you wish for. Error logs and the tools are great and all, but if a user is unable to go read on the MSDN Docs how to debug something they will not have a hope in hell of understanding the debug output either. Kernel panics are no better in this regard either. The average user (heck the average poweruser) has no hope in hell of understanding what went wrong.
I think the problem is legacy, back when windows didn't have meaningful isolation between the kernel and drivers in userland it was trivial to bring down the system (hell Bill Gates did it live in front of a TV audience by plugging in a printer). That can most definitely be blamed on the OS, but that hasn't been the case now for 2 decades+.