HeyYou Posted May 12, 2020 Share Posted May 12, 2020 Try this: Step 1: Click on the Start Menu > Search for Command Prompt > Right-click on Command Prompt > Run As Administrator.Step 2: Once the Command Prompt is up and running, type the below command and hit Enter. bcdedit.exe /set {current} nx AlwaysOff Step 3: Once you get the output as The operation completed successfully, restart your computer once and check for the issue. Link to comment Share on other sites More sharing options...
Wererommel Posted May 13, 2020 Share Posted May 13, 2020 Phoo, then I really am out of ideas. This looks like some kind of networking problem, and I'm no expert. It only happens in Fallout 4? Link to comment Share on other sites More sharing options...
GillisParrish Posted May 14, 2020 Author Share Posted May 14, 2020 I have disabled DEP(which is what the "bcdedit.exe" command is)and yes it only happens with FO4. Link to comment Share on other sites More sharing options...
GillisParrish Posted May 14, 2020 Author Share Posted May 14, 2020 Honestly,I'm about to start offering payment for someone to fix it,not just the BEX64 error,but how to fix load order,mod conflicts,and merge plugins.So tired of Fallout4 being such a pain in the ass to keep running. Link to comment Share on other sites More sharing options...
Wererommel Posted May 14, 2020 Share Posted May 14, 2020 I don't know why, but I don't usually have a lot of problems until the next "update" comes and ruins everything. (Because I use Vortex? They say there are problems with that too.) Are you playing any other Steam games? Link to comment Share on other sites More sharing options...
Wererommel Posted May 15, 2020 Share Posted May 15, 2020 Are you using MO? ACSpiral says that the .inis you think you are using may not be the same as the one MO uses: "So I checked my Fallout4Custom.ini in Documents/My Games/Fallout4 and sure enough the edit was there where I put it. I then checked the copy that MO keeps within itself and, unlike the original copy, this one didn't have the necessary edit. So when I ran the game through MO it was relying on the edit within TrueGrass.ini to make the rest of the mods work. " Of course, this may have nothing to do with it. I am totally shooting in the dark. Link to comment Share on other sites More sharing options...
GillisParrish Posted May 15, 2020 Author Share Posted May 15, 2020 No,I use the community supported NMM,and I have had similar problem to that.Some mods add ini,also which don't change in accordance with the Fallout ini's....but I got that figured out.I have uninstalled the C++ packages,reinstalled those and it still crashes.BEX 64 is a stack overflow issue I believe,but I do not know how to track down what is causing it.My settings were working fine til the latest round of SS updates,so I ran all those back ...and the MF still crashes. Link to comment Share on other sites More sharing options...
Recommended Posts