[Fo4] Please help me with diagnosing the cause of my crashes.

[D.Dark]

The case: All DLCs, 113 plugins, F4SE installed for Bullet Counted Reload and Classic Holstered Weapons. Have had a very stable playthrough upwards of 100s of hours in the past but after boredom and tinkering with new mods, managed to break my game. Revisted it recently, re-installed the game and rebuilt my load order from scratch. Autosaves are disabled. Hardware is top of the range.

The symptoms: Game CTD upon entering or exiting certain cells, starting with Museum of Freedom. but inconsistently. I've seen crashes like this in my last playthroughs (and subsequent testing) and know that they seem to spread to other areas and with increasing frequency after 9-10 hours of play, eventually borking the whole thing. Other symptoms include having a CTD when reloading previous saves.

Load order
https://pastebin.com/D1Bfhecu

I have Vivid Fallout set as my textures, a Black pipboy texture and a Midnight Dogmeat texture installed. I keep weapon textures to whatever is the best performance/quality balance (i.e. no 4k textures).

And the Papyrus log that the game just generated upon failing to load my most recent save says:

Papyrus Log
https://pastebin.com/Nyc8K5vG

My smooth brain is thinking that the issue is related to the Magnum Revolver Rifle failing to LL inject correctly, or me having deleted the automatically downloaded Creation Content from my drive but I've done that before without issue so I could be barking up the wrong tree there.

I'm hoping folks with decidedly less smooth brains than mine can help me out. Any help is much appreciated!

*Edit Fixed: A lie, it was all a lie! With the help of the team behind Buffout 4 I was able to determine that all of my problems stemmed from Fallout 4 being unsupported by any Nvidia drivers after 445.0 Rolling back to a driver that pre-dated any of those versions fixed everything.

[neddy3135]

I know this sounds silly , Did any of of this happen before installing a certain mod? and how often does your game crash ?.

The way to find out if it is mod related is disable a few mods at time , try your game and it still crashes , your bad mod is in that group and install those ONE at a time .
Otherwise , do the same procedure until you find the bad mod . I know it's time consuming , but as far I know , it's the only way I know to find a bad mod .

[D.Dark]

Originally posted by neddy3135:

I know this sounds silly , Did any of of this happen before installing a certain mod? and how often does your game crash ?.

The way to find out if it is mod related is disable a few mods at time , try your game and it still crashes , your bad mod is in that group and install those ONE at a time .
Otherwise , do the same procedure until you find the bad mod . I know it's time consuming , but as far I know , it's the only way I know to find a bad mod .

I can reliably reproduce this crash by reloading my most recent save. Based on how this crash shows up (i.e. identical to the crashes I was having in my previous playthroughs), I'd say it shows up infrequently but randomly in the first <9 hours, then with constant frequency after that time. This current playthrough is only about 1h50m long because I've been using that time to stand in Vault 111 slowly installing mods before exiting.

The mods that I installed just prior to encountering these bugs include:
Diary of a Madman
WInchester Cowboy Repeater
Mossberg 500
Mass Fusion Containment Settlement
and F4SE for Bullet Counted Reload and Classic Holstered Weapons, both of which appear to work correctly in my playthroughs.

I'm not sure if that is of any use to you, but I sure do appreciate the help.

[Bored Peon]

Originally posted by D.Dark:

I can reliably reproduce this crash by reloading my most recent save.

That is a tool, use it.

Any time you can reliably reproduce a CTD then you can narrow down the mod causing it by disabling mods and try to reproduce it again.

I also looked at your load order and did not see any conflicting mods that I know of.

[D.Dark]

I'll keep poking around. I've spent most of today looking at the West Tek Optics and Magnum2045 .esps to see why there are nulls coming back for their entries, as well as trying to get Buffout 4 and it's fractal dependencies operating but just stopped Fallout4.exe and f4se_loader to stop launching entirely. I've deleted anything related to Buffout 4 and now I'm trying again. I'll do as you suggest; disable half my mod list, try the file, try the other half, etc. and see if I can narrow it down.

Thanks for your help, peeps. If any epiphanies occur to you later on, please do share. I'm not confident my experiments will yield results.

[D.Dark]

You lads are both top of the pops. Your advice on deactivating half my list -> another half -> another half was one I had heard before but not actually implemented myself, despite attempting everything else along my many years of modding. Seems there's always something new to learn, or try. I found out which mod it is - now I just have to find a way of building around its absence (including any mods I made into its slave). Thanks again, kind sirs.

[Bored Peon]

No, problem. Like I said the big key to finding the mod causing it is to find a CTD you can easily replicate.

Which mod was it for future reference?

[D.Dark]

It was Unbogus Fallout (All in One). I've used that mod for years and although I have made edits to it myself, but systematically removing records in xEdit, reloading, removing other ones, etc. I was able to narrow it down to Non-Player Character (Actor) records as creating the issue. This is one area of Unbogus that I had never edited myself so I suspect it may have been some type of conflict between it and BCR or CWHS.

Deleting the whole category allowed for me to reload my most recent bugged save. Using process of elimination I narrowed the NPC Actor record down to Non Player Character (Actor): 0004AF23 endRaiderFaceM03. The edits Unbogus made to this record were the same as had been made to over a thousand other NPCs (scale with level, tweaked base stats, etc.) but for some reason it was deleting this record that allowed me to reload. My theory is that CHWS was trying to put a weapon on the back of a dead NPC and struggling with the edits. I suspect I may encounter this bug again with future with other enemy templates, but time will tell.

[D.Dark]

A lie, it was all a lie! With the help of the team behind Buffout 4 I was able to determine that all of my problems stemmed from Fallout 4 being unsupported by any Nvidia drivers after 445.0 Rolling back to a driver that pre-dated any of those versions fixed everything.

[Spec_Ops_Ape]

I'm going to assume you are using an older generation Nvidia card. 461.09 works fine for me and Fallout 4, as did the previous version and the one before that.

[fluxtorrent]

Has nothing to do with fallout 4, its specific to buffout 4. As he said. Which is a mod. Had the same problem myself

[Spec_Ops_Ape]

Originally posted by fluxtorrent:

Has nothing to do with fallout 4, its specific to buffout 4. As he said. Which is a mod. Had the same problem myself

Originally posted by D.Dark:

A lie, it was all a lie! With the help of the team behind Buffout 4 I was able to determine that all of my problems stemmed from Fallout 4 being unsupported by any Nvidia drivers after 445.0 Rolling back to a driver that pre-dated any of those versions fixed everything.

[fluxtorrent]

I know what he typed. I also know why it was the BUFFOUT 4 team that helped him identify the problem. Buffout 4 is the issue when it comes to the nvidia drivers. I can literally run my entire modlist sans buffout 4 on the current nvidia drivers (2070super) but I need to rollback to use buffout 4. So next time, try not talking before you think.

[Spec_Ops_Ape]

Originally posted by fluxtorrent:

So next time, try not talking before you think.

Arrogant nobody thinks they can tell me what to do, hilarious.
OP said nothing about Buffout 4 causing the crash and I responded to the information OP gave. You responding after the fact does not change what was said earlier.

[fluxtorrent]

Ah so not only can you not take correction and your reading comprehension suspect, but you need to resort to ad homs to try and back pedal your ignorance. Way to chime in on a topic you literally didn't understand with irrelevant commentary only to cry when your ignorance was highlighted.