How to fix Wolfenstein II: The New Colossus random crashes, errors, or bugs and glitches

[enZar]

Update: Download the latest Nvidia or AMD drivers.

Update 2: The latest patch update has improved and resolved the issues, so ignore this guide

I have been playing the game for few hours and I have been experiencing some difficulties such as BSOD, random freeze after death, and some bug such as toggle duel wielding, the guns will appear invisible after toggle off, but the guns will appear when changing weapons. So it seems nothing has changed from the two previous games (Wolfenstein The New Order and The Old Blood) that had problem running the 64-bit version.
This is the guide to fix all the problems for Wolfenstein II: The New Colossus.

1. Go to the steam game directory where you have installed the game

2. Copy and paste NewColossus_x64vk in the game file

3. Rename it to NewColossus_x32vk

4. Create a text document called steam_appid

5. In that text document type 612880

6. Save the text document in the game directory

10. Make sure the executable lunch file is added to the steam library to choose the right file to launch it.

8. Launch the game in NewColossus_x32vk not NewColossus_x64vk

Do not delete NewColossus_x64vk or else it won’t work.
There should be option to allow to run the game at 32-bit or 64-bit version

Has this fix solved your problem? Let me know in the feedback section.
Thanks!

[rjdriver]

Has anyone tried this?

[Warlord1]

I haved a BSOD and fix it updating Radeon drivers,after that crash twice jumping to the helicopter.

[enZar]

rjdriver님이 먼저 게시:

Has anyone tried this?

The game was just fresh from release, but I'm hoping someone who has this sort of problem will try this method to fix the game.

[enZar]

Warlord1님이 먼저 게시:

I haved a BSOD and fix it updating Radeon drivers,after that crash twice jumping to the helicopter.

I get BSOD as well, until this method was the way to fix the problem, just like TNO and TOB

[гот-педовка]

wtf? Games still suport 32 bit today?

[enZar]

I'm not a dog님이 먼저 게시:

wtf? Games still suport 32 bit today?

The 64-bit version runs horrible, I'm not sure why its causing the issue but the 32-bit is the only way to fix the problem.

[Pagan Min - King of Kyrat]

I'm not a dog님이 먼저 게시:

wtf? Games still suport 32 bit today?

This is some kind of ♥♥♥♥♥♥♥♥ I guess... Even wolfenstein: New Order didn't supported 32 bit systems, so how part 2 can support? But we can check

[Pagan Min - King of Kyrat]

EnsarG님이 먼저 게시:

I have been playing this game for a while and I have been experiencing some difficulties such as BSOD and random freeze after death. I have noticed a bug to toggle duel wielding, when turned off, the gun will be invisible but the gun will appear when changing weapons. So it seems nothing has changed from the two previous games (Wolfenstein The New Order and The Old Blood) that had problem running the 64-bit version.

This is the guide to fix all the problems for Wolfenstein II: The New Colossus.

1. Go to the steam game directory where you have installed the game

2. Copy and paste NewColossus_x64vk in the game file

3. Rename the fle to NewColossus_x32vk (The game folder must have NewColossus_x64vk and NewColossus_x32vk)

4. Create a text document called steam_appid

5. In that text document type 612880

6. Save the text document in the game directory

10. Make sure the executable lunch file WolfNewOrder_x32 is added to the steam library to choose the right file to launch it.

8. Launch the game in NewColossus_x32vk not NewColossus_x64vk

Do not delete NewColossus_x64vk or else it won’t work.

The devs should add a option to allow us to run the game at 32-bit or 64-bit version

Has this fix solved your problem? Let me know in the feedback section.
Thanks!

Dude, I'm not yet saying you're a liarm but how the hell any game in 2017 could support 32 bit? Time od Win 32 has past somewhere in 2013.

[enZar]

If it was the same with TNO and TOB running the 64-bit, I would assume the game would not run well with the 64-bit version in the new colossus.

[enZar]

bump

[saaya]

10. Make sure the executable lunch file WolfNewOrder_x32 is added to the steam library to choose the right file to launch it.

how am i supposed to do that? 0_o

[enZar]

saaya님이 먼저 게시:

10. Make sure the executable lunch file WolfNewOrder_x32 is added to the steam library to choose the right file to launch it.

how am i supposed to do that? 0_o

There was a error in the guide (WolfNewOrder_x32 is is the wolfenstein the new order) of naming of the file. Thank you for that. To get the game into the steam library, go to add a game, under the section add non-steam game to select the launch file. Which is NewColossus_x32vk in the game folder.

[VonBartol]

It also work for "could not write crush dump"?

[saaya]

no matter what i do, run as admin etc, when checking taskmanager its still the 64bit executable running, not 32bit

[enZar]

Bart2000님이 먼저 게시:

It also work for "could not write crush dump"?

No