Bug Report - fatal error / crash

[Raposo]

I have started playing again now with the full release and I am getting multiple fatal errors (crash to desktop) on different areas. I have played just a little bit until the start of the first "world" and I got those crashes 3 times.

1. On the starting area just after the first limbo well;
2. After the first cutscene;
3. Locking to the first enemy on the first world;

I am bit worried of getting those crashes more and more, is there any log I can forward to help with a possible fix?

My specs are:
Ryzen 9 5900x
32 GB ram
RX 5700XT (driver version on 21.2.1)

[Redlock Studio]

Hey Raposo,
We're super sorry about that! Thanks a lot for all the details, that's really helpful.
We'll try and fix that asap.

[San Ghervais]

Is it this "LowLevelFatalError [File:Unknown] [Line: 198] Unreal Engine is exiting due to D3D device being lost. [Error: 0x887A005 - 'REMOVED')"

I got one randomly early in the game when I picked up an item, but i cant seem to make it through the village past the second portal, below the Temple of Narueh without receiving this error. Sometimes it crashes as soon as I walk away from the save point, and some times I can get a ways in

[6daveroo9]

I am also getting various crashes, often from D3D device being lost.

Specs:
- Operating System: Windows 10 Pro 64-bit (10.0, Build 19042) (19041.vb_release.191206-1406)
- System Manufacturer: ASUSTeK Computer
- System Model: TUF B450M-PRO GAMING
- BIOS Date: 11/13/19 18:02:32 Ver: 05.0000D (type: BIOS)
- Processor: AMD Ryzen 7 3800X 8-Core Processor (16 CPUs), ~4.2GHz
- Memory: 32768MB RAM DDR4
- Display Card: AMD Radeon RX 5700 XT
- Display Memory: 24504 MB

Other than that, very much enjoying the game. Having the option only to "perfect block" was a bit of an irritation, but I'm getting the hang of it. One thing, though - there is one triangular transporter that takes you right beside an enemy, who can lambaste the crap out of you while you materialise. Bad form - pretty close to downright cheating. It's only in the one spot, so far, but left a very bad taste in my mouth. I'm happy to have to be ready to dodge, or run, or whatever, the minute I materialise, but losing half my health while I'm stuck in the process of materialising is frustrating/enraging.

[Daryth]

Looks like it's to do with Radeon cards (I have a Radeon RX 5700 XT). I have a similar issue as well. When I come across the enemy with explosive attacks. If one lands near me the game crashes with a Fatal Error.....

[Okwaho]

I have an Nvidia 1070 in my laptop and I am also having super frequent hard crashes. It's not the Ryzen.

[leovic]

I get crashes too

Originally posted by Gherontius:

Is it this "LowLevelFatalError [File:Unknown] [Line: 198] Unreal Engine is exiting due to D3D device being lost. [Error: 0x887A005 - 'REMOVED')"

I get those crash reports too. I get other crash reports to. I'll start recording them now that I get so many crashes. I'm running an AMD Ryzen 7 2700x CPU and Radeon RX Vega 64 on 21.1.1 drivers.

I'm at the point in the game where I cleared Niphur and Radamanthe's Temple. I just beat the Stranger for the second time and got the crucible upgrade that allows for level 8 weapon upgrades. The Stranger never reappeared in Limbo. I hope that's on purpose because that means I'm missing a spell upgrade then.

[Raposo]

@Redlock Studio

Just a quick update, I had another session of around 2h and everything went really smooth with no crashes and errors at all.
I will add more details to this topic if it starts to occur again.

[mitc1111]

The first 15 hours of gameplay I didnt get any crashes. Now I'm getting the fatal error crash fairly often. It seems like it happens more with the guys shooting the explosive red balls at me. Maybe something to do with the explosive effects?

[San Ghervais]

Anyone still seeing that same fatal error with the new patch?

I haven't seen it again yet, but I did just get a new one:

error DXGI_EERROR_DEVICE_REMOVED

Edit: some quick research shows this may be a different symptom of the same underlying issue. many posts are suggesting editing the windows registry TDR level or Delay, although some users reported blue screen crashes instead of game crashes after messing with TDR Level in other games, but I've found no similar claims about TDR Delay

[Floid]

Originally posted by Gherontius:

Anyone still seeing that same fatal error with the new patch?

I haven't seen it again yet, but I did just get a new one:

error DXGI_EERROR_DEVICE_REMOVED

Edit: some quick research shows this may be a different symptom of the same underlying issue. many posts are suggesting editing the windows registry TDR level or Delay, although some users reported blue screen crashes instead of game crashes after messing with TDR Level in other games, but I've found no similar claims about TDR Delay

Time delay response has always been the first thing I edit on a new gaming system. And sadly it's still kinda needed in 2021 - as it helps with a wide range of issues with games, by just helping to make the Windows OS more forgiving. It should be noted though that TDR is not a cure all, it won't stop a game from crashing if it has some real stability issues, or conflicts, or can't work because of absent prerequisites.

All editing TDR does is give the game more time to recover (if it's able to) in the event it stops responding. But as we all know, apps, games and browsers can all enter into an none-responsive state every so often, but that doesn't necessarily mean the actual whole process has crashed.

Here's a real world example for you - back when witcher 3 first released, it was very unstable at the time. Many people would have the game hard crash often with the default windows TDR value. Then some of us edited the TDR value in registry, and noticed that these crashes suddenly turned into 3-5 second freezes, and then the game would recover and continue on working as normal. So for many people editing TDR, 'effectively' fixed the crashing for them, as they were no longer technically crashing, but just having 3-5 second freezes instead, that the game would often recover from.

So that's basically the jist of TDR.
Also TDR is still not a outdated tweak even today, as it can really help with averting crashing with a lot of early access titles. As they often enter into a "Not Responding" state sometimes when they are loading, but then if you give them a few extra TDR second's, they will load normally.

[San Ghervais]

Thanks for fleshing that out. Almost every post I found was either a copy paste with no original source all over battlefield, fifa and tomb raider discussions, or how to posts on microsoft forums, neither of which I thought it would be helpful to quote.

I haven't had a crash since upping the delay (yet), although i have had a couple short freezes, but nothing more than what appeared to be the frame rate dropping. So, hopefully, this workaround will hold anyone seeing this issue over until the devs can address underlying issues?