Crash when using Vulkan

[arus_lightis]

GZDoom immediately crashes when having Vulkan as renderer. Which means I can't even change the renderer back from the options menu.

My laptop setup:
Windows 10 22H2 19045.3570
Intel Core i5-6200U
NVidia GeForce 940M 2GB

Error message:
Code: C0000005 (Access Violation - tried to write address 0000000000000000)
Address: 0000000000000000
Flags: 00000000

[Graf Zahl]

Please post the entire crash log, this does not help at all.

[arus_lightis]

Here's the log.

[Graf Zahl]

What is your graphics hardware?

[humplebert]

I believe I am experiencing the same error. CrashReport.zip and NVIDIA System Summary included.

[Redneckerz]

What is your graphics hardware?

Says so in the OP:
Intel Core i5-6200U
NVidia GeForce 940M 2GB

[Rachael]

I believe I am experiencing the same error. CrashReport.zip and NVIDIA System Summary included.

Huh, interesting, I did not know that Microsoft had a Mesa Vulkan fallback.

Needless to say though, it isn't compatible with GZDoom. And either way it's definitely not the right driver for an RTX 4090 on Windows.

Try reinstalling your drivers (from NVidia, directly) and see if that fixes the problem. Make sure to do a system restart afterward.

This one may work: (as of 2024/01/23, please recheck for the latest driver if you are past this date)
https://www.nvidia.com/Download/driverR ... 927/en-us/
It's a Studio Driver, which means at the very least you don't have to update it as often, they're often tested to be more stable, too, but it might be incompatible with cutting edge games as they are released. (But if you're using GZDoom, that's not relevant at the very moment)

[SanyaWaffles]

I think I had a similar experience with one of our in-house forks after the latest NVidia Game Ready driver update. I did check with stock GZDoom and it did similarly. It'd crash (Very Fatal Error, not an abort or whatever) if I held the screenshot key at startup (which I have bound to alt). It also caused the splash screen to cover the startup log. This didn't happen before.

I'll check and see if the problem persisted after I reinstall the driver.

[axredneck]

... the screenshot key at startup (which I have bound to alt)...

Looks like a bad idea.

[SanyaWaffles]

That very may well be, still shouldn't crash.

[Uli_S]

I have a similiar issue.
Vulkan worked for me in the past.
But now it's crashing when I try to launch the game using Vulkan.

Intel i7
Geforce GT 1030 2GB

[Rachael]

Yet another vulkan_dzn.dll crash. Please try updating your display drivers to see if that fixes it.

This is really odd that suddenly there's a bunch of reports coming out against that very .dll with really good hardware - the only thing that this is making clear is that the hardware's own drivers are not at play when these occur.

And the log.rtf confirms this - It's Microsoft's Direct3D12 wrapper.

[Uli_S]

Rachael hat geschrieben:
> Yet another vulkan_dzn.dll crash. Please try updating your display drivers
> to see if that fixes it.

I've already updated all device drivers including the Nvidia driver.
Doesn't fix it.

It's not a critical issue for me, since I can run the Doom games even with HD graphics mods at very high framerates using the OpenGL backend.
But for some very intense custom maps (FrozenT.wad) Vulkan could be an performance advantage.

[Rachael]

I'm looking into this. That layer needs an option to be disabled, I don't have it on my system for some reason so that's making it even more complicated to figure out what's happening.

For those who are affected by this issue: Are you able to start at all in Vulkan? - And if so, can you do me a favour and post a screenshot of the vk_listdevices command?

[dpJudas]

If vk_listdevices lists a second device, then launching it with "+vk_device 1" on the command line should make it attempt to boot with the second device.