BEX64

[GillisParrish]

So,this error has periodically popped up for years,and has resulted in many times just putting the game down for months at a time.
What is it?How do I fix it permanently?
I have heard it is caused by not having a certain DirectX update installed.The Bethesda site refers you directly to the MS website to download and install the correct version,which I have multiple times,ran back the DirectX to the version they suggest will fix the problem - it does not.
I have heard it is a DEP problem,proceed to the settings,add an exception,but you can't add properties to 64 bit programs,but you can disable DEP altogether(which is what I have done) - it does not work.
I have heard it is caused by multiple scripts calling for the same .dll("MSVCR110.dll").So, I changed the Papyrus settings in the various .ini's,in accordance with a post from KingGath himself - it does not work.
If this is the problem how does one go about tracking it down,because a slight variation on "it is multiple scripts tripping all over each other" is,that it is cause by 3rd party software calling for the MSVCR110.dll,while F4SE is calling on it for game stuff.
I have heard go to an interior cell(like the bunker in Sanctuary)and sleep for a week - it does not work.
And of course I have heard every mod downloaded is the culprit,that mod is cancer,that mod is a nightmare but generally I don't think that is the case,but in this case SS,SSC,WSF,and WS+ all required updating,and that is basically when my game became unplayable.Assuming these updates have multiple scripts running(more then oh...2 days ago)how would one go about fixing that?Too much update at one time for F4SE,causing scripting conflicts?IDK.I am about fed up with it,like I said I have been battling this beast for years,and it will go away for months and I'll think that last edit in the .ini's did it or that patch seems to have got it,but here it is 2020 and I'm still fighting this motherf...problem.
Any insight would be appreciated.

[Wererommel]

Is this what you're talking about?

 

https://help.bethesda.net/app/answers/detail/a_id/31717/~/what-should-i-do-if-fallout-4-crashes-with-the-error-message%2C-problem-event

[GillisParrish]

yes I have that installed.

[Wererommel]

https://answers.microsoft.com/en-us/windows/forum/all/bex64-error/75ef6860-3f55-4bc0-8659-033381faeaa2

[GillisParrish]

done that too

[Wererommel]

Check and see if you have these files in your main game folder:

 

bink2w64.dll
cudart64_75.dll
f4se_1_10_163.dll
f4se_steam_loader.dll
FLEXEXTRELEASE_X64.DLL
flexRelease_x64.dll
msvcp110.dll
nvToolsExt64_1.dll
steam_api64.dll

[GillisParrish]

all those .dll are present.

[Wererommel]

Nothing else occurs to me at the moment. I'll let you know if I think of something. Or maybe someone else has a thought.

[Wererommel]

I had another thought already: Check the size of these files. If they are outdated or corrupted, then the file size may be different.


bink2w64.dll (418 KB)
cudart64_75.dll (353 KB)
f4se_1_10_163.dll (839 KB)
f4se_steam_loader.dll (139 KB)
FLEXEXTRELEASE_X64.DLL (345 KB)
flexRelease_x64.dll (1,270 KB)
GFSDK_GodraysLib.x64.dll (340 KB)
GFSDK_SSAO_D3D11.win64.dll (538 KB)
msvcp110.dll (646 KB)
nvToolsExt64_1.dll (42 KB)
steam_api64.dll (202 KB)

Or, if the numbers all match, the problem must lie elsewhere.

[GillisParrish]

sizes match.