Gollum Fatal Error Crash At Game Start.

vkd3dclosed

HansKristian-Work/vkd3d-proton#1578 · opened 2023-05-29 by 7gxycn08 · updated 2023-05-30 · 11 comments · github

77gxycn08 2023-05-29 github

Getting Unreal Engine Fatal Error Crash at start of the exe when vkd3d is installed.
here is the full crash log

                   Exception Analysis                                   *

KEY_VALUES_STRING: 1

Key  : AV.Dereference
Value: NullClassPtr

Key  : AV.Fault
Value: Read

Key  : Analysis.CPU.mSec
Value: 250

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 393

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

Key  : Analysis.Init.CPU.mSec
Value: 78

Key  : Analysis.Init.Elapsed.mSec
Value: 8798

Key  : Analysis.Memory.CommitPeak.Mb
Value: 346

Key  : Timeline.OS.Boot.DeltaSec
Value: 100249

Key  : Timeline.Process.Start.DeltaSec
Value: 1

Key  : WER.OS.Branch
Value: ni_release

Key  : WER.OS.Timestamp
Value: 2022-05-06T12:50:00Z

Key  : WER.OS.Version
Value: 10.0.22621.1

Key  : WER.Process.Version
Value: 4.27.2.0

FILE_IN_CAB: UE4Minidump.dmp

CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000000000000000 rcx=000000000e1e97a8
rdx=f7859b33211854be rsi=0000000000f7e7b8 rdi=000000000e1e97a8
rip=00007ffa550024c4 rsp=0000000000f7e730 rbp=0000000000f7e790
r8=0000000000f7e7b8 r9=00007ffab9f4e170 r10=0000000030fa6080
r11=0000000000000000 r12=0000000000000000 r13=00007ff64b57e020
r14=0000000000f7e8e8 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
amdxc64+0x824c4:
00007ffa550024c4 488b5038 mov rdx,qword ptr [rax+38h] ds:0000000000000038=????????????????
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffa550024c4 (amdxc64+0x00000000000824c4)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000038
Attempt to read from address 0000000000000038

PROCESS_NAME: ToM-Win64-Shipping.exe

READ_ADDRESS: 0000000000000038

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000038

STACK_TEXT:
0000000000f7e730 00007ffa55003476 : 000000000b4fcb18 000000000e1e97a8 000000000e1e97a8 00007ff649cc57c6 : amdxc64+0x824c4
0000000000f7e760 00007ff649cc582b : 0000000000f7e8a8 00000000101b1250 00000000101b1428 0000000000000000 : amdxc64!AmdExtD3DCreateInterface+0x6c6
0000000000f7e7a0 00007ff649cc625f : 0000000000f7e8a8 00000000101b1250 0000000000000000 0000000000000000 : ToM_Win64_Shipping!agsDriverExtensionsDX11_WriteBreadcrumb+0x6bb
0000000000f7e7e0 00007ff64793bf77 : 00000000103422e8 0000000000f7e960 0000000000000000 0000000018d5e020 : ToM_Win64_Shipping!agsDriverExtensionsDX12_CreateDevice+0x1ef
0000000000f7e860 00007ff647944361 : 00000000010a7648 0000000000f7eb50 00000000010a7648 0000000018d5e020 : ToM_Win64_Shipping!ffxGetVkImageView+0xb3e257
0000000000f7ea50 00007ff64798f96c : 0000000018d117a0 0000000000000001 00007ff64b57e020 000000000e60b290 : ToM_Win64_Shipping!ffxGetVkImageView+0xb46641
0000000000f7eb80 00007ff6485cf115 : 0000000000000000 000000000e60b290 0000000000000000 0000000000000000 : ToM_Win64_Shipping!ffxGetVkImageView+0xb91c4c
0000000000f7ed30 00007ff646538c9d : 000000000e60b300 0000000000000004 00007ff64a78a5c8 0000000000000001 : ToM_Win64_Shipping!ffxGetVkImageView+0x17d13f5
0000000000f7eea0 00007ff646531a36 : 0000000000000255 00007ff649e9dbe0 0000000000000000 0000000006287b00 : ToM_Win64_Shipping!AK::WriteBytesCount::Reserve+0xd04d
0000000000f7f4f0 00007ff646531d1a : 0000000000000030 0000000000000000 0000000000000000 0000000000000000 : ToM_Win64_Shipping!AK::WriteBytesCount::Reserve+0x5de6
0000000000f7f620 00007ff646532fb4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ToM_Win64_Shipping!AK::WriteBytesCount::Reserve+0x60ca
0000000000f7f660 00007ff64653bfd4 : 000000000000000a 00007ffaee68549c 00000000010a800a 0000000000000000 : ToM_Win64_Shipping!AK::WriteBytesCount::Reserve+0x7364
0000000000f7feb0 00007ff649dc378e : 000000000000000a 00007ff649dc3805 0000000000000000 0000000000000000 : ToM_Win64_Shipping!AK::WriteBytesCount::Reserve+0x10384
0000000000f7fef0 00007ffaef0626ad : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ToM_Win64_Shipping!agsCheckDriverVersion+0xfceae
0000000000f7ff30 00007ffaf114a9f8 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x1d
0000000000f7ff60 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x28

STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: amdxc64+824c4

MODULE_NAME: amdxc64

IMAGE_NAME: amdxc64.dll

FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_amdxc64.dll!Unknown

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 31.0.14057.2005

FAILURE_ID_HASH: {ac9cacbc-d019-a8b4-7a28-a2425548d10b}

Followup: MachineOwner
`

Software information

Name of the game, settings used etc.
Lord of the rings Gollum

System information

GPU:7900xtx
Driver:23.5.1
Wine version: NA
VKD3D-Proton version: 2.9

Log files

UE4Minidump.zip

BBlisto91 2023-05-29 github

In the future it's better if you can attach any logs as a github gist or text file so they don't fill up the whole issue.

Are you using dxvk's dxgi.dll along with vkd3d-proton?

Mmbriar 2023-05-29 github

looks like maybe it fails because it's trying to use amdags, which will probably never work with vkd3d-proton on windows. Maybe overwriting the vendor id in dxvk.conf to something with dxgi.customVendorId = ffff will help, but keep in mind that vkd3d-proton is usually either slow or broken on AMD's windows driver, so there is not much point in using it in the first place on windows.

77gxycn08 2023-05-29 github

In the future it's better if you can attach any logs as a github gist or text file so they don't fill up the whole issue.
Are you using dxvk's dxgi.dll along with vkd3d-proton?

tried both with and without dxvk dxgi.dll i still get the same fatal error.

Mmbriar 2023-05-29 github

vkd3d-proton can't work without dxvk's dxgi.dll. Try the config option I posted above. If that doesn't help there is probably nothing that can be done here. The game is known to work on linux with vkd3d-proton.

BBlisto91 2023-05-29 github

Ye try the config, needs to be made next to the exe or where ever the dxgi log is generated if that is different.
I tried to quickly boot the game on Linux with 2.9 both with the radv and amdvlk driver and besides the videos being black it seems to work and i can get to the main menu. Same GPU

77gxycn08 2023-05-29 github

vkd3d-proton can't work without dxvk's dxgi.dll. Try the config option I posted above. If that doesn't help there is probably nothing that can be done here. The game is known to work on linux with vkd3d-proton.

dxgi.customVendorId = ffff

did the trick for me the game launched however it is stuck on a black screen and won't load the intro movies.

BBlisto91 2023-05-29 github

Skip them with holding space and see if it doesn't go ahead after that

77gxycn08 2023-05-29 github

Skip them with holding space and see if it doesn't go ahead after that

It worked Thank you so much!!

BBlisto91 2023-05-29 github

I will look in to making a separate issue for the black videos if it is indeed related to vkd3d-proton

77gxycn08 2023-05-29 github

Is there a workaround for ray tracing?
I have VKD3D_CONFIG = dxr set in enviroment variables but when i enable raytracing in game It gives me a fatal error crash.

Mmbriar 2023-05-29 github

Ray tracing is pretty broken on all AMD drivers with vkd3d-proton, so probably not.