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

×
Community
ControlCTD in Anchor fight(104 posts)(104 posts)
(104 posts)
Pages:
1
2
3
4
5
6
7
This is my favourite topic
Posted September 18, 2020
Having the same problem, tried the same options, nothing worked.
Send a ticket through 505 Support website.
Posted September 20, 2020
I managed to get through this boss fight by using only my telekinesis throw power and the standard service weapon (Grip). Using any other weapon type like Charge or Pierce would make the game crash (reproducible).
Posted September 21, 2020
Looks like a general issue. I had an issue when using seize to control guys to fight golden man for me. Had to turn things down to get past that fight. I haven’t upped it but now I have got the anchor fight and it crashes the moment the anchor attacks. And running gtx1080ftw, fast machine with 32gb ram.
Posted September 22, 2020
dude, i have the same issue (at the GOG version) and nothing works. But then i kill the Radeon overlay (in the task manager) so it doesn't appear if i click alt+R. And it helps! It didn't crush at the first attack even at high resolution\graphic.

Upd. Actually it crushes at ~5 min i fighting the boss, but i try to kill him faster
Post edited September 22, 2020 by xareh90
Posted September 26, 2020
avatar
Manaflower: Fortunately Anchor is optional, so I was able to beat the game ignoring it, but it's still a huge bummer.

Still, I experimented with it a little more and checking some videos about the fight in hopes of finding a solution, and the crash seems to coincide with the boss's attack.

My ability to debug this has reached its limit besides just changing my GPU driver (currently 452.06). If I have the energy, I guess I could try studio drivers since they're supposedly more stable, but there's nothing really pointing at it being driver issue (though I suppose it could be deeper seated issue).
avatar
argenisX: This must be an RTX specific bug, there's a lot more people having the issue.

The fixes for this are (and believe me this is a bit crazy)

1)Turning the audio to 0 on the settings of the game before entering the fight

2) Settings the resolution to less than the full screen resolution of your monitor

3) Playing the game in compatibility mode, specifically Windows Vista mode

Give those all together a try, that's a bit insane, considering that the boss itself is also kinda hard to beat until way later on.
It's not RTX specific. I have a non-RTX Nvidia-GPU (with the latest driver) and the same issue.
Posted September 29, 2020
Sigh, I tried every solution that was suggested but nothing helped. Still had this damn CTD once the Anchor does its first attack. So I finally gave up activated Assisted Mode + Instant Kill and finished the fight before it could do its attack. At least that helped.
Posted October 02, 2020
I just experienced this crash today after applying the patch. The crash happens about a minute into the fight. I did not get this far before the patch so I can't verify if it makes a difference or not. Intel i9 with a GTX 1660 and 32GB RAM. The rest of the game plays great, this is the first issue I've ran across. I'm going to wait and see if they can patch it, I'd rather not cheat except as a last resort.
Post edited October 02, 2020 by Reynard_Muldrake
Posted October 03, 2020
What worked for me was disabling the Nvidia Freestyle filters I had applied (or Reshade, in a more general case). Just setting Freestyle to off, worked perfectly. I haven't had problems with my filters (Sharpen + Curves) in any other part of the game.
Posted October 15, 2020
Saw today that they released an update.
It fixes the Anchor fight to a certain degree.
You can start the fight with whatever options you like,
but if Anchor fires to many attacks, the game crashes again.
I didn't count it, but I would say up to 10 attacks you have time
to defeat Anchor, after that the game will crash.
Post edited October 15, 2020 by GTrash81
Posted October 17, 2020
Hi guys,

I don'T know if anyone is still experiencing the issue, but one thing that worked for me is the combination of two settings.
Find the executable and right-clik on it -> properties -> compatibility

and the set the settings to

Windows Vista (service pack 2)

as well as

Disable fullscreen optimization.

Tried all the other tipps here, but that was the only thing that worked.
No more crashes since then.

Best regards,
Chris
Post edited October 17, 2020 by mansionmaniac
Posted October 19, 2020
Ryzen 3xxx CPUs seem to be the common denominator here.


Same exact issue on a 3080 FE with Ryzen 3700X. To zero in on the issue here let me clarify and say that this is not just an 'Anchor Boss crash' but SPECIFICALLY a consistent, unavoidable crash that always happens the exact moment that it begins spewing clocks from its mouth.

Have tried all proposed solutions on every forum and nothing works.

"The instruction at 0x00007FFA6326F42B referenced at 0x0000000000000000. The memory could not be read."
Post edited October 19, 2020 by InfiniteClouds
Posted October 19, 2020
Can you folks with this issue please post your full system specs so we can try and diagnose this? What version of Windows 10 are you using? I'm running a LTSC version -- are you? I noticed at least two other people who had this same exact issue had a Ryzen 3700X... do you? Or another Ryzen? What about your mothebroard? Also do you have any AV software (Bitdefender maybe?)

GPU doesn't seem to matter here.
Post edited October 19, 2020 by InfiniteClouds
Posted October 24, 2020
I tested with two different configurations,

with an AMD Rysen 5 3600 processor the game crash,
with an Intel I5-7300 HQ the fight of the anchor goes without problem.
Posted October 25, 2020
Fix courtesy of Obeliskoid:

There are two .dll files in the game directory.
platform_rdwin10_f.dll. (a bad opcode here is causing the crash)
and
platform_rdwin7_f.dll.
Back-up your rdwin10 file.
Rename platform_rdwin7_f.dll to platform_rdwin10_f.dll to overwrite the windows 10 file. This fixed the crash for me. Not sure if it breaks anything else but you could always put the original rdwin10 file back after the boss fight.
Posted November 02, 2020
Same to me
Pages:
1
2
3
4
5
6
7
This is my favourite topic
Community
ControlCTD in Anchor fight(104 posts)(104 posts)
(104 posts)