It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I had the same problem Tried everything.

My system 1080Ti water cooled. overclocked 17 5820 at 4gightz 64 bit windows 10 pro, 32 gig ram.

My system runs anything. This is not your system. its there software.

My FIX...

Change to window mode,

Keep your vid settings low for the fight.

the key is the resolution. I went to a identical resolution and rendering to 1080 x 720. At this setting I was able to fight with no crashes. I found that if the rendering didn't match the resolution it would still crash during the fight. Never could finish it. Only when i went to the above did it work correctly. I changed it back to normal after and it works like a champ again.

Something is playing out with the code to the cpu and gpu with the rendering on the resolution. My thought.. Give the above a try. also turn off the music and sound effects if you have a lower cpu. Will keep the strain off the cpu.
I have a nvidia 3090 graphics card and intel i9-11900k. Same problem with CTD. My solution was to go to control panel and change physx to CPU. Then in the game I disabled all ray tracing. Was able to play through the anchor without a problem. After that I changed my settings back to what they were.
spec: r5 3600 and rtx 3070.
Same problem was resolved after uninstalling amdgpu driver using DDU.
Had the same problem.
What helped was the workaround with changing the priority of the executable process to "high" via the task manager (Details tabs, right click on the process).
Either this or I was just lucky as I tried to finish it as fast as possible.

My system:
Windows 10 Pro 20H2
AMD 5600X
AMD 6700XT
32 GB Ram

Crash appeared always when the boss started to spawn the enemies.
Post edited December 28, 2021 by TheCandyMan666
avatar
TheCandyMan666: Had the same problem.
What helped was the workaround with changing the priority of the executable process to "high" via the task manager (Details tabs, right click on the process).
Either this or I was just lucky as I tried to finish it as fast as possible.

My system:
Windows 10 Pro 20H2
AMD 5600X
AMD 6700XT
32 GB Ram

Crash appeared always when the boss started to spawn the enemies.
Thank you, I followed the settings and turned off the sound, and defeated the boss
Like many of you, I also encounter the crash when attempting to fight the anchor. Also, like many of you, I had to reduce the resolution and put my graphics performance to low. I ran the game with DX11 and I change the phyX management, on NVIDIA control panel, to my processor and not my graphic card. And even with that, I still had crash during the fight, but I manage to kill it.

My config:
processor: ryzen 5600X
graphic card: RTX 3080
RAM: 32Go
I tried all the fixes listed here and on a few Reddit threads, I finally beat it by using the ingame cheat (I mean, assist!) menu for One hit kills.

I really resent needing to resort to that as a work around, but after almost two hours of troubleshooting it just wasn't worth trying to fix anymore.
I capped my FPS at 30 with RTSS, using DX11 and it didn't crash.
The problem still persists as of Jan 2022.

Specs:
OS: Win10 Pro 64-bit 21H2
CPU: Ryzen 7 4800H
GPU: GTX 1650 Ti
RAM: 16GB

Game Settings:
API: D3D11
Quality Preset: Low
Render Resolution: 1080p

Solution (no hacky workarounds):
NVIDIA Control Panel > Configure Surround, PhysX > PhysX settings (Processor: CPU)

It will still crash if you take too long to defeat the Anchor so keep it under 5mins if you can. Try facing the wall whenever it's doing crazy animations. This sub-mission is optional and you can beat it faster if you have the Launch Enemy ability to throw the exploding Hiss back to the core rather than going for the red clocks.

After you beat the Anchor, set PhysX back to Processor: GPU.

Cheat Mode (sort of):
Gameplay > Assist Mode (Enabled) > One-Hit Kills (Checked)

With PhysX still set to CPU, obviously this in-game setting will let you defeat the boss in seconds. Do this if you really just need this sub-mission done. It's not your fault they didn't fix the bug after all this time.
Post edited January 13, 2022 by kathyrollo
I have a problem when I put the menus and collectibles while I am playing. the screen is clinched :/
Same problem. Sometimes it crashes after a few seconds, sometimes after one minute, sometimes after 2 minutes.
Without the ingame "cheat" I'm not able to beat the anchor.
And nothing is helping, I tried everything I found. :(
Very frustrating, cause it's not only the fight in the main game, it's also the fight in SHÜM2 in the DLC, that crashes.
I wonder why the version on Epic has no problem with this fight?
Post edited February 22, 2022 by happymichi
high rated
avatar
RogerRamjets: What worked for me was setting to the process affintiy in taskmanger for game to the first 4 cores.

I think there a deadlock condition occurring due to crappy multthreaded programming.
This worked for me as well, no need to downgrade graphics settings or PhysX to CPU.

For those not clear on how to do this, all you need to do is:

1. Start Game
2. Open task manager (CTRL+SHIFT+ESC)
3. Right click Game_rmdwin10_f.exe > "Go to details"
4. Right click Control_DX12.exe > "Set affinity"
5. Untick <All Processors>
6. Tick first four CPU Cores (0 to 3)
7. Click OK
8. Profit

I found I only needed to do this for the Anchor boss fight, when you restart game the above will be reset back to <All Processors>

If you want there is a video on finding the optimal cores to use, but basically the cores need to be on the same CCD/CCX: https://www.youtube.com/watch?v=m9m_YkiBKtE
avatar
RogerRamjets: What worked for me was setting to the process affintiy in taskmanger for game to the first 4 cores.

I think there a deadlock condition occurring due to crappy multthreaded programming.
avatar
teatime69: This worked for me as well, no need to downgrade graphics settings or PhysX to CPU.

For those not clear on how to do this, all you need to do is:

1. Start Game
2. Open task manager (CTRL+SHIFT+ESC)
3. Right click Game_rmdwin10_f.exe > "Go to details"
4. Right click Control_DX12.exe > "Set affinity"
5. Untick <All Processors>
6. Tick first four CPU Cores (0 to 3)
7. Click OK
8. Profit

I found I only needed to do this for the Anchor boss fight, when you restart game the above will be reset back to <All Processors>

If you want there is a video on finding the optimal cores to use, but basically the cores need to be on the same CCD/CCX: https://www.youtube.com/watch?v=m9m_YkiBKtE
It actually works for me. Thanks a lot teatime69!
I think this is simply a game bug and has nothing to do with affinity/resolution/graphics settings/priority/physx/drivers/overclocking etc. I tried a bunch of these posted fixes and at first, none of them worked. Then the affinity trick suddenly started working. I then restarted the game without the affinity mask and IT STILL DIDN'T CRASH.

So I got curious and did a bunch of tests on when the crash would happen. Turns out the ONLY factor is whether the boss is shooting the clocks at the hiss. Doesn't matter if it's the ones on the ground or flying ones. As soon as the clocks are about to hit a hiss = crash.

I think the reason so many people have so many different fixes for this is because it's just placebo - it's a 1 in 4 chance that boss is spewing clocks at the first wave of hiss, and after the first wave, it's pretty easy and natural to kill them before the clock spew. And changing graphics settings/affinity etc could be affecting the game's RNG so that it doesn't spawn hiss in the path of the clock spew.

Anyway, TLDR, just kill the hiss asap and you won't crash. If you're too low level turn on the one hit kill cheat.
My experience tallies with allenv30's assessment a few posts back. I was happily able to solve the problem from the (dx12 version) game's option menu by:

*changing the resolution to 'Windowed' 1920 x 1080
*Disabling DLSS
*Setting all ray-tracing options to 'Off'.

Everything went smooth as mah butt after that, changed the settings back after the fight.
Saw many hiss get destroyed by clocks during the course of the fight, so the previous post (jarghau) may not always be true...


My system:
Win 10 Home 64-bit (Version 21H2)
DirectX 12
16GB RAM
NVIDIA GeForce RTX 2070 Super 16GB
i7-10700KF CPU @ 3.80GHz