[BUG] Access Violation error upon boot

gebdag commented 3 months ago

GZDoom version

The one shipped with 1.0.2

Which game are you running with GZDoom?

Doom

What Operating System are you using?

Windows 11

Please describe your specific OS version

Windows 11 Pro

Relevant hardware info

12700k, RTX 4090

Have you checked that no other similar issue already exists?

[X] I have searched and not found similar issues.

A clear and concise description of what the bug is.

The game gets to the Raytracing initialization step and then crashes with the following error message: "Code: C0000005 (Access Violation - tried to read address 0000000000000000)". Already tried to clear the config file. It worked fine yesterday. The only thing I installed in the mean time was the Wukong Benchmark off of Steam. Could it potentially be a dependency issue?

Steps to reproduce the behaviour.

Happens upon boot Happens with both RTGL1 and without

Provide a Log

CrashReport.zip

tioslash commented 3 months ago

Same exact error here everytime I try to launch it, except I am using a Radeon 7900 XT gpu.

kissandfly commented 3 months ago

Same here. Windows 11 RTX4070

gebdag commented 3 months ago

I fixed the issue reinstalling the VC redistributable https://aka.ms/vs/17/release/vc_redist.x64.exe

tioslash commented 3 months ago

I fixed the issue reinstalling the VC redistributable https://aka.ms/vs/17/release/vc_redist.x64.exe

Good to hear. Tried it here on my end and unfortunately did not work :/ Still error on launch.

Sk-F commented 3 months ago

Same here. Also reinstalled VC, didn't work.

5800X3D + 6800XT

Mine says: Code: C0000005 (Access Violation - tried to read address 00000000000000008) Address: 00007ffa4a685c81

Couldn't even boot it, not even once.

kissandfly commented 3 months ago

Great works for me, thanks

vvtunes commented 3 months ago

Same error here, tried to reinstall VC redist to no effect. v1.0.2, doom 2, 5800x3d + 7900xt, windows 11 24h2

Code: C0000005 (Access Violation - tried to read address 0000000000000008) Address: 00007ffd9205a9b1

sguart commented 3 months ago

I fixed the issue reinstalling the VC redistributable https://aka.ms/vs/17/release/vc_redist.x64.exe

it worked after i did a repair then reboot the system.

Shageki commented 3 months ago

Same for me: v1.0.2, Doom 2 (Steam), Ryzen 5800X + 6800XT, Windows 11 Pro 23H2

Code: C0000005 (Access Violation - tried to read address 0000000000000008) Address: 00007ffd9a955cc1

Repaired VC Distributable and rebooted, no joy.

greasefart commented 3 months ago

Same error: Code: C0000005 (Access Violation - tried to read address 0000000000000008)

5800X3D, 7900 XTX, latest stable AMD drivers, Windows 11 Pro, updated

Reinstalled VC, rebooted, no luck
Tried Steam Doom II, and DOOM2.wad from GOG distribution, no luck.

Can't wait to play! Looks awesome.

vs-shirokii commented 3 months ago

Eh, null pointer read somewhere.. can someone send a crash dump?

"Save report to disk" and send that file

snoopy7548 commented 3 months ago

Eh, null pointer read somewhere.. can someone send a crash dump?

"Save report to disk" and send that file

Here's my crash report with the same error.

CrashReport.zip

greasefart commented 3 months ago

CrashReport.zip

tioslash commented 3 months ago

Here´s mine:

CrashReport.zip

vs-shirokii commented 3 months ago

Oof, something inside the AMD driver 🤔 I guess I misuse something without checking availability of some feature.

If someone is familiar with Vulkan SDK and Vulkan Configurator (to force Validation Layers, and output validation log), it would be helpful to understand where a problem might be

Low possibility, but maybe to update AMD drivers to latest until then..

Gleniel commented 3 months ago

Oof, something inside the AMD driver 🤔 I guess I misuse something without checking availability of some feature.

If someone is familiar with Vulkan SDK and Vulkan Configurator (to force Validation Layers, and output validation log), it would be helpful to understand where a problem might be

Low possibility, but maybe to update AMD drivers to latest until then..

i think the fluid simulation is the issue, i found it on the comment on other issue. https://github.com/vs-shirokii/gzdoom-rt/issues/14#issuecomment-2295427772

tioslash commented 3 months ago

Oof, something inside the AMD driver 🤔 I guess I misuse something without checking availability of some feature. If someone is familiar with Vulkan SDK and Vulkan Configurator (to force Validation Layers, and output validation log), it would be helpful to understand where a problem might be Low possibility, but maybe to update AMD drivers to latest until then..

i think the fluid simulation is the issue, i found it on the comment on other issue. #14 (comment)

The gzdoom-rt2.ini file does not even show up for me in the /Documents/My Games/GZDoom/ folder after launching the mod once and getting the crash error unfortunately.

vs-shirokii commented 3 months ago

@tioslash You can try to start gzdoom.exe with +rt_fluid 0 argument.

I.e. create .txt file around your .exe, put gzdoom.exe +rt_fluid 0 in it. Rename .txt to .bat, and double-click that .bat file.

Neo27484 commented 3 months ago

set your windows resolution to 1920x1080. This worked for me after the same error. Ingame is max 1080p possible

tioslash commented 3 months ago

@tioslash You can try to start gzdoom.exe with +rt_fluid 0 argument.

I.e. create .txt file around your .exe, put gzdoom.exe +rt_fluid 0 in it. Rename .txt to .bat, and double-click that .bat file.

Hi, can confirm that this worked! I´ve created the .bat file and launched it without issues. Running 4k with FSR Quality mode and FG enabled on a 7900 XT. Latest drivers installed.

As soon as I enabled fluid simulation in the game options it crashed. So at least in my end this was definitely the issue.

Gleniel commented 3 months ago

@tioslash You can try to start gzdoom.exe with +rt_fluid 0 argument. I.e. create .txt file around your .exe, put gzdoom.exe +rt_fluid 0 in it. Rename .txt to .bat, and double-click that .bat file.

Hi, can confirm that this worked! I´ve created the .bat file and launched it without issues. Running 4k with FSR Quality mode and FG enabled on a 7900 XT. Latest drivers installed.

As soon as I enabled fluid simulation in the game options it crashed. So at least in my end this was definitely the issue.

yeah, turning off the fluid simulation on ini file also worked for me, fluid simulation is definitely the issue causing it to crash on AMD GPUs, I'm using RX 6700 XT btw.

greasefart commented 3 months ago

+rt_fluid 0 works for both 7900 XTX and 6800S. Anyone know what visuals I'm missing out on with this?

vs-shirokii / gzdoom-rt