Windows Server 2019: Crash dump not generated on dynamic NVme disk. Volmgr 45, Volmgr 46 errors

Question

Павел Павел 1

Good day. There is Windows Server 2019 Standard (1809). All updates installed.

2 Samsung Enterprise PM9A3 NVMe drives installed

After adding a mirror in disk management, 2 error messages are generated on each reboot

Volmgr 45 The system could not sucessfully load the crash dump driver.

and 1 message

Volmgr 46 Crash dump initialization failed

Memory dump file is not generated

Free space 240 GB on drive C:

From what has been tested:

memory
chkdsk c: /f /r
sfc /scannow (Windows Resource Protection found no integrity violations.)
DISM /Online /Cleanup-Image /ScanHealth (No component store corruption detected)
the paging file is set: "Automatically select the size of the paging file" (tried different options. manually 10-20GB, at the choice of the system, etc. without changes)
checked all variants of memory dumps: small dump, kernel memory dump, etc. set to "Automatic"

Further actions:

I am deploying a backup of this server on a virtual machine with !! SCSI !! disks. there are no errors.
If deployed on a virtual machine with NVMe disks, errors again and no dump is created.
created a clean server on a virtual machine with an NVMe disk. installed updates. there are no errors.

converted the disk to dynamic and after reboot the same errors. 2 Volmgr 45 and 1 Volmgr 46.

memory dumps are not created

judging by everything described, when using a dynamic NVMe disk in Server 2019, there are problems with volmgr and creating a crash dump.

Server 2016 Standard didn't have this problem. previously used in a similar configuration. and checked specifically, as described in paragraph 3

server configuration just in case, although, apparently, it's not in the hardware:

Ryzen 9 5950X

Asus PRO WS 565-ACE

128GB DDR4 ECC

2xNVMe Samsung Enterprise PM9A3

is there any fix for the system? can someone help?

P.S.

found a similar problem here:

did not find a solution.

Your answer