DLL issues. Ever since the updates

[Ketchup]

Hey all, I have been having ongoing issues with my Fallout 4 and I have with the help of windows event viewer found that the issue could lie within the msvcr110.dll. This causes CTDs on menu screen and a plethora of issues. I have looked for help, checked game cache, checked mods and a number of areas even with the f4se.

Any help would greatly be appreciated.

Cheers and happy hunting.

[Ketchup]

hey Prince, sorry for the late response. I have googled the error code, thank you so much for the help. Turns out that this is from the 2012 distributable, my concerns are that this only occured after the 1.7.22 patch from Bethesda that threw out the issue. Will be Installing it and seeing if this resolves the issue. :D

[Ketchup]

ok installed the x64, x86 and arm, nothing resolved. - will update again after I try a few more things

Will be trying the 2013 .... mixed messages on google sadly give different views. Any help would be great :D

[Ketchup]

bump. Really would like some help, thus far, I am now backing up and then uninstalling and reinstalling the game. Lets hope this works, any help would be appreciated.

[Xyzzy]

ensure that you have All versions of c++ dll.
and all directx and dotnet. Only use microsoft to get them. Do Not use 3rd party sites.

[Valkyrie]

I have the same issue, however I have tried restoring the game from a back up, reinstalling the game fresh and I cannot afford to reinstall windows 10 after all these mods I have installed through nexus mod manager and ones that arent but improve textures.

I'm going to go through all ther windows distributions of C++ and reinstall them a few times, the earliest I have is 2005 all the way through to 2013. All this work for a DLL, seriously windows?

Thank you everyone for the help.

[Valkyrie]

hey all, this is the error of what I am getting with this DLL issue. Its left me super stumped. I really, really want to play this game.

Faulting application name: Fallout4.exe, version: 1.7.22.0, time stamp: 0x57efda88
Faulting module name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098826e
Exception code: 0xc0000409
Fault offset: 0x000000000006d4e3
Faulting process id: 0x7684
Faulting application start time: 0x01d229d29c13bd9b
Faulting application path: C:\Program Files (x86)\Steam\SteamApps\common\Fallout 4\Fallout4.exe
Faulting module path: C:\Program Files (x86)\Steam\SteamApps\common\Fallout 4\MSVCR110.dll
Report Id: cf5f8ee4-0491-4023-9259-f6ef4de74a04
Faulting package full name:
Faulting package-relative application ID:

[Xyzzy]

some games require the 32bit version even though you're a 64bit and vice versa, so download 32bit version (and 64bit) if it hangs temporarily hide 64bit version (cut n paste to desktop.). still error... put back the 64bit and cut the 32bit.

http://www.faqforge.com/windows/fix-the-program-cant-start-because-msvcr100-dll-is-missing-from-your-computer-error-on-windows/

[Ketchup]

Good news, after careful process of elimination and revisiton nexus mod manager, I found that when no mods or DLC were enabled, it ran fine. So far, 122 of 300 mods its running fine. It was a mod all along and Loot wont detect the conflict bcause there are no conflicts, it could be that the mod if corrupted.

[[AG] stigus]

Originally posted by Devil's Due:

Good news, after careful process of elimination and revisiton nexus mod manager, I found that when no mods or DLC were enabled, it ran fine. So far, 122 of 300 mods its running fine. It was a mod all along and Loot wont detect the conflict bcause there are no conflicts, it could be that the mod if corrupted.

whats the mod? it might help other peeps

[Ketchup]

sorry for the long delay.
After working with a system engineering friend, then creating a batch file to generate a recording of the DLL's it turned out that something with the new update had corrupted the batch of mods. After removing all the mods, rebuilding it from scratch did we manage to resolve the issue.

Some of the mods were a mixture whom required varying Direct X. As for the ones that were the issue, sadly it became more and more tedious. Hence why we rebuilt. Games working perfectly now. :D