Fixes & Performance

KF2 Won't Start or Crashes on Launch: Full Troubleshooting

This is a long checklist for Killing Floor 2 on Windows that will not launch or crashes right after the splash screen. Try the common solutions one at a time, in order, and test the game after each. For a specific error see also 0xc000007b fix and the startup FAQ.

Common solutions

Corrupted configuration. Open C:\Users\<name>\Documents\My Games and delete the KillingFloor2 folder. The game rebuilds it.

Irregular compatibility settings. In Steam\steamapps\common\killingfloor2\Binaries\Win64 right-click KFGame.exe, open Properties, then the Compatibility tab. Uncheck every box that is ticked: compatibility mode, 256 colors, 640 x 480 resolution, disable visual themes, disable display scaling on high DPI, and run as administrator. Apply, OK, retry.

Device detection failure. Unplug Xbox, PlayStation, VAKOSS, DS2 or Mayflash controllers, including their USB adapters.

Wrong GPU in use. Open the NVIDIA control panel from the taskbar, go to Manage 3D Settings, then the Program Settings tab. With two groupings you need no change. With three (#1, #2 and #3), add Killing Floor 2 to group #1 and set it to the high-performance GPU. Make sure dxcpl.exe is not running for KF2 if you know that tool.

Broken PhysX install. Uninstall "NVIDIA PhysX" in Add/Remove Programs, then run the installer from Steam\steamapps\common\killingfloor2\_CommonRedist\PhysX\9.14.0702.

Broken Microsoft C++ redistributables. Uninstall every 2010 and 2012 Microsoft C++ Redistributable. Then from Steam\steamapps\common\Steamworks Shared\_CommonRedist\vcredist install the x64 version from the 2010 folder and the x64 version from the 2012 folder, each run as administrator.

Hidden errors. Run KFGame.exe from Binaries\Win64 as administrator; this can reveal an error message. A missing .dll message usually means the C++ redistributable problem above. A 0xc000007b error is covered at the end of the advanced section.

Deep cache verification. Delete the Binaries folder in the game directory, then delete GlobalShaderCache-PC-D3D-SM4.bin and GlobalShaderCache-PC-D3D-SM5.bin from KFGame\BrewedPC. In Steam, open the game's Properties, Local Files, "Verify Integrity of Game Cache..." (10 to 15 minutes), then retry.

Advanced solutions

Eliminate variables. Disable the firewall and antivirus for thirty minutes, then set the Steam launch option -windowed to force a windowed DX10 launch.

Find the crash log. C:\Users\<name>\Documents\My Games\KillingFloor2\KFGame\Logs\Launch.log holds the latest log. To ask for help, paste its contents on pastebin.com, generate the paste and post the link in a new thread in the Bug Report section of the community hub.

Common log messages and their fixes:

Log messageWhat to do
"this application cannot be run over a remote desktop configuration" (after a Windows 10 update)Change the desktop resolution, reboot, change it back
Missing nvcuda.dllCopy nvcuda.dll from C:\Windows\SysWOW64 to C:\Windows\System32
"[file name] Serial Size Mismatch"In Steam, Browse Local Files, search the file name without extension, delete it, then verify the game cache
"EOF [number]/[number]" (ReadFile beyond EOF)Delete the folder containing that file via Browse Local Files, then verify the game cache
"Bad name index [numbers]"Verify the game cache
"Critical error: Fatal error!"Driver conflict: update the NVIDIA driver to the newest; if already newest, install the oldest driver available for your GPU
Fatal error followed by addresses ending in dxgi.dllSee the software conflicts list below
"Critical: appError called: Assertion failed"Usually CrossFire blocking file loading: disable CrossFire or force a single GPU
"Adding Weapon to favorites: string_#" (crashes on menus)Corrupted favorites, see below

Corrupt favorites (crash when clicking menus). Disable Steam Cloud storage for KF2, turn off Wi-Fi or unplug ethernet, launch the game (everything should look reset), quit, reconnect to the network, launch again, minimize it and re-enable Steam Cloud.

0xc000007b error. When running KFGame.exe as administrator gives this error: download Dependency Walker, open KFGame.exe from Binaries\Win64, sort by the CPU column, and look for files marked x86 (skip API and EXT dlls and nvcuda.dll). Note the path, download the x64 version of that .dll from a trustworthy source (scan it for viruses), replace the file and repeat for the others, trying the game after each.

Known software conflicts

These programs may or may not interfere with KF2:

  • MSI Afterburner
  • RivaTuner (try stealth mode)
  • OneDrive (a problem if it redirects or alters your My Documents path)
  • DAEMON Tools and DAEMON Tools Lite
  • CAM software
  • PlayClaw
  • Mirillis Action
  • Dxtory (in the Advanced tab tick "Delay Hook" under Hook Option and set about 6 seconds or more)
  • FRAPS
  • D3Dgear
  • RTSS (set Custom Direct 3D Support to ON)
  • Roccat Isku and Swarm FX software and drivers
  • Logitech Gaming Software 8.82.151 (install version 9 instead)

FAQ

What is the first thing to try when KF2 crashes on startup?
Delete the KillingFloor2 folder in Documents\My Games, so the game regenerates a clean configuration.
Where is the KF2 crash log?
Documents\My Games\KillingFloor2\KFGame\Logs\Launch.log holds the most recent crash log.
Which programs conflict with KF2?
Overlay and capture tools such as MSI Afterburner, RivaTuner, Dxtory, FRAPS, Mirillis Action, DAEMON Tools and some Roccat or Logitech software.