Memory.dmp file is not being created when your computer encounters a STOP message:

There are several reasons why the Memory.dmp file is not being created when your computer encounters a STOP message:


The Memory.dmp file already exists and the option Overwrite Any Existing File (found in Control Panel System) is not selected. It is a good idea to leave this box checked and to move or copy the current Memory.dmp file.
The paging file on the boot drive is not large enough. To use the "Write Debugging Information To" feature to obtain a complete memory dump file, the paging file on the boot drive must be at least as large as physical memory + 1 MB. When you create a kernel memory dump file, the file is usually around one-third the size of the physical memory on the system. Of course, this quantity will vary, depending on your circumstances.
The paging file is not on the %systemroot% partition. When the STOP error occurs, the system crash dump is written out to the pagefile on the root of the %systemroot% drive.
There is not room for the Memory.dmp file in the path specified in Control Panel for writing the memory dump.
It is possible that the SCSI controller is bad or the system crash is caused by a bad SCSI controller board.
If you specify a non-existent path, a dump file will not be written. For example, if you specify the path as C:\Dumpfiles\Memory.dmp and no C:\Dumpfiles folder exists, a dump file will not be written.
Minimum requirement enable a complete memory dump on a computer that has more than 2 GB of RAM:


Important We recommend that you consider the following information before you enable a complete memory dump on a computer that has more than 2 GB of RAM:
It can take a substantial amount of time to create a complete memory dump on a computer with more than 2 GB of RAM. This can reduce overall system uptime.
A complete memory dump on a computer with more than 2 GB of RAM requires a very large system partition because of the paging file size requirements. If you select this option, you must have a paging file on the boot volume that is sufficiently large to hold all the physical RAM plus 1 MB. The extra megabyte is required for a complete memory dump file because Windows writes a header in addition to dumping the memory contents. The header contains a crash dump signature and specifies the values of some kernel variables. The header information does not require a full megabyte of space, but Windows sizes your paging file in increments of megabytes.
A complete memory dump file is rarely required. In most cases, a kernel memory dump is sufficient for analysis. Please consult your escalation channel before enabling the complete memory dump in a production environment.
If your computer has more than 4 GB of RAM, you must configure the Boot.ini file to start the computer with the Physical Address Extension (/PAE) switch.
Complete Memory Dump option not avaliable in Windows Server 2003, Windows XP 64-bit Edition Version 2003, Windows XP Professional x64 Edition, Windows Vista
The only options available under Write Debugging Information in the Startup and Recovery dialog box in System Properties are Small Memory Dump (64 KB) and Kernel Memory Dump. The Complete Memory Dump option is not available. If you set the CrashDumpEnabled DWORD value to 1 in the registry to enable a complete memory dump on a computer that is running Windows XP, or Windows 2000, the memory dump may become corrupted when your computer stops unexpectedly.
loadTOCNode(2, 'resolution');



To specify that you want to use a complete memory dump file by modifying the registry, set the CrashDumpEnabled DWORD value to 1. For example, type the following information at a command prompt, and then press ENTER:
wmic recoveros set DebugInfoType = 1
To specify that you want to use the D:\Dump\Mem.dmp file as your memory dump file by modifying the registry, set the DumpFile expandable string value to D:\Dump\Mem.dmp. For example, type the following information at a command prompt, and then press ENTER:
wmic recoveros set DebugFilePath = D:\Dump\Mem.dmp
To specify that you do not want to overwrite any previous kernel or complete memory dump files by modifying the registry, set the Overwrite DWORD value to 0. For example, type the following information at a command prompt, and then press ENTER:
wmic recoveros set OverwriteExistingDebugFile = 0
Note The Write Debugging Information section of the Startup and Recovery dialog box in System Properties continues to list only Small Memory Dump (64 KB) and Kernel Memory Dump after you enable a complete memory dump by using these methods. The Complete Memory Dump option remains unavailable, and you must use the Windows registry to configure complete memory dump options.