Crashes randomly during play, usually visually freezes and then CTD. Happens at a frequency of at least once per mission, and can happen sometimes outside of a mission.
I have verified integrity multiple times, turned off all overlays, turned off frame gen, game stutters too bad without DLSS SuperRes so that is still on. I’ve tried reinstalling drivers, deleting the appdata folder multiple times between fixes, several restarts, tried changing the graphics quality to several baselines and ray tracing is off.
I don’t know why it’s still mentioning FidelityFX though since I run a 4070.
[PC] Do You Use Mods? (Optional):
No, I don’t use mods
Reproduction Rate (Required):
Often (<75%)
Platform (Required):
PC - Steam
[PC] Crash Report (Optional):
GUID: 701b554d-ceba-42d1-9def-08c916205db1
Log File:
Info Type:
[Engine Error]: Deadlock detected while waiting on renderer thread. Update was not called for 16.1 seconds. You need to supply a crash dump or a crashify link in the report since we need both logs and crashdump to investigate this.
The issue could be related to the following modules found in the stack trace:
module ‘GameOverlayRenderer64’. This module is related to Steam Overlay. If this is a recurring issue try disable it and see if that helps.
module ‘sl.common’.
module ‘sl.dlss_g’.
module ‘sl.interposer’. This module is related to Nvidia streamline sdk. If this is a recurring issue disable features related to it and see if that helps.
module ‘amd_fidelityfx_framegeneration_dx12’.
This is the error I keep getting, like… all my overlays are off
Frame gen is turned off too
But if I turn off super res, the game barely functions
@Soligna sorry to hear this. I’ve discussed this with our engine developers and we can see some unusual references to an overlay. Please can you try disabling Steam overlay and let me know if the crashing persists?
The Steam Overlay can be disabled by unticking the ‘Enable the Steam Overlay while in-game’ option in the Steam ‘Settings’ menu.
That setting I turned off the moment I saw that on the error report. The error code has continued to appear even though the setting has been off. I even went more thorough and ensured both Discord and Nvidia Overlays were set to off, same error afterwards, I have no other overlays.
I’ve got it mostly working, had to have DLSS frame gen off, graphics to medium, cores set to 1, verified files, deleted the appdata folder, let it regenerate, then turned off the deadlock detector. This got me not having the deadlock crashes.
Buuuut, now I’m having 2014 disconnection errors frequently. If it’s not one thing it’s another.
Seems like something is wrong with the module ‘sl.interposer’ on your end. At this point its probably best to DDU your GPU drivers and install new ones!
The DDU and reinstall seems to be working fine, I have both DLSS and Frame Gen on now without issue; however, I haven’t re-enabled the deadlock detector to know for sure.
2014 and 2021 errors are prominent though, might start a new thread on it. I tried all of those fixes and it’s still happening at least once a mission, sometimes twice. Sometimes I lose dialogue audio before getting a 2014 error, sometimes it blackscreens first, other times it just freezes solid for a while before getting the 2014.
2021 errors seem to be more related to when I join a match, I have only seen it a few times.
Just so you guys know, the 2014 errors I was having had nothing to do with my internet. I checked windows event viewer and noticed that I was having raid errors at every disconnect, specifically “Reset to device, \Device\RaidPort0, was issued.”
Followed by a ton of “The IO operation at logical block address 0x2477b9f8 for Disk 1 (PDO name: \Device\0000005e) was retried.”
So to fix this, I had 2 m.2s in usb drives that I wasn’t even using that I disconnected, then flashed an updated firmware for my SanDisk 2tb m.2 that I keep my games on. Those two things resolved my 2014 error crashes.
“Staggeringly competent” is always what I wanted to hear myself referred as lol.
The amount of things I tried in-between is what’s staggering. I threw the book at this one. Pretty much every hardware driver on this computer has been fully reinstalled. I tried several graphics mods. Ran 12 hours of internet stability testing for packet loss, reconfigured my router, and replaced all my ethernet cables.
Well lets hope some of the people with constant 2014’s gonna see this and find inspiration in it to look past the notion that it must be caused by the internet!
I was just recently helping my friend to set XMP profile for his memory over discord and after 90 minutes i was pretty much ready to buy a train ticket to Germany and beat him to death
You making this not exactly mundande troubleshooting done and actually figuring out how to fix it on your own is indeed a display of staggering competence!
Haha, doesn’t hurt that I grew up in a computer repair store, and have been a Comcast Tech and a Computer Repair Tech, was just odd that this presented with this game in particular. It always felt like the wrong lock for a disconnect.
Now, if only I could edit the title of the post ahem@FatsharkLev so that it also reflects the 2014 error fix
