By default when a BSOD occurs you will get a memory dump normally located in “C:\Windows\” and aptley named “memory.dmp”. Unless any settings are changed by a user or policy it should be default reside there, to note they are normally over-written or could be placed in “C:\WINDOWS\ Minidump\” after every BSOD.
To analyse a BSOD you need to install the “Windows Debugging Tools” located here simply download whatever version is current (as it covers nearly all current versions of windows at the time of this post XP onwards to Win8). It will say you need 300+mb for the install however going through the install you will get a check list of what you want to install simply just select debugging tools for windows.
You now need to open CMD (as an admin) and “CD” to this path (assuming you used the default path) so “cd” > “C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\”.
now type the following “kd –z C:\Windows\memory.dmp” followed by “.logopen c:\debuglog.txt” you are now aquiring the symbols package from microsoft to help with “decrypting” the mem dump so type “.sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols”
Now finally run this command to close the “C:\debuglog.txt” and you should get a readable debug log “.reload;!analyze -v;r;kv;lmnt;.logclose;q”
You should now be able to read the log and sift through the data (which their normally is alot) however it should point you in the direction of the cause of the issue, which is usually a driver issue.
Credit goes to “I found a fix” and “weblogsasp”
Further Reading
Crash Dump Analysis
Microsoft support Article 315263
Windows 7 Forums BSOD Posting Instructions
Major Geeks Debugging BSOD
Using WinDbg