Dying Light

Dying Light

View Stats:
Devil `Legit Jun 24, 2015 @ 9:15pm
Solution to 0xc000007b error
Here is the solution to the 0xc000007b error, so far it seems to be working on most games that this error appears with.

Go here:
C:\Program Files\Steam\SteamApps\common\Dying Light\_CommonRedist\DirectX\Jun2010

Open all of the x64.cab and copy the files inside to
(probably only needs the .dll, however i used winrar and just extracted all of the .cab at once)

Here:
C:\Program Files\Steam\SteamApps\common\Dying Light

This should fix the error, if not, you may need to update your directx, .net framework, or vcredist.
Last edited by Devil `Legit; Jun 24, 2015 @ 9:28pm
< >
Showing 1-1 of 1 comments
BorisTheButcher Dec 2, 2015 @ 8:24pm 
I helped a friend fix this error today. There doesn't seem to be a comprehensive answer anywhere, but the 0xc000007b happens in many games. The error appears to hit especially people with AMD/ATI cards, or systems that used to have AMD/ATI cards.

The problem is that the game expects specific versions of certain DLLs to be present. In my friend's case the game was looking for msvcr100.dll, and was finding it inside the ATI driver folder. That was the wrong version (it is part of the Visual C++ 2010 redistributable).

Do this - go into your game directory, and look for _CommonRedist folder (e.g. C:\Program Files (x86)\Steam\SteamApps\common\Dying Light\_CommonRedist). That contains the packages that you need to install (start with the vcredist packages).

Try to install all the packages. If one of them complains and tells you that a newer version of the package is installed, you probably found the problem. Uninstall the newer version of the package through Add/Remove Programs, and install this one.

For future reference, you can figure these types of poblems by using the procmon tool. Add a filter to procomon to look at what the binary is doing, and try to launch the game. Check to see what the game is doing right when it starts shutting down threads and processes. If it is failing to find a DLL or finding it in a strange location, then that is probably the problem.
< >
Showing 1-1 of 1 comments
Per page: 1530 50

Date Posted: Jun 24, 2015 @ 9:15pm
Posts: 1