How do you know which driver is responsible for the crash? It's all in kernel mode so everything is sharing the same address space. Even if you could determine that the crashed code belonged to a given driver, it's impossible to know whether that was responsible the crash, or some other driver called it with bad parameters. Even if you could get past all those problems, not loading a driver also comes with other problems. If the driver is required for some critical functionality, not loading the driver might cause other crashes. It also means you can disable an antivirus by getting to crash 3 times in a row.