Thanks @tjwmmd2. I tracked down the history of this and it looks like it’s being tracked in internal bug number 4745620. It sounds like the problem is not exactly a bug, but a limitation in which virtual address ranges are needed by CUDA and an incompatibility between how CUDA needs to run and how DXVK is using memory. It’s being worked on but it doesn’t sound like it’s simple to solve.
The patch sounds pretty iffy to me. If it works, it’s likely purely by luck depending on which address ranges the game ends up using.