The minidump files are usually located in C:/Windows/Minidump/*.dmp and the full memory dump in C:/Windows/MEMORY.dmp. Something should be logged in your Event log as well, including the STOP code and parameters. It's important to call out that for various reasons, a dump won't be created even if you explicitly tell it to.
I have a couple of minidump files generated by blue screen crashes on a Windows Server 2008 R2 x64 machine. I have installed the debugging tools and I am able to look at the contents of these files.
Thanks! That is pretty a pretty good answer, but I don't think the minidump contains this info. I do get kd> promt on the file, but I don't get anything like that info in !vm. That might be because it end the output with "ProcessCommitUsage could not be calculated". I'll look into procdump also.
Windbg / minidump - how do I get a process list with memory use
You can use Out-Minidump function for PowerShell: Out-Minidump writes a process dump file with all process memory to disk. This is similar to running procdump.exe with the '-ma' switch. Basic usage: Enable PowerShell script execution via Set-ExecutionPolicy cmdlet. It should be Bypass, Unrestricted or RemoteSigned. Details: If you (or a helpful admin) runs Set-ExecutionPolicy as administrator ...
Those minidump files just indicate different memory errors in that program, but nothing about your system, are there any normal minidump files in C:\Windows\Minidump
It can't be only the folder C:\Windows\Minidump because in my case it tells me that it would delete 5.65 GB, but the Minidump Folder only contains some KB. Where are the files located which will be deleted?