Sure, you can do a lot more than a simple !analyze -v with WinDbg, but if you're doing tech support and keep getting spammed by minidumps or just want to solve something quick and easy, you can use BlueScreenView.
Monday, November 02, 2009
Basically, you can see the drivers found on the stack at the time of the crash, a list of all drivers loaded in the kernel or XP style BSOD as it would appear in the crash. You can also create HTML reports to send to your clients.
The process is simple. You point BSV at a bunch of minidumps, you look at what driver is on the stack - then you upgrade it (oh, look, it's NVIDIA, time to upgrade). Or uninstall it (oh, look, I'm running some daemon tools thing pseudo-driver, to time remove it). Then you see if Windows stops crashing. If not, go to plan B - WinDbg, Driver Verifier, etc.