scroll down

Call of Duty: WW2 Errors, Crashes, Black Screen, Multi-Monitor Issue And Fixes

Call of Duty: WW2 has launched for PC and consoles, however, PC users have been experiencing some Call of Duty: WW2 errors which are ruining their experience. Here we will discuss all these issues that PC users have been experiencing and will provide with a possible solution or workaround.

Call of Duty: WW2 is the latest entry in the long-running franchise. The game is developed by Sledgehammer Games who previously worked on Call of Duty: Advanced Warfare. Call of Duty: WW2 takes the series back to its roots with its boots on the ground gameplay.

For more help on Call of Duty: WW2 also read our Memento Locations Guide, Zombies Final Reich Guide, and Zombies Final Reich Weapons Locations Guide.

Call of Duty: WW2 Errors, Crashes, And Fixes

Following are the Call of Duty: WW2 errors that PC users have been experiencing and we will also provide a possible solution or workaround.

Call of Duty: WW2 – s2_sp64_ship.exe Crash Error
This is among many Call of Duty: WW2 errors that players have been experiencing which is not letting them start the single-player campaign. However, the issue might be with the OS you are trying to run the game on. Just update your Windows OS and the issue should be resolved.

Call of Duty: WW2 – Game Crashing
Some PC users have been experiencing crashes while trying to play the game. Make Sure you GPU drivers are up-to-date as older drivers might not be compatible with the game. Also, make sure to close all the unnecessary background processes before starting the game as they can also cause these crashes.

Call of Duty: WW2 – Multi-Monitor Issue
Some PC players who are using multi-monitor setup are not able to play the game on the main display as the game only starts in the secondary display. The solution to this problem is quite simple and should resolve the issue.

All you have to do is go to the video settings and select “Fullscreen” Then press “ALT+Enter” which will put the game in the windowed mode on the secondary screen. Now drag the window to your Primary monitor and then change the video setting to whichever option you like and again press “Alt+Enter” and the game should start on the primary monitor from now on.

Call of Duty: WW2 – Low FPS/Stuttering/Bad Performance
PC gamers are no strangers to game not running well on their systems. Make sure you have installed the latest drivers for your GPU as your old drivers might be incompatible with the game and at least download the Game Ready drivers for Call of Duty: WW2 as they bring optimizations specific to the game.

Another reason you game has bad performance might be because your system is using the integrated GPU instead of dedicated one. Make sure your system is using the external GPU to fix this issue you can either do it through Nvidia control panel or through your Bios.

Another, reason for the stuttering might be your HDD, as there is a chance that a program in the background might be using it too much which in some cases can cause game stuttering. Open up your task manager, and close unnecessary programs and the issue should resolve.

Call of Duty: WW2 – Screen Flickering
This is another one of the Call of Duty: WW2 errors that players have been facing that causes the screen to flicker as soon as the game starts and this is happening majorly when gamers try to play the single-player campaign. While there is no solution for that but there is a workaround that should resolve the issue.

Start the game and if you see flickering then just press “ALT + Enter” this will put the game in the windowed mode as for some reason the Fullscreen option is causing this issue. This should resolve your issue.

Another reason why you are seeing the green flicker might due to the conflict with the game’s refresh rate and your monitors. Just go to the video settings and select another refresh rate which should resolve the issue.

Call of Duty: WW2 – Audio Issues/No Sound
Some PC users have noted that there is no sound in-game which is obviously very annoying. Go to Playback Devices by right-clicking on the sound icon in the bottom left corner of the desktop.

A list of sound devices will be displayed here, all you have to do is disable all other sound devices except for the one that you want to use and the issue should resolve and this solution might also work for those who are using integrated sound cards.

Also, some players might be experiencing strange buzz with the game sound which makes playing the game difficult. The solution to this issue is to playback devices by right clicking the audio icon in the bottom right corner, select the audio device that is enabled, for most it will be “Speakers”, and open properties. Select “Advanced” and set the audio quality.

There will be quite a few options and not every option will resolve this issue and you will have to experiment a little bit. This should resolve the issue.

Call of Duty: WW2 – Missing “.dll” Files
This is a common error that occurs mostly for Windows 7 users due to the lack of the updated OS or Visual C++ Redistributable not being up-to-date. All you have to do is update your OS and the issue will be resolved and if the OS is updated and the issue persists then just install the Visual C++ 2015 Redistributable Update 3 which will automatically update the file or will put it in your system if it is missing.

Also, if you are seeing the error for a missing “SteamAPI.dll” then try re-installing Steam on your PC and this should resolve the issue.

Call of Duty: WW2 – No Display/Black Screen
This is another one of Call of Duty: WW2 errors that players have been experiencing. The issue that players have been experiencing is that when they play the game in Fullscreen mode the screen goes black but it runs fine in Windowed mode.

The issue might be that the game has selected a higher resolution than your monitor’s native resolution by default. Just go to the video settings and select your native resolution and the game will work fine in Fullscreen mode.

If you are facing any other Call of Duty: WW2 errors not listed here or have a better solution to an error, let us know in the comments!