0xc000007b Error?

Question

here is some information to understand my situation better.

OS: windows 8.1

IDE: Visual Studio 2008 Pro

Language: C++

i have just my Firefox reinstalled and after this(maybe it was not the reason),

my visual studio Project compiled only with 9.0.30729.6161 VC++ Runtime DLL.

Until yesterday it always compiled with 9.0.30729.8387 VC++ Runtime DLL.

Because of this (or maybe other reason), now i cannot start my Project.exe.

Nothing is changed in source-code. Project-Property and all other things are also unchanged.

I just get the error number 0xc000007b suddenly.

How can i fix this?

Answer 1

It was because of an 32bit DLL, which should not be loaded for my 64bit Project.exe.

I have found this with Process Monitor.

I don't know why, but anyway is the "path" is changed and the 32bit DLL(which has the same name with 64bit DLL) is loaded..

If you have the same Problem, just start Process Monitor and check out dll files.

Answer 2

-Turn off your antivirus software before starting the installation.

-Accept any additional software offered during installation process, since it may be crucial for running your application properly. You can skip things such as search bars, antivirus scanners, registry cleaners and the other software which isn’t directly related to the application.

-Install an application to the system partition (C:). Although this shouldn’t matter, it’s been proven that some apps may return an error if installed on a logical partition.

There is more than one way to solve it. This link might also be helpful. http://finally-found-the-solution.blogspot.com/2015/02/how-to-fix-0xc000007b-application-error.html

Answer 3

Entered the answer in another place, but figure it could be helpful for folks who badly need some help:

It has been mentioned in other answers that using dependency walker is the way to go, in my case (my application keeps failing with the error code), dependency walker showed a few dll that are NOT relevant!

Finally figured out that I can run profiling by going to "profile" menu and it will run the application and stop at the exact dll that's cause the problem! I found out a 32bit dll was picked because of path and fixed it.