Windows Wolfenstein 2 doesn't start - error could not write crash dump

For some reason when I attempt to start the latest game in the Wolfenstein saga I get a box titled Crashinfo with the message Could not write crash dump with no other explanation.

Bethesda responded quickly but were effectively no help in saying that my hardware doesn't support it. Feedback from a fellow gamer suggests this isn't true (he's got it to work and we have the same board and processor, possibly same graphics too).

Here's the spec:
Asus Prime B350-Plus
Ryzen 3 1300X
16Gb DDR4 RAM (think its 1033Mhz)
7Tb drive space in total (no space issues on installed drive)
GeForce 1050Ti
Windows 10 x64
BitDefender Total Security (note I tried to disable this and it didn't work)

Nothing is overclocked. The only info I've found suggests some settings to change but they depend on me getting into the game to change them (or at least the ones I've found did...)

I've verified the game install through Steam, checked the drive for errors (all drives in fact), made sure the latest drivers are installed, Windows 10 up to date and still no progress.

Any suggestions? I've also tried running it as admin which was another suggestion I found and that had no effect.

 

Could you try installing it to a steam library on a different drive ? I'm wondering if it can't write the crash dump because some permissions have got messed up in the install folder.

 

I'll have a go. Even with virgin media it will still take hours. I doubt this is the cause though as lots of other games have no issues (Doom for example and the other Wolfenstein games).

That said, steam became a pain with having more than one steam library after a change. I complained and they wouldn't change it back but there is a way to add another steam library. I'll put it on another drive with loads of space and see what happens.

Thanks for the reply and watch this space!

 

A quick google has returned possible fix !

Delete the config file from the following folder "C:\Users\Username\Saved Games\MachineGames\Wolfenstein II The New Colossus\base\Wolfenstein II The New ColossusConfig.local". Restart steam and game

 

Thank you! Seems I'm not great at searching for fixes like this. I'll try it later.

 

Sadly the file doesn't exist but I have found the attached crash file which was originally a HTML file.

 

Yeah I don't think anyone will want to open that mate. Maybe paste the contents of the file into a separate post?

 

Won't want to open a text file do you mean? I'm not aware of any risk there but I'll have a go later at posting it as is often the norm on forums.

I also hope to test some options I've found during research.

 

Not so much the fact that it's a text file. Just a bit risky as the file could be anything really.

 

Copy paste of the file:

 

<PRE>
Callstack Function(desc) Line Bytes File Process Address
--------------------------- ---- ----- ---- ------- -------
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x2409ad11 ?
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x2409af51 ?
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x247af248 ?
** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x2409b030 ?

Register Info
---------------------------
EDI: 0x00007FFF247AF1D0 ESI: 0x0000000000000000 EAX: 0x0000000000000063
EBX: 0xAAAAAAAAAAAAAAAB ECX: 0x0000000000000076 EDX: 0x0000000000000000
EIP: 0x00007FFF2409AD11 EBP: 0x0000007B2C3F5D00 SegCs: 0x0000000000000033
EFlags: 0x0000000000010246 ESP: 0x0000007B2C3F4518 SegSs: 0x000000000000002B

Exception Info
---------------------------
ExpCode: 0xC0000005 (Access Violation)
ExpFlags: 0
ExpAddress: 0x00007FFF2409AD11

Build & Runtime Info
---------------------------
User: Paul
Version: 20180223-123524-78326_indigo-umber
File Path: C:\Program Files (x86)\Steam\steamapps\common\Wolfenstein.II.The.New.Colossus\NewColossus_x64vk.exe
System Time: 5/21/2018 22:36:02
Build String: 20180223-123524-78326_indigo-umber
VT File Path:
VMTR Override: generated/pagefiles
Launch Command: "C:\Program Files (x86)\Steam\steamapps\common\Wolfenstein.II.The.New.Colossus\NewColossus_x64vk.exe"

Memory Info
---------------------------
In Use: 31%
MB Physical RAM: 16320
MB Physical Free: 11131
MB Paging File: 40896
MB Paging Free: 34147
MB User Address: 134217728
MB User Free: 134213153

CPU Info
---------------------------
Num Packages: 1
Num Cores: 4
Num Logical: 4
CPU ID: Generic
CPU MHz: 3493

Forge Info
---------------------------
Binary Name:
Package Name:
Candidate Name:
Runtime UUID:

User Info: Paul
---------------------------
Repro Steps:


Details:



</PRE>

 

Still getting nowhere with this. There was a recent update by Bethesda which appeared to at least change the symptoms but it resulted in the same error. I don't see how hardware which does not allegedly have sufficient power could cause this error but it is basically what Bethesda said and they refused to help further.