“My computer just had a BSOD (Blue Screen Of Death), and I wrote down the stop information.
While I was writing that, it was dumping the contents of the memory into a file, and that file was called “MEMORY.DMP”

Is there any way I can read that, and see what caused my computer to stop?”

The Answer is YES.
The BSOD is always the result of a critical system error and Windows can no longer keep on running when that occur and instead crashes. About 80 percent of all BSODs occur because of bad drivers. Hardware problems such as corrupt memory modules or hard drive generally also produce a BSOD every now and then.
The Memory.dmp file created by BSOD contains useful information that may help identify why your computer has stopped unexpectedly. It can be read using a Microsoft Debugging tool.

Debugging Tool is a part of Microsoft Windows SDK (Software Development Kit) and can be downloaded from microsoft download center
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=8279

How to install Debugging Tool and Debug a memory.dmp file

System Requirements:

* Dot Net Framework 4 is required
* Disk Space Requirement
Debugging Tool Only requires approximately 80 MB
Debugging Tool with default SDK installation requires approximately 800 MB
Debugging Tool with Complete SDK installation requires approximately 1.5 GB

Installation:

* First Install Dot Net Framework 4
* Now to install Debugging tool run downloaded SDK installer “winsdk_web.exe”
* Follow the instructions and select the components as per your requirment

Start Debugging:

* Create directories “Symbols” and “Dump”
* Copy the memory.dmp file in C:\Dump\ and leave the C:\Symbols\ directory empty.
* Copy I386 directory of Same OS which dump file is to be debug to C drive or you can insert its CD.
* Open command prompt and type
cd C:\Program Files\Debugging Tools for Windows (x86)

* Now finally To start debugging type
windbg -y srv*C:\Symbols*http://msdl.microsoft.com/download/symbols -i C:\I386 -z C:\Dump\MEMORY.DMP

It shows Bugcheck Analysis after debugging and the “Problem caused by”.

For Example
*******************************************************************************
*                                                                                                                                                                                   *
*                        Bugcheck Analysis                                                                                                                     *
*                                                                                                                                                                                   *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000207668, fffff8800904b030, 0}

Probably caused by : win32k.sys ( win32k!GreDeleteWnd+14 )

Followup: MachineOwner
———

2: kd> !analyze -v
*******************************************************************************
*                                                                                                                                                                                   *
*                        Bugcheck Analysis                                                                                                                     *
*                                                                                                                                                                                   *
*******************************************************************************