Update: While the kd tool below will do the job of minidump analysis sufficiently, I believe the windbg tool is a better option because it will give you "probably cause" after it loads the minidump.

Once you start windbg with the preceding command line. Just go to File->Open Crash Dump  and then select the minidump you wish to analyze. Windbg is part of the Debugging Tools from Microsoft below.

 

1) Download and install the http://www.microsoft.com/whdc/devtools/debugging/default.mspx Debugging Tools from Microsoft
2) Locate your latest memory.dmp file- C:WINDOWS MinidumpMini081505-01.dmp or whatever
3) open a CMD prompt and cdprogram filesdebugging tools for windows
4) type the following stuff:
Code:

c:program filesdebugging tools>kd -z C:WINDOWS MinidumpMini081505-01.dmp
(it will spew a bunch)
kd> .logopen c:debuglog.txt
kd> .sympath srv*c:symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q

5) You now have a debuglog.txt in c:, open it in notepad and post the content here