99 times out of 100, I use BlueScreenView to analyze BSODs. It's a great program for initial analysis.
If I need to go more in depth, I use windb from here https://msdn.microsoft.com/en-us/windows/hardware/hh852365
However, when you run windbg, you get errors about missing symbols. I read about the fix for the symbold problem here: http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx
The fix for the symbol error is to type this command at the bottom of the window (part to type in bold):
0: kd> !symfix
then save the workspace and close and reopen windbg
Now you get no symbol errors when you open the minidump. Now, you can get get more detail about the BSOD with this command:
0: kd> !analyze -v