THX for the Adobe info... I may have to get an NVIDIA card for my cube, since it is mainly used under Windows with Adobe apps.
Regarding your drive issue, I wonder if you are having them same issue as
@CaseySJ, he can't boot from an NVME drive unless he's using OSXAptioFix-free2000. In light of the recent updates on the forum, you should try booting with FWRuntimeServices and OCQuirks.efi files instead of AptioMemoryFix. This may or may not help.
I think (and unless you have an empty drive there's no way to test this), Windows is not the issue here, but adding the NVME drive to that slot might be the problem. As you said, it may be altering the memmap and causing allocation errors once the drive is plugged in...
As I only have 1 NVMe drive on the bottom slot (970 EVO). I'm not experiencing such issues. I have WIndows 7 and 10 sharing the 970 EVO, and then have macOS Mojave and Catalina sharing an 860 EVO on a SATA port. This seems to be working fine with AptioMemoryFix.efi.
If I get a chance I;'ll add a second NVME drive on the top slot (for the sake of testing), see what happens. Of course I'm still on BIOS F7, so that may also play a part here