I wish get your recommendations for central analysis of BSODs software. I have a bunch of dumps which I wish to analyze and understand the root cause for the system crash.
Which tools/applications could I use?
Nirsoft Bluescreenview is a nice tool to show the content of a BSOD the same way it was displayed on the screen. This is often sufficient to find out the data needed for googling a problem (like the STOP code etc.). This is fine if your task is mainly of IT administrative nature.
The central factor here is that it will collect all BSODs of one PC automatically.
The downside is: you can't do an in-depth analysis. It may be a starting point to find the right BSOD to be later analyzed in WinDbg (as mentioned before).
Windows kernel crash dumps can be analyzed with WinDbg (pronounce "windebug", "windbag" or "win-dee-bee-gee").
Regarding the central analysis of crashes, you can e.g. run it on a server and write scripts (MSDN) to automate the analysis for you. However, note that there are dozens of potential causes and writing a good script may take some time. The
!analyze -v command already does a lot for you.
Assuming that you're mainly interested in debugging your own software (as opposed to doing Microsoft a favor and analyzing their issues), you have to set up your own symbol server (Stack Overflow).
WinDbg is very powerful and probably the only tool up-to-date with the latest versions of Microsoft Windows, since Microsoft itself uses it for debugging the OS.
Becoming familiar with WinDbg is a hard task, though. It took me years to profoundly answer questions about it - and I do user mode debugging only. Maybe a kernel driver developer can become familiar with WinDbg a bit faster.