This is sounding similar to the .dll issue I was having earlier in the thread, though it was a different .dll (d3dx9_39 instead of MSVCR110). Like I'm assuming you did, I found and downloaded the specific .dll I needed, but then a new error would pop up instead ('0xc000007b' for me, instead of 'ox000007b').
I outlined my eventual successful solution to these issues earlier in the thread, but I'll restate the problem and potential solution a bit differently here since, y'know, different .dll and all. If the underlying problem you're having is the same as what I had, then I think it's that the specific .dll you downloaded trying to fix the issue might be right, but is perhaps incompatible with some different, later revision that is already on your system. Moreover, the game or its engine wasn't equipped to accept or expect the later revision, and what the game actually wants is, specifically, a .dll that works with your framework but which is named what it was initially asking you for. Like, maybe the .dll you got as part of your framework is technically the correct .dll for that era, but the game is dumb and thinks it has to have the specific older version when it really doesn't – that was the impression I got when I looked and saw I already had an installation of DirectX9, but the game didn't like the D3DX9_43.dll that came with it and kept asking for d3dx9_39.dll, the earlier revision.
I solved my problem by going and finding the version of the .dll that I had – D3DX9_43.dll for me, probably MSVCR###-something for you, though I'm not sure where you'd look to find that – and then copying and pasting it into the game folder. After that, I just renamed it to the filename that the game first asked for, so my 'D3DX9_43.dll' became 'd3dx9_39.dll', and presumably your 'MSVCR###-whatever.dll' should be renamed to 'MSVCR110.dll'. After I did that, I had no more issues.
Sorry for the wall of text, but I hope it makes enough sense and that a solution like this can work for you.
