what is "could not write crash dump"

[白白]

Whenever I try to open the game. it says "could not write crash dump"

I have updated to 388.10 and all other things perfectly work. I am just confused that why the officuals don't do anything to fix this problem since so many poeple are facing the same questions.

Do they even read the comments for god's sake

[Q]

I have the same ♥♥♥♥♥♥♥ problem

[crmfghtr]

This is ridiculous, do they not test this on multiple PC platforms? Shame on you! Here is my crash dump info. Winsock Initialized
idCommonLocal::Init() time 20: 0.063s
------ Initializing File System ------
Current search path:
- C:/Users/scott/SAVEDG~1/MachineGames/Wolfenstein II The New Colossus/base/
- C:/Program Files (x86)/Steam/steamapps/common/Wolfenstein.II.The.New.Colossus/base/
------ File System initialized.
WARNING: ReadJsonFile: could not read file: packagechunklist.json
Executing build.cfg...
------ Command Line ------
"C:\Program Files (x86)\Steam\steamapps\common\Wolfenstein.II.The.New.Colossus\NewColossus_x64vk.exe"
------ CPU Information ------
1 CPU package, 4 physical cores, 8 logical cores
2195 MHz Intel CPU with MMX & SSE & SSE2 & SSE3 & SSSE3 & SSE41 & SSE42 & AVX & HTT
32768 kB 1st level cache, 262144 kB 2nd level cache, 6291456 kB 3rd level cache
8096 MB System Memory
idCommonLocal::Init() time 30: 0.069s
idLib::SetProduction( PROD_PRODUCTION )
idCommonLocal::Init() time 40: 0.295s
------- Initializing renderSystem --------
PreliminaryRenderSetup
...registered window class
-------------------------
Application Info
-------------------------
App : Wolfenstein II The New Colossus - 1.0.2
Engine : idTech - 6.5.0
-------------------------
Instance Extensions
-------------------------
+ VK_KHR_surface
+ VK_KHR_win32_surface
+ VK_KHR_get_physical_device_properties2
WARNING: No address, error: 126
WARNING: No address, error: 126
WARNING: No address, error: 126
? @ 0x4104c40d( ) + bytes () : ** UNKNOWN **( ** FUNC_PARAM_ERROR ** )
? @ 0xfffffffe( ) + bytes () : ** UNKNOWN **( ** FUNC_PARAM_ERROR ** )
? @ 0x07b2f620( ) + bytes () : ** UNKNOWN **( ** FUNC_PARAM_ERROR ** )
FATAL ERROR: vkEnumeratePhysicalDevices failed with error (VK_ERROR_INITIALIZATION_FAILED)
TIMER: idRenderSystemLocal::Init() took 1517.9301 ms


idRenderSystem::Shutdown()
log file 'qconsole.log' opened on Sun Oct 29 18:49:32 2017

CrashHandler: Storing data and writing local report.
WARNING: No address, error: 126
idStackTracer::GetSource: Failed

[NoobKiller2017]

Try various methods online reinstall game N times, reshipment graphics driver N times, eventually successful environment is like this:
1) graphics driver 388.10 (2) must not preloading version game 3. In my computer, to disable the core graphics in the equipment management
4. Into the game found resolution problem please set had to be set in full screen mode. Ps: my computer is AlienwareR6 gtx1080. The hope can help you.

[hotdogtin]

OK, I had the same fault. I'd installed the latest updates and Nvidia driver 388.13, problem still there.

I've found a fix, well, one that worked for me.

You need to enter the compatibility mode for the application. Right click on the EXE, select properties and then compatibility.

Then you need to select "Overide high DPI scaling behaviour scaling performed by application"

Then apply and run the game.

The issues are caused by 1440p and 2160p monitor users having custom desktop size and font scaling.

[cyrosystems]

I have the same problem running 388.0 driver, I pre-loaded the game. Tonight tried to play it for the first time and this. Not impressed.

[ct_kamenovski]

I dont get it... How can an update ♥♥♥♥ up this game... It is an update like UP DATE not DOWN DATE... Wtf?!?!? The game was working fine but after this driver update it starts to show me this error "cannot write crash dump". It is doing this in game or when I am ALT + TAB-ed. WASNT DOING THIS AT ALL BEFORE. WTF?!?!?? I repeat IT WAS WORKING BEFORE!!! Sorry I am realy pissed off !!!

[ZaXaR]

Crash dump not writing crash:
only manual video driver installation did help in my case.

[Iceaganctor]

http://steamcommunity.com/app/612880/discussions/0/1479856439044448702/ try this

[cyrosystems]

Tried everything I've found including the latest Nvidia driver, disable steam overlay etc... Paid for this game about a week ago and still can't play it. Steam should not allow titles with problems like this to be listed in the store.

[Str1ker878]

引用自 LAOBAI ur father：

引用自 MAXMANUS：

Same problem here waiting for fix

nOW I am seriously thinking about refunding lol

Do it.

[cyrosystems]

I'm thinking of getting a refund then buying this for half price on sale sometime in the future when the bugs have been fixed. I paid $79 USD for a title I can't even play and from what I've read has quite a few other issues.

[Str1ker878]

引用自 cyrosystems：

I'm thinking of getting a refund then buying this for half price on sale sometime in the future when the bugs have been fixed. I paid $79 USD for a title I can't even play and from what I've read has quite a few other issues.

Do it. That's the least you can do to attract their attention to current issues with the game.

[cyrosystems]

I've done it, my refund request is in. Such a shame, I really enjoyed the previous Wolfenstein titles.

[白白]

引用自 cyrosystems：

I've done it, my refund request is in. Such a shame, I really enjoyed the previous Wolfenstein titles.

i thought the exact same day. THe company just destroyed their own game because of some rediculous problems

[cyrosystems]

Just reporting that I successfully received a refund.