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 was playing the game fine until I reached the Manhattan mission. Then when I entered the subway there I got killed and the game crashed with a "Could not write crash dump" error message.

Now when I open the game again and click "continue" or load my latest save file it will instantly crash with the same error message over and over and over. Other people are also reporting the same issue on the S***m forum of the game.

I already used the "Verify/Repair" function of GOG Galaxy to see if there was anything wrong but that did not help to fix this issue. Looks like I won't be able to continue my playthrough until this problem is fixed. This game requires another patch just like "The New Order" did.
Don't you have any previous savegame you can turn to? And what about autosaves? Shouldn't there be at least one created upon every new level beginning?
avatar
deus-ex-: Don't you have any previous savegame you can turn to? And what about autosaves? Shouldn't there be at least one created upon every new level beginning?
Yes I had two autosaves and the older one still worked so I loaded that one. I've also turned off "Async compute" in the Advanced options and over the 4 hours I played then I had no random crashes or crashes when loading the latest save file. Maybe that option causes issues on older GPUs like mine (GTX 1060 6 GB). I'll have to play more and see if it will stay this way.
I investigated a little regarding Wolfenstein II and async compute. The v1.07 update changelog from November, 6th 2017 states: "Async compute temporarily disabled until driver fix available". Bethesda/Machine Games never released another update after that.

You seem to have identified the root cause of the issue. I haven't played the game yet, but I will keep this setting in mind when I'm going to do so.
avatar
deus-ex-: You seem to have identified the root cause of the issue. I haven't played the game yet, but I will keep this setting in mind when I'm going to do so.
Unfortunately this doesn't seem to 100 % fix this issue. I'm able to play but once I go back to the main menu and exit the game the familiar "Could not write crash dump" error message appears again. Luckily it happens after I saved so it doesn't seem to corrupt my save file(s). It's still annoying though and I wish MachineGames would give a fuck and fix this issue.

EDIT: On my first District side mission the game decided to crash randomly again. Same error message. I've forwarded this to the Bethesda support now.

EDIT 2: I lowered the framerate limit in the advanced options by a little and now I got no crash during gameplay or when I closed the game. I did at least 3 Enigma code side missions without any issues (no ""Could not write crash dump" message this time).
Post edited January 02, 2021 by Berzerk2002
Thanks for the feedback. This surely will help me and others when facing similar issues with this game.
The framerate limit seems to be the cause. I had no "Could not write crash dump" crashes anymore since I lowered it to something below 100 fps (e.g. 95 fps). To me it seems that either my CPU is too old and can't handle this game at a triple-digit framerate anymore or the game has issues with that.

I'm still in contact with the Bethesda support regarding this whole situation. When I got any new insights I'll post them here.
For me this crash only occurs when picking up collectables and not every time. Often only if I click J to view the item immediately, as well.
I had this twice so far, and I'm playing on Steam. I thought this is a new driver issue, but now I see this topic from December 2020.

It's irritating, because my latest progress wasn't saved after crash.

My specs are: Ryzen 3700X, 32 GB RAM 3200 MHz, RTX3070, Win10 with latest update.