My two-pennyworth on this in case other people are having the same problem (TLDR: try using something other than NVMe drives):
I had a motherboard failure that I decided to use as an opportunity to clean out all the rubbish and reinstall Windows from scratch. There was some stuff on my C: drive I needed to keep, though, so I restored a backup of my C: drive to a new virtual machine, so I could copy what I wanted to a Shared Folder. Host and guest are both Windows 11 23H2. VMWare Workstation Pro 17.5.0 Build 22583795. When creating the guest, I used all the recommended defaults except for memory, where I gave it 16GB instead of the recommended 4GB (the host has 64GB), and host-only networking, because I don't need the guest to talk to anyone else.
The restore of the backup worked ok, and Windows booted in the guest ok, but every time I tried to copy the stuff I wanted to a shared folder, I got a WHEA_Uncorrectable_Error BSOD in the guest after about 2 minutes. After about the 4th or 5th time, I figured this wan't going to work, so had a look at the mini dumps. All the dumps pointed towards a storage error, mostly involving stornvme.sys. So I decided to switch to a non-NVMe drive (see below if you're in a similar situation). I created a new VM and used a SATA drive instead of NVMe, and have had no problems since.
The ugly details of converting to SATA:
I don't know of a way to convert an NVMe drive to a SATA drive, so I decided to create a new VM and, because I didn't wnat to go through the many hours of restoring a 1TB backup, use the existing vmdk. For some incomprehensible (to me) reason, Workstation Pro does not allow you to attach an existing unencrypted drive to an encrypted virtual machine, EVEN IF THE VIRTUAL MACHINE IS NOT ENCRYPTING THE DRIVES. I totally fail to understand this - the existing drive on the virtual machine is unencrypted, so what difference does it make to add another unencrypted drive? Anyway, because of this I had to create a new WIndows 10 VM, without a TPM, and attach the existing drive to it as a SATA drive. I then minimally encrypted the VM, added a TPM, changed it to Windows 11 and booted. All worked ok.
