Game keeps crashing at the VERY end

[KingOfMarz14]

So I bought Deathloop on sale and lets just say that it did not disappoint. Its been the most fun I've had with a game this year. But I have a MAJOR problem. Every single time I finally beat the game, and the cut-scene plays out, it immediately crashes. I did both endings and the same thing happens. So what i'm trying to say is that I can't beat the game. I'm going to try to do it again while I wait for people to respond to this.

[Skeeter]

I don't have a solution either but I have this exact issue. lowering VRAM usage, general settings, turning off vsync etc all did not work to solve this. For reference I played the entire game with vsync on and very high graphics preset with 0 crashes.I have never made it through the last cutscence without the game fully crashing in 5 attempts

[KingOfMarz14]

Also update, I tried it 4 more times doing each ending twice, I looked up the error code and I did the "fix" for it but it did nothing. I literaly don't know how its possible.

[Mirage à trois]

Same issue. The worse part is the whole entire day resets after the lockup, that is, if you don't suffer hard drive/ssd corruption from having to hit the reset button.

[Skeeter]

Actually for me it processes as completing the ending you just dont actually see it. I got the achievement for beating the game but "play it again, Colt" is impossible due to not continuing over to the next day in one unbroken session

[Evangelion]

I have the same issue but got the achievement as well, I tried to beat it 4 times and it consistently crashed when the credits were supposed to be played. If you go to the main menu and click credits it will crash everytime you do so meaning the credits are causing the crash. I haven't found a single solution to fixing it.... so guess this is it for now

[adamsan]

Same happening here with latest AMD drivers for Radeon 6600

[GravyRobbers97]

Joining the party to say the same thing literally just happened to me. AMD 6700 XT.

[Dexxter]

I dunno if this is still usefull for you, but Steam's "Verify local data" fixed it for me