Crashing either to Desktop or Requiring Full Reboot MO2 AAF

[nogling]

Hello all,

 

I used FourPlay awhile ago, and then tried AAF. I couldn't fully figure it out and deleted everything/stopped playing. Today I decided to try again after 1 year+ totally from scratch. I saw this wonderful AAF guide: https://www.loverslab.com/topic/139374-aaf-up-to-date-adult-oriented-setup-guide-11june2020/ and followed it pretty much exactly.

 

I think I did everything properly. I start a new game, no mods enabled at all. I make it out of the vault, save, and quit. I load up MO2 and turn on my mods, and start the game. I load my save, it warns me that mods are active, and I begin.

 

Then I play anywhere from 20 seconds to 5 minutes before it crashes, either a CTD where it tells me my AMD Radeon display driver has crashed and recovered, or it just hangs there forever frozen in game until I physically reboot using a hardware button wired into my PC. I can't get past (at best) killing the bloatflies with Codsworth in the starting area.

 

Here is my MO2 load order, and I believe everything should be properly in place as far as that goes, but I would appreciate a check from someone more knowledgeable. Should my plugins order be changed at all? Does anything appear odd? Does anyone have experience with older AMD systems and Fallout 4? I have the latest drivers from them so it should not be that. I have 2 GPUs and I've tried it both with and without Crossfire enabled to no discernible avail. Running 7 64-bit if that helps at all. Exes are running as administrator....

 

 

 

Update: It's not even AAF and the mods I've discovered. Loading up purely vanilla after leaving the Vault also crashes. I didn't think it would because *in* the Vault I had no issues. Does anyone have any experience with vanilla FO4 crashing via your AMD display driver?

[nogling]

Ok new info: It might have something to with the mods after all, though stability is intermittent no matter what's on. I went to the FO4 launcher and put everything to minimum in the advanced graphical settings, and godrays off. It think it helped somewhat. I made it to Preston and company on vanilla without crashing. However when the mods are on, I only made it the museum entrance and engaging the raiders there. Crossfire has been off on both attempts, and I also fully disabled the Radeon overlay in game because I thought that might be an issue....

[dagobaking]

Is this a pirated game? Broken computer?

[EgoBallistic]

On 6/13/2020 at 2:21 AM, nogling said:

Update: It's not even AAF and the mods I've discovered. Loading up purely vanilla after leaving the Vault also crashes. I didn't think it would because *in* the Vault I had no issues. Does anyone have any experience with vanilla FO4 crashing via your AMD display driver?

Not sure this is helpful, but with the latest Nvidia drivers my game will CTD on load in certain places like Diamond City if I have the game set to Full Screen.  If I set it to Borderless Widescreen it has no issues.  This is with a 2080ti, not an AMD card, but the issue was also related to the display driver.

 

A couple of weeks ago I updated to the 446.14 drivers.  I had been using the 431.60 drivers from last November.  When I started FO4 up again, I started getting CTDs.  I could load saves made in Home Plate, but new saves made in Diamond City would always CTD on the load screen.  I thought it might be a corrupt save, but then I discovered it happened even with old saves from months ago. 

 

I removed all the mods I had installed since making those old saves, and that didn't help.  So the only thing left to try was to roll back to the 431.60 drivers.  sure enough, when I did that, no more CTDs even with the newest saves.  I then went back to 446.14, and the CTDs came back.  After trying different settings options, I discovered that putting the game in Borderless Windowed mode fixed the issues completely with the new drivers.  I've been playing it that way ever since with zero problems.

 

So just something to try.  There could be something in the game engine that recent drivers from both AMD and Nvidia don't like.  Or it could be completely unrelated, who knows.

[nogling]

On 6/14/2020 at 8:17 PM, dagobaking said:

Is this a pirated game? Broken computer?

Game is normal, not pirated. Other games play normal. I only have these issues with Fallout 4.

 

On 6/15/2020 at 1:58 AM, EgoBallistic said:

Not sure this is helpful, but with the latest Nvidia drivers my game will CTD on load in certain places like Diamond City if I have the game set to Full Screen.  If I set it to Borderless Widescreen it has no issues.  This is with a 2080ti, not an AMD card, but the issue was also related to the display driver.

 

A couple of weeks ago I updated to the 446.14 drivers.  I had been using the 431.60 drivers from last November.  When I started FO4 up again, I started getting CTDs.  I could load saves made in Home Plate, but new saves made in Diamond City would always CTD on the load screen.  I thought it might be a corrupt save, but then I discovered it happened even with old saves from months ago. 

 

I removed all the mods I had installed since making those old saves, and that didn't help.  So the only thing left to try was to roll back to the 431.60 drivers.  sure enough, when I did that, no more CTDs even with the newest saves.  I then went back to 446.14, and the CTDs came back.  After trying different settings options, I discovered that putting the game in Borderless Windowed mode fixed the issues completely with the new drivers.  I've been playing it that way ever since with zero problems.

 

So just something to try.  There could be something in the game engine that recent drivers from both AMD and Nvidia don't like.  Or it could be completely unrelated, who knows.

I've tried Borderless Widescreen...doesn't do anything for me as far as I can tell. I did a fresh factory install of the latest drivers. I might get some pretty old ones, like a year ago or something, and factory install them. I know before I got the latest drivers, I had January ones, and it was still the same....