Solved Windows does not create a memory dump file when BSOD

Windows does not create a memory dump file when a Stop error occurs in Windows 8 or Windows Server 2012

Consider the following scenario:

• You connect a storage device that is controlled by Microsoft Multipath I/O (MPIO) to a computer that is running Window 8 or Windows Server 2012.
• You configure Windows to generate a complete memory dump file or kernel memory dump file when a Stop error occurs.
• You configure Windows to save the memory dump file to the storage device.
• A Stop error occurs.

In this scenario, Windows may not generate the memory dump file.

Windows does not create a memory dump file when a Stop error occurs in Windows 8 or Windows Server 2012

I think the numerical list is a better fit for the scenario described above, because it's a sequence.

Given the thread title, it's worth covering the old scenarios as well (and the bullet list is on purpose here):

• The paging file is too small (fix: set the system managed size)
• Not enough free space on the system drive to write the full dump (fix: change the dump writing location or configure small dumps to be written)
• BSOD occurs before the paging file is open, e.g. during driver initialization at boot
• System components involved in dump creation are corrupted
• OS hangs or sudden reboots caused by faulty hardware, e.g. CPU overheating