[SOLVED] Crash with Raze and Vulkan

The DOS game "Shadow Warrior" (shareware) works flawlessly with Raze and ReShade using OpenGL. Raze alone with Vulkan renderer also works flawlessly.
With the Vulkan driver and ReShade in Raze, however, the screen instantly freezes as soon as the gameplay is started. The menu works, but when one gets into the actual gameplay, the error message appears:

Code: C0000005 (Access Violation - tried to read address 00000000000000f8)
Address: 00007ffa8ada365a
Flags: 00000000

I tested it with both ReShade 6.1.1 and 6.2 and with both the current official (April 2024) and an older development (Feb 2024) build of Raze. When switching the renderer, I always first uninstalled Reshade completely and then set it to the new Raze renderer. The error appears whenever ReShade is installed, without any shaders selected.

I cannot seem to reproduce this, ReShade 6.2, Raze at default settings with Vulkan:


It would be useful to get ahold of the crash dump (since Raze is nice enough to create one).

So apparently it's not a problem of Raze and ReShade per se.
For further testing, I changed some settings both in the Raze config and in the Nvidia driver (the problem occured in all driver versions of that time, but now I only tested the current 560.70).
V-Sync, Linear scaling, DXGI, latency, whatever ... all settings show the same "very fatal error" that is described above. Here are some lines from the crash report:

Bytes near RIP:
00007ffa60b9364a: 85 c0 48 8d 48 b0 8b 07 49 0f 44 cf 4c 6b c0 2c
00007ffa60b9365a: 4c 8b 89 f8 00 00 00 49 8b 0b 41 8b 81 98 01 00
00007ffa60b9366a: 00 41 89 44 08 04 48 8b 06 48 8b 40 20 48 85 c0

Call trace:
  rip=00007ffa60b9365a  <- Here it dies.
  Function range: 00007ffa60b92e60 -> 00007ffa60b93ac8

 FRAME 00:
  rip=00007ffa60afb7eb rsp=000000e62c9ad8c0 rbp=0000000000000002
  r12=000002201d5b6600 r13=000002200cff60c0 r14=0000000000000000
  rdi=000002202d6a4c20 rsi=000002201d5abd08 rbx=000000e62c9adbb0
   -> 'rbx' saved on stack at 000000e62c9ad8c0 (=> 000000e62c9adbb0)
   -> 'rbp' saved on stack at 000000e62c9ad8c8 (=> 0000000000000002)
   -> 'rsi' saved on stack at 000000e62c9ad8d0 (=> 000002201d5abd08)
   -> 'rdi' saved on stack at 000000e62c9ad8b0 (=> 000002202d6a4c20)
   -> 'r14' saved on stack at 000000e62c9ad8a8 (=> 0000000000000000)
   -> 'r15' saved on stack at 000000e62c9ad8a0 (=> 000002201d5aba80)
  Function range: 00007ffa60afb6c0 -> 00007ffa60afb8b5

 FRAME 01:
  rip=00007ffa5fa02fb1 rsp=000000e62c9ada70 rbp=000000e62c9adb70
  r12=000002201d5b6600 r13=000002200cff60c0 r14=0000000000000002
  rdi=000002202d6a4c20 rsi=000000000000002e rbx=0000000000000000
   -> 'rbx' saved on stack at 000000e62c9ada70 (=> 0000000000000000)
   -> 'rbp' saved on stack at 000000e62c9ada78 (=> 000000e62c9adb70)
   -> 'rsi' saved on stack at 000000e62c9ada80 (=> 000000000000002e)
   -> 'rdi' saved on stack at 000000e62c9ada60 (=> 000002202d6a4c20)
   -> 'r14' saved on stack at 000000e62c9ada58 (=> 0000000000000002)
   -> 'r15' saved on stack at 000000e62c9ada50 (=> 0000000000000006)
  Function range: 00007ffa5fa02a10 -> 00007ffa5fa0302e
  Function range: 00007ffa5fa02880 -> 00007ffa5fa02a10

As soon as ReShade is installed (without any shaders activated), any Build game freezes when starting the actual gameplay. GzDoom Vulkan with ReShade work flawlessly.

I can't do anything without a crash dump (*.dmp).

The crash happens, when all four conditions are fulfilled:
1) ReShade for Vulkan is installed
2) GZDoom / Raze is configured for Vulkan
3) Options - Display Options - Multisample is *NOT* off
4) The actual gameplay has been started

Fixed by github.com/crosire/reshade/commit/de89b8...ddca1eb7da1804cf32e0 .