CTD after about 1-2 minutes. MO2 no Mods other then F4SE and ENB.

[blueballbob]

Haven't played Fallout 4 in a while so fired it up recently.  Started to get a CTD about 2 minutes in almost every time.  Had been working fine about three months ago.

 

OS: Windows 10 latest

GPU: Nvidia RTX 2080ti Driver 430.86

CPU: Intel Core i7-7820X

RAM: 32 GB

 

Couldn't find an offending mod, so stripped everything back to just ENB, F4SE and MO2 version 2.2.0.  And was still able to replicate the crash.

Occasionally get this:

Application Fallout4.exe has been blocked from accessing Graphics hardware.

 

Tried launching Fallout 4 outside of MO2, seems to run fine.  Even with the F4SE Launcher and ENB files still there.

 

Tried Uninstalling Fallout 4 completely, and re-installing it.  Still CTD with MO2 launching and no mods.

Tried Downgrading MO2 to 2.1.6.  Still CTD with MO2 launching and no mods.

Tried reinstalling ENB, Still CTD with MO2 launching and no mods.

Tried reinstalling F4SE.  Still CTD with MO2 launching and no mods.

 

If I run Skyrim SE with MO2, and full mod set, zero issues.

Can run Battlefront 2 with no issues.

 

Any ideas?  Downgrade the NVIDIA drivers maybe?

 

 

[LukeDuke]

I have GTX 1080 Ti with latest nvidia drivers and can confirm random CTD in FO4 and sometimes in SSE too. So yeah downgrade drivers or wait for new drivers which might fix it or not..

[blueballbob]

17 hours ago, LukeDuke said:

I have GTX 1080 Ti with latest nvidia drivers and can confirm random CTD in FO4 and sometimes in SSE too. So yeah downgrade drivers or wait for new drivers which might fix it or not..

Well mine is pretty quick, like within a minute or two of loading a save.  Tried rolling back to driver 419.67, that didn't do anything.  I'm starting to wonder if some Windows patch isn't playing nice with MO2?

 

Strange thing is Skyrim SE runs like a champ in the same MO2.

 

Guess I'll wait a few more months on Fallout 4 and try again.

[Invictusblade]

so I am assuming that it ctd's in the main menu as well

have a look in your Data folder

now rename all of your folders inside Data to have a _2 next to it (such as Meshes_2)

now start the game and see if it still crashes (then it might be your settings files, rename them then)

if it works, then slowly return the folders back to their proper names until it errors then look into that folder.

 

(I had this problem quite a few times with different issues & solves such as it turns out to be an empty text file inside an animation folder inside Meshes)

[blueballbob]

17 hours ago, Invictaxe said:

so I am assuming that it ctd's in the main menu as well

have a look in your Data folder

now rename all of your folders inside Data to have a _2 next to it (such as Meshes_2)

now start the game and see if it still crashes (then it might be your settings files, rename them then)

if it works, then slowly return the folders back to their proper names until it errors then look into that folder.

 

(I had this problem quite a few times with different issues & solves such as it turns out to be an empty text file inside an animation folder inside Meshes)

Thanks.  I'll take a look at that. 

I can load a saved game, so it's not crashing in menus.  It'll load the game, but about 1-2 minutes in it'll crash.  

 

Will try default settings files and look for empty text files.   Have some mesh folders in overwrite from making a body in bodyslide, so might clean that folder and try it again with the bare MO2, F4SE and Enb setup.

[Invictusblade]

51 minutes ago, blueballbob said:

Thanks.  I'll take a look at that. 

I can load a saved game, so it's not crashing in menus.  It'll load the game, but about 1-2 minutes in it'll crash.  

 

Will try default settings files and look for empty text files.   Have some mesh folders in overwrite from making a body in bodyslide, so might clean that folder and try it again with the bare MO2, F4SE and Enb setup.

I didn't Actually say anything about looking specifically for Empty Text files (it just happened to affect my game once(I used it as an example of how weird Fallout 4 crashes can be))

I said to do a broad renaming of your Folders inside Data Folder.

 

because it could be a lot of things, Bad textures, Bad meshes, Bad Interface icons

[blueballbob]

Resolved!

 

Finally figured it out.  Must have been something in the ini files that were in MO2's folders.  Deleted the default ini files and re-created them with the Fallout 4 launcher.  Then did the edits needed and copied those to the MO2 default profile folder and replaced the really old ini files there.

 

Working great now!  Finally.