reproducible crash in Two colonels and Sam's story

[weirdbeard]

It happens in two colonels, at the beginning of dlc, when you see a big worm through the glass and the character takes out a radio (walkie talkie), also this happens in Sam's story dlc during a conversation with Tom, when the hero takes out a radio to give it to Klim. Somehow it happens when the character takes out the radio. My screen went black, my display losing signal and system hangs, very rarely it just crashing Metro exodus application. It happens while running at dx12 with any preset.

my specs:
Ryzen 5 2600
ASUS Prime b350m-a
Ballistix LT sports 3000mhz 16gb dual channel
Sapphire RX 5700 reference
700w PSU

all drivers, bios, whatever up to date.

p.s.: I have been experiencing problems with black screens for a long time after buying the rx 5700, but usually these problems are happen randomly, not sure if it drivers problem or game bug

[Garwinski]

I have the same problem. I had the same problem in the Two Colonels DLC as well: Whenever the radio is pulled out, I crashed. In the Two Colonels, I could just finish the game in dx11 as the environments were very small and I did not notice the performance decrease, but in Sam's Story, performance is quite bad on dx 11, in dx 12 it is pretty good, but the game crashes every time Sam pulls out the radio. I submitted a crash report to 4A games, hopefully they will pick it up (even though I already reported it with the Two Colonels DLC, and it was never fixed. Now that more people are reporting it though, it might gain some notoriety).

[weirdbeard]

Originally posted by Garwinski:

I have the same problem. I had the same problem in the Two Colonels DLC as well: Whenever the radio is pulled out, I crashed. In the Two Colonels, I could just finish the game in dx11 as the environments were very small and I did not notice the performance decrease, but in Sam's Story, performance is quite bad on dx 11, in dx 12 it is pretty good, but the game crashes every time Sam pulls out the radio. I submitted a crash report to 4A games, hopefully they will pick it up (even though I already reported it with the Two Colonels DLC, and it was never fixed. Now that more people are reporting it though, it might gain some notoriety).

I reported this problem to technical support and sent them a crash dump. Now I am waiting for an answer from them. Could you tell me your PC specs?

[Garwinski]

Pretty similar to yours:

Ryzen 2600
Asus Prime x370 Pro
5700XT reference
16GB RAM
1000w platinum PSU, two separate PCIE 8 pin power cables runnning from PSU to GPU.

[weirdbeard]

Originally posted by Garwinski:

Pretty similar to yours:

Ryzen 2600
Asus Prime x370 Pro
5700XT reference
16GB RAM
1000w platinum PSU, two separate PCIE 8 pin power cables runnning from PSU to GPU.

Do you have issues in any other games, black screens for example? I guess it can be specific stuff with amd navi cards

[Garwinski]

No I actually dont have any general problems like black screens, freezes etc. If you would believe all the threads on reddit this card would function better as a paper weight, but then again, people having problems are of course more vocal than people that are just gaming without any problems.

It could be Navi, but I believe I saw someone else with an AMD card of a different generation having the same problem.

DX12 is mostly included for raytracing, so DX12 development might be more focused on Nvidia (together with all the gameworks stuff), and the crash is triggered by DX 12 calling something NVidia-only that doesnt work on AMD? Who knows, but if everyone that encounters this problem has an AMD card (and I am not sure that is the case right now, not everyone reporting this crash mentioned their hardware), that would at least point the devs in the right direction. But they will probably figure it out from our crash reports with dxdiag, crashreports etc included.

[weirdbeard]

Originally posted by Garwinski:

No I actually dont have any general problems like black screens, freezes etc. If you would believe all the threads on reddit this card would function better as a paper weight, but then again, people having problems are of course more vocal than people that are just gaming without any problems.

It could be Navi, but I believe I saw someone else with an AMD card of a different generation having the same problem.

DX12 is mostly included for raytracing, so DX12 development might be more focused on Nvidia (together with all the gameworks stuff), and the crash is triggered by DX 12 calling something NVidia-only that doesnt work on AMD? Who knows, but if everyone that encounters this problem has an AMD card (and I am not sure that is the case right now, not everyone reporting this crash mentioned their hardware), that would at least point the devs in the right direction. But they will probably figure it out from our crash reports with dxdiag, crashreports etc included.

Unfortunately, I am one of those who have been living on the AMD support forum for half a year in search of a solution to the problem with several hundred of the same people

[Grav]

I would like to say i have this very same issue.
Wouldn't be surprised if it was another unexplainable bug related to these 5700-series cards.
If so, we'll perhaps see a fix in a later Catalyst driver as usual.

Since i bought my card back in August 19, i've seen so many strange and almost random issues coming and going very dependant on the driver installed.
Especially Catalyst 19.12.2 and 19.12.3 gave me specifically some headaches.

specs:
Ryzen 7 3700X
Asus ROG Strix X570-F Gaming
Corsair Vengeance LPX 2*16GB DDR4-3200
Asus Radeon RX 5700 XT TUF Gaming x3 (AMD Catalyst 20.1.3)
Kingston KC2000 1TB
750W Corsair RM750x

[weirdbeard]

Originally posted by Grav:

I would like to say i have this very same issue.
Wouldn't be surprised if it was another unexplainable bug related to these 5700-series cards.
If so, we'll perhaps see a fix in a later Catalyst driver as usual.

Since i bought my card back in August 19, i've seen so many strange and almost random issues coming and going very dependant on the driver installed.
Especially Catalyst 19.12.2 and 19.12.3 gave me specifically some headaches.

specs:
Ryzen 7 3700X
Asus ROG Strix X570-F Gaming
Corsair Vengeance LPX 2*16GB DDR4-3200
Asus Radeon RX 5700 XT TUF Gaming x3 (AMD Catalyst 20.1.3)
Kingston KC2000 1TB
750W Corsair RM750x

update
when I first started the problem scene after installing the new the driver(20.Q1.1 for enterprise), the game did not crash, but later I noticed that my audio device changed to hdmi audio, which I don’t use, and when I changed it back to my usb headset the game crashed again in the same place, but this time without a black screen, just the application crashed to the desktop. It can be some problem with dx12/sound input

[Fuzz]

Changing to DX11 fixed the crashing for me in the DLCs.

[manay27]

Originally posted by Fuzz:

Changing to DX11 fixed the crashing for me in the DLCs.

Thanks! It helped me, too.

[weirdbeard]

Originally posted by manay27:

Originally posted by Fuzz:

Changing to DX11 fixed the crashing for me in the DLCs.

Thanks! It helped me, too.

I think I said at the very beginning that this happens only in dx12, and using dx11 is not a solution to the problem, but a workaround

[Garwinski]

Latest AMD driver notes for driver 20.2.2, just released, mention the following:

Metro Exodus™ may experience an application hang or TDR when choosing some specific dialogue prompts in the Sam’s Story DLC

Could be related to the issue we are describing here. I might try it tonight, but if anyone else is able to try, please report back.

[Cyborg]

Any update on this? Same problem with the radio crashes, also 5700XT.

[weirdbeard]

Originally posted by Cyborg:

Any update on this? Same problem with the radio crashes, also 5700XT.

Fixed in 20.2.2 drivers

[MeowCats]

DX12 is crash happy on my 1080Ti, while DX11 is stable in all scenarios. Was DX12 there since launch or was it added post launch? it feels like another sloppy DX12 implementation.. i wonder if there's atleast one game with DX12 that doesn't crash and/or has frame-pacing issues.