KillingFloor2 crash - Game .exe has stopped working or hang on launch

The most common cause of this is corrupt files in the user directory or missing prerequisite files. Please try the following:

If you run security software such as an anti-virus or firewall (and other similar software), make sure the game is on any allowed/ignore list. If the game starts to misbehave after an update, try removing and re-adding the game to any such lists.

For the best connection results, please add these IPs to any security software permission/exclusion list:
analytics.tripwireinteractive.com
tripwireinteractive.com
playfabapi.com
epicgames.dev

Common Solutions

Corrupted Configuration:

1. Navigate to: C:\Users\[your name]\Documents\My Games.
2. Delete the "KillingFloor2" folder.
3. Try playing the game now.

Irregular Compatibility Setting:

1. Navigate to Steam\steamapps\common\killingfloor2\Binaries\Win64.
2. Locate the KFGame.exe and right-click it.
3. Now select "Properties".
4. Click on the "Compatibility" tab.
5. If checked, uncheck "Run this program in compatibility mode".
6. If checked, uncheck "Run in 256 colors".
7. If checked, uncheck "Run in 640 x 480 screen resolution".
8. If checked, uncheck "Disable visual themes".
9. If checked, uncheck "Disable display scaling on high DPI settings".
10. If checked, uncheck "Run this program as an administrator".
11. Click "Apply" to apply changes".
12. Click "OK" to close the window.
13. Try playing the game now.

Device Detection Failure:

1. Disconnect any xbox, playstation, VAKOSS, DS2 or mayflash controllers. This includes usb adapters.
2. Try playing the game now.

For users who have a graphics chip built into their CPU from Intel or AMD, make sure that the game is set to launch with your dedicated GPU via the video card control panel software that comes with it. The game does not support CPU graphics chipsets.

Nvidia - Follow the instructions below to change the default graphics processor:

1. Open the NVIDIA Control Panel.
2. Click the Manage 3D Settings link.
3. Click the Global Settings tab.
4. In the Preferred graphics processor drop down menu, select “High-performance NVIDIA processor).

AMD

1. If your Catalyst Control Center has the Switchable Graphics tab go there and browse to locate vngame.exe and set it for High Performance

Improper Physx Installation:

1. Go to your control panel for add/remove programs
2. Uninstall "NVIDIA Physx".
3. Then navigate to: \Steam\steamapps\common\killingfloor2\_CommonRedist\PhysX\9.14.0702
4. Run the Physx installer.
5. Try playing the game now.

We have also seen some cases where doing a clean install of the PhysX driver (uninstall completely and reinstall the latest: http://www.nvidia.com/object/physx-9.15.0428-driver.html ) has helped.

Improper Microsoft C++ Redists Installation:

1. Go to your control panel for add/remove programs.
2. Uninstall all versions of 2010 Microsoft C++ Redistribs.
3. Uninstall all versions of 2012 Microsoft C++ Redistribs.
4. Navigate to: Steam\steamapps\common\Steamworks Shared\ _CommonRedist\vcredist
5. In the 2010 folder, install the x64 version, and right-click run as admin.
6. In the 2012 folder, install the x64 version, and right-click run as admin.

Hidden Errors:

1. Try running the KFGame.exe as an administrator.
2. Sometimes this will cause a hidden error to appear.
3. Navigate to Steam\steamapps\common\killingfloor2\Binaries\Win64.
4. Locate the KFGame.exe and right-click it.
5. Now select "Run as Administrator".
6. If you get an error about a missing .dll, most likely you are having Microsoft C++ Redist installing problems.
7. If you get an error about "0xc000007b", skip to the end of the advanced solutions and read the directions specifically for that.

Deep Cache Verification:

1. Navigate to Steam\steamapps\common\killingfloor2
2. Delete the binaries folder.
3. Navigate to Steam\steamapps\common\killingfloor2\KFGame\BrewedPC
4. Delete the file: GlobalShaderCache-PC-D3D-SM4.bin
5. Delete the file: GlobalShaderCache-PC-D3D-SM5.bin
6. Go to Steam Library.
7. Right-click on Killing Floor 2.
8. Select Properties.
9. Go to Local Files tab.
10. Click the button "Verify Integrity of Game Cache...". This should take 10-15 minutes.
11. Try playing the game now.

Advanced Solutions:

Eliminating Variables:
If none of the common solutions worked for you then let's go ahead and eliminate some variables. Please disable your firewall and/or antivirus for the next thirty minutes. After that is done, let's force the game to launch in a dx10, windowed mode.

1. Go to your Steam Library.
2. Right-click on Killing Floor 2.
3. Select Properties.
4. You are on the General tab. Click on "Set Launch Options".
5. Type in: -windowed -dx10
6. Click OK.
7. Try playing the game now.

Remote Desktop Configuration:
If you recently installed a Window's 10 update and you see an error in your logfile stating that "this application cannot be run over a remote desktop configuration." then you should do the following:

1. Change your desktop resolution.
2. Reboot your computer.
3. Change your desktop resolution back.
4. Try playing the game now.

Missing nvcuda.dll:
If you see errors in your logfile relating to a missing nvcuda.dll, then you should do the following:

1. Navigate to C:\Windows\SysWOW64.
2. Locate the file "nvcuda.dll" and right-click it.
3. Select "Copy".
4. Navigate to C:\Windows\System32.
5. Right-click inside this folder to paste your copied file.
6. Try playing the game now.

Serial Size Mismatch:
If you see errors in your logfile relating to a "[file name] Serial Size Mismatch", then you should do the following:

1. Go to Steam Library.
2. Right-click on Killing Floor 2.
3. Select Properties.
4. Go to Local Files tab.
5. Click "Browse Local Files".
6. Perform a search for the [file name]. Do not include the file's extention when you search (omit .stg44, etc).
7. Once located, delete that file and close the window.
8. Now you're back on the Killing Floor 2 properties. Click the button "Verify Integrity of Game Cache..." This should take 10-15 minutes.
9. Try playing the game now.

ReadFile Beyond EDF:
If you see errors in your logfile relating to a "EOF [long number]/[long number]", then you should do the following:

1. Go to Steam Library.
2. Right-click on Killing Floor 2.
3. Select Properties.
4. Go to Local Files tab.
5. Click "Browse Local Files".
6. Navigate to the folder that houses the file.
7. Once located, delete that folder and close the window.
8. Now you're back on the Killing Floor 2 properties. Click the button "Verify Integrity of Game Cache..." This should take 10-15 minutes.
9. Try playing the game now.

Bad Name Index:
If you see a reference to "Bad name index [numbers]" in your logfile, then you should do the following:

1. Go to Steam Library.
2. Right-click on Killing Floor 2.
3. Select Properties.
4. Go to Local Files tab.
5. Click the button "Verify Integrity of Game Cache...". This should take 10-15 minutes.
6. Try playing the game now.

Fatal Error Problem 1:
If you see a reference to "=== Critical error: === Fatal error!" in your logfile, this usually means there is some sort of driver conflict happening. Windows 10 automatically pushes updates sometimes so your computer may have changed overnight. You should do the following:

1. Find out what NVIDIA driver version you curently have.
2. Find out what the newest NVIDIA driver version is.
3. If you are not on the newest, uninstall your current NVIDIA drivers and upgrade to the newest version.
4. Try playing the game now. If that doesn't work then:
5. Since you are on the newest GPU version, locate the oldest version available to your GPU from NVIDIA.
6. Uninstall your current NVIDIA drivers and downgrade to the oldest version.
7. Try playing the game now.

Fatal Error Problem 2:
If you see a reference to "=== Critical error: === Fatal error!" in your logfile followed up with this specific set of text:

Address = 0x76ad0944 (filename not found)
Address = 0x5bf168 (filename not found)
Address = 0x5880bed0 (filename not found)
Address = 0x1 (filename not found)
Address = 0xf34bca97 (filename not found) [in D:\Windows\system32\dxgi.dll]
Address = 0xf34c2dae (filename not found) [in D:\Windows\system32\dxgi.dll]

You should do the following:

1. Please reference the known software conflicts section.

Assertion Failed:
If you see something around the lines of: "Critical: appError called: Assertion failed" then the most likely culprit is your crossfire is preventing the game gathering all necessary files during startup.

1. Find out what GPU you are using.
2. Figure out how to disable crossfire or force use a single gpu.
3. Try playing the game now.

Corrupt Favorites (crashing on menus):
If you are crashing when clicking on menu's then it is likely you have corrupted weapon favorites for some reason. If you see errors in your logfile relating to "Adding Weapon to favorites: string_#", then you should do the following:

1. Disable Steam Game Cloud Storage for Killing Floor 2.
2. Turn off Wi-Fi or unplug your ethernet cable.
3. When you launch Killing Floor 2 it should look like everything has "reset".
4. Now quit your game and turn on your Wi-Fi or plug your ethernet back in.
5. Launch Killing Floor 2.
6. Minimize it and activate the steam cloud storage.
7. Taken from thread: https://steamcommunity.com/app/232090/discussions/1/1694923613878834990/

0xc000007b Error:
If you are getting "0xc000007b" error when you're running your KFGame.exe as an administrator, see below:

1. Download Dependencies (https://github.com/lucasg/Dependencies/releases) or Dependency Walker (http://www.dependencywalker.com/)
2. Launch Dependencies/Dependency Walker and hit the "open" icon.
3. Navigate to G:\Steam\steamapps\common\killingfloor2\Binaries\Win64
4. Select KFGame.exe.
5. In the middle of the screen you'll see a column for CPU. Click it to sort all the files by it.
6. Right-click on a random row and select "show full file path".
7. Scroll either all the way up, or all the way down, looking for any files that have "x86" in the CPU column. If they are API or EXT .dlls you can skip them. You can also skip the one named nvcuda.dll. Note the filepath it is in.
8. Download that .dll from online. Make sure it is the x64 version. Please be careful what site you use and do a virus check on your downloaded file if necessary.
9. Replace the existing .dll in the appropriate folder.
10. Rinse and repeat. Feel free to try clicking play after each one.

Crashing frequently on map change:

1. Navigate to your ...\Documents\My Games\KillingFloor2\KFGame\Config\... directory
2. Open your KFEngine.ini
3. Run a search for a line containing MaxObjectsNotConsideredByGC=179220.
4. Try changing the value from 179220 to 33476, making sure not to change the values of any other functions. Afterward, save the file and attempt to play two continues matches.

Known Software Conflicts
The following softwares may or may not interfere with Killing Floor 2:

• MSI Afterburner
• RivaTuner
• DAEMON Tools
• DAEMON Tools Lite
• CAM Software
• PlayClaw
• Mirillis Action
• Dxtory: Possible solution: Go to the "Advanced" Tab in DxTory and under "Hook Option" tick the "Delay Hook" box and set a timer of around 6 seconds or more depending on when your game stops crashing. credit to CryCel for finding it.
• FRAPS
• D3Dgear
• RTSS: Possible solution: Set Custom Direct 3D Support to ON.
• Medal.tv clip software

If the game prompts you to send in a bugsplat error report, please let it
do so along with your email address. This will help us diagnose and
fix the crash (if it isn't fixed by any of the above). We are
often unable to provide any further suggestions or direct help as we
continue to look into player submitted reports to determine cause and
work on fixes.