AMD and direct x 12

[Jerbus]

I recently upgraded my graphics card to an AMD radeon RX 6750 XT literally for Silent Hill 2 remake because my old card couldn't run it and was getting great fps on high settings. I stopped playing for a while and I guess an update messed up the game for some people. Game crashes on launch and is unplayable. I tried many different fixes and found the only thing that works is launching with -dx11 command or changing D3D12 file, and deleting the file: amd_fidelityfx_dx12.dll in SilentHill2>SHProto>Binaries>Win64 folder. If the amd file is still there, I get the same crash on launch. Game runs like trash in Dx11 and I thought I fixed my problem but I'm pretty sure that deleting the amd file only makes the game run in direct x 11 because I'm getting massive frame drops, avg 50 FPS, and performance issues that I didn't have before the update. I also marked the SHProto-Win-64-Shipping.exe file as an exception in my antivirus. I don't know if that was needed or not.

This is the error I consistently get on launch:
Fatal error!

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000020

SHProto-Win64-Shipping.exe
SHProto-Win64-Shipping.exe
SHProto-Win64-Shipping.exe
SHProto-Win64-Shipping.exe
SHProto-Win64-Shipping.exe
SHProto-Win64-Shipping.exe
SHProto-Win64-Shipping.exe
SHProto-Win64-Shipping.exe
SHProto-Win64-Shipping.exe
SHProto-Win64-Shipping.exe
SHProto-Win64-Shipping.exe
KERNEL32.DLL
ntdll.dll

Crash in runnable thread RHIThread

Sometimes the 0x0000000000000020 will read 0x0000000000000000 if i delete the D3D12.dll file in the D3D12 folder.

Is anyone else with an AMD card able to run the game with direct X 12? I'm currently at a loss right now because I've spent days looking on threads and troubleshooting to no solution. I think the problem lies somewhere with the amd_fidelityfx_dx12.dll file but I can't really find any information for this online. The game will not launch with this file in the folder and if it's not, I'm pretty sure it's direct x 11 which is almost unplayable.

System info:
Windows 10
AMD Ryzen 7 2700x Eight-Core Processor
RAM: 16GB
GPU: AMD Radeon RX 6750 XT
This is my first time really posting for help so if any further info is needed, let me know.

[Zephyr]

Hi there :). I have an RX 7900XT and the game crashed twice in a row on startup. Not even a start menu :). It was clearly GPU/GPU driver related from the error message (ntdll.dll). Since I usually undervolt my GPU heavily I thought, well ok, let us try vanilla settings, more or less. I got the game to start on third try with GPU clock set to 2450 mhz, voltage at 100% vanilla, 1100 mV in my case, no memory OC, no power target change.

Once the game got to load the first time i could apply my usual undervolt/OC settings again.

https://steamcommunity.com/sharedfiles/filedetails/?id=3393434978
https://steamcommunity.com/sharedfiles/filedetails/?id=3393434923

This is with UV 1030 mV, 2650 mhz GPU clock max. However this will not be directly applicable for your GPU. Settings are maxed out graphics (except Ray tracing off), XeSS balanced, scaled to 4K.

So, maybe try to reduce GPU clock a bit and set all else to vanilla. Otherwise maybe clean driver installation with DDU could help. I only started the game now, so no idea to help you further. Your PC will likely struggle a fair bit with the game considering how much difficulty my GPU has, though. Maybe it was different before the last patch, I have never seen it :).

This may also help:

https://steamcommunity.com/app/2124490/discussions/0/595136312034515000/

[Dude Guyman]

I have 2 AMD GPUs (RX 6600 and RX 6750 XT), and an Nvidia GTX1660 Super. In my experience with those...

I get the same crash on all of them, and on many driver versions I have tried out.
"amd_fidelityfx_dx12.dll" is the FSR upscaling file, and I doubt very seriously it has anything to do with the crash (which is related to dx12 shader caching) unless your settings call for it and it's missing. Once shader caching is successful, the crashing stops. Same crash with: "Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address" that happens ~instantly, before any loading screens or menus even appear.

None of the fixes posted here had any effect. The only "fix" was start, restart, restart, 2-20 times until you finally get a black screen, that looks like it froze. If you get to that WAIT! After 1-3 minutes, it goes to "caching shaders" and after that you're golden. I am convinced all the "fixes" posted here have no effect and it just happens to launch randomly and then folks think that last "fix" they tried actually worked when it was just random in reality. The game NEEDS a patch for this!

Also, you can get a newer version of the amd_fidelityfx_dx12.dll file from (dig it out of the SDK v1.1.3 "binaries" folder) assuming the game's stock version (1.0.1.37507 was it?) is older, but it won't fix the crash:

FSR FidelityFX SDK v1.1.3:
https://github.com/GPUOpen-LibrariesAndSDKs/FidelityFX-SDK/releases
amd_fidelityfx_dx12.dll = 1.0.1.39157 (SDK 3.1.3)

Or, if you prefer, XeSS SDK 1.3.1:
https://github.com/intel/xess/releases
Libxess.dll = 1.3.1.32

[Zephyr]

Originally posted by Dude Guyman:

I have 2 AMD GPUs (RX 6600 and RX 6750 XT), and an Nvidia GTX1660 Super. In my experience with those...

I get the same crash on all of them, and on many driver versions I have tried out.
"amd_fidelityfx_dx12.dll" is the FSR upscaling file, and I doubt very seriously it has anything to do with the crash (which is related to dx12 shader caching) unless your settings call for it and it's missing. Once shader caching is successful, the crashing stops. Same crash with: "Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address" that happens ~instantly, before any loading screens or menus even appear.

None of the fixes posted here had any effect. The only "fix" was start, restart, restart, 2-20 times until you finally get a black screen, that looks like it froze. If you get to that WAIT! After 1-3 minutes, it goes to "caching shaders" and after that you're golden. I am convinced all the "fixes" posted here have no effect and it just happens to launch randomly and then folks think that last "fix" they tried actually worked when it was just random in reality. The game NEEDS a patch for this!

Also, you can get a newer version of the amd_fidelityfx_dx12.dll file from (dig it out of the SDK v1.1.3 "binaries" folder) assuming the game's stock version (1.0.1.37507 was it?) is older, but it won't fix the crash:

FSR FidelityFX SDK v1.1.3:
https://github.com/GPUOpen-LibrariesAndSDKs/FidelityFX-SDK/releases
amd_fidelityfx_dx12.dll = 1.0.1.39157 (SDK 3.1.3)

Or, if you prefer, XeSS SDK 1.3.1:
https://github.com/intel/xess/releases
Libxess.dll = 1.3.1.32

Yes, it may be that you just need to restart until it finally works. in that case I was lucky. Only two crashes and now it seems to work without issues.

[Jerbus]

Originally posted by Dude Guyman:

I have 2 AMD GPUs (RX 6600 and RX 6750 XT), and an Nvidia GTX1660 Super. In my experience with those...

I get the same crash on all of them, and on many driver versions I have tried out.
"amd_fidelityfx_dx12.dll" is the FSR upscaling file, and I doubt very seriously it has anything to do with the crash (which is related to dx12 shader caching) unless your settings call for it and it's missing. Once shader caching is successful, the crashing stops. Same crash with: "Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address" that happens ~instantly, before any loading screens or menus even appear.

None of the fixes posted here had any effect. The only "fix" was start, restart, restart, 2-20 times until you finally get a black screen, that looks like it froze. If you get to that WAIT! After 1-3 minutes, it goes to "caching shaders" and after that you're golden. I am convinced all the "fixes" posted here have no effect and it just happens to launch randomly and then folks think that last "fix" they tried actually worked when it was just random in reality. The game NEEDS a patch for this!

Also, you can get a newer version of the amd_fidelityfx_dx12.dll file from (dig it out of the SDK v1.1.3 "binaries" folder) assuming the game's stock version (1.0.1.37507 was it?) is older, but it won't fix the crash:

FSR FidelityFX SDK v1.1.3:
https://github.com/GPUOpen-LibrariesAndSDKs/FidelityFX-SDK/releases
amd_fidelityfx_dx12.dll = 1.0.1.39157 (SDK 3.1.3)

Or, if you prefer, XeSS SDK 1.3.1:
https://github.com/intel/xess/releases
Libxess.dll = 1.3.1.32

I think you might be right. I finally got the game to load after several steam/game/computer restarts. It got further into the loading screens but crashed 2 times until it finally loaded. My saves were gone and I started a new game and made 2 saves. Finally getting around 80 FPS but will still get major stutters occasionally. Some stutters were major and lasted 10 swconds. I closed and opened the game and finally got the compiling shaders message, played a little more and then closed and tried to add one of my old back up saves to get back to where I was. Same crashes again. Gonna keep trying to restart until something sticks. Frustrating, but thank you, I feel like I finally got somewhere.

[Dude Guyman]

Another interesting/odd thing I noticed in the hours of troubleshooting this game was in the ".\AppData\Local\SilentHill2\Saved\SaveGames\GFXSettings.SHProto-Win64-Shipping.xml" file, after using the -dx11 switch, about 9 lines down would be "-dx11" added in after the EXE, like so:

<EXECCMD Value="SHProto-Win64-Shipping.exe -dx11 SAVEWINPOS=1" />
</APPLICATION>

Even after you switch back to -dx12, it would remain there, and "-dx12" never appears there, because it is assumed as default I would guess. Other times I could run with -dx11 and that text would not appear there. No idea why or if it matters. I found it odd though.