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:

1) Delete your documents/my games/Killing Floor 2/ folder directory completely
2) Verify Steam cache. Right-click on KF2 in Steam Library > Properties > Local Files > [Verify Integrity]
2.1) For a deeper verification try deleting your steamapps/common/killingfloor2/binaries folder as well as the /KFGame/BrewedPC/ GlobalShaderCache and LocalShaderCache .bin and .upk files before you verify integrity
3) The game may be trying to compile shaders if it appears to hang on launch. You can check for this by looking for a shadercompiler.exe in your Task Manager. If you find it, waiting for the process to finish should allow the game to launch as normal.
4) Running the .exe redist files located in your SteamApps/common/killingfloor2/_CommonRedist location
5) Update any device drivers you have to the latest available
6) Disconnect USB controllers and other HID devices except for keyboard and mouse
7) Restart Steam client
8) Launch Steam (or set the game .exe) to launch as an Administrator
9) Turn off DxTory
10) Change your Steam avatar icon to a Steam default one

You will also want to try the following launch options (via Steam properties for the game):

-dx10
-windowed


If the game prompts you to send in a bugsplat error report, please let it do so. This will help us diagnose and fix the crash (if it isn't fixed by any of the above).


For those who have the 0xc000007b error we are doing further investigation on this. However we would like users to try reinstalling/repairing the following:

VC C++ Redist: https://www.microsoft.com/en-us/download/details.aspx?id=30679
DirectX: https://www.microsoft.com/en-us/download/details.aspx?id=34429
.net: https://www.microsoft.com/en-us/download/details.aspx?id=17718

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.

We are aware of at least one case where none of these seem to help and we are trying to gain access to a computer that has this issue so we can debug it. If you live in the Greater Atlanta area and have this issue, please let us know.