Sudden CTD issue

[IBAGadget]

I'm hoping someone can help me out here. Just started getting CTD issues shortly after starting up my game and loading my save. Initial CTD occurred after about 15 minutes of play time, but that has since dropped to about 30-60 seconds after initially loading my save. just enough time for AAF to register and let me think about doing something. Here's my latest Papyrus and Crash logs.

 

Hopefully someone more knowledgeable than myself can point me in the right direction as to what could be the culprit, or if it is something more systemic to FO4 base game.

As an extra bit of info, during my last playthrough just the other day, I had a glitch where I was exiting out of the Sanctuary Hot Springs Home, and instead of winding up just outside the door, I wound up in the middle of Thicket Excavations wearing a Vault 111 suit and equipped with a second unmodified PipBoy.

 

After this, my Poster tab in the Decorations menu of the workshop disappeared completely and I have not been able to get it back. The various Settlement Menu Manager fixes have only succeeded in wiping out any added in workshop categories without bringing back the Posters category.

 

frustrating, to say the least.

 

Should I be looking at a complete re-install of FO4?

 

Can I purge my modlist in Vortex, Re-install FO4, then Re-Deploy my modlist without any serious issues? or is it going to be a complete re-install of all my mods?

If I have to re-install FO4, am I going to need to go through the manual re-installation of F4SE afterwards?

Papyrus.0.log crash-2022-09-13-01-37-36.log

[Sgt. Marge]

crash-2022-09-13-01-37-36-AUTOSCAN.md

 

Here is your auto-scanned crash log.   I've linked the auto-scanner there as you may want to download that and get it working for next time you have a crash.  It looks like you've got a couple contenders to track down here.  PipboyMapData, that one sounds familiar.  You have something that changes the pip boy map?

 

Spoiler

 

This one got dinged too starting stats wife.esp

 

Spoiler

 

There are some other suggestions, you can open the scanned log with Notepad ++ for easier reading

Edited September 13, 2022 by Sgt. Marge

[IBAGadget]

6 minutes ago, Sgt. Marge said:

crash-2022-09-13-01-37-36-AUTOSCAN.md 6.14 kB · 0 downloads

 

Here is your auto-scanned crash log.   I've linked the auto-scanner there as you may want to download that and get it working for next time you have a crash.  It looks like you've got a couple contenders to track down here.  PipboyMapData, that one sounds familiar.  You have something that changes the pip boy map?

 

  Hide contents

 

This one got dinged too starting stats wife.esp

 

  Hide contents

 

There are some other suggestions, you can open the scanned log with Notepad ++ for easier reading

Thank you. That information is very surprising, as I have been using The Starting Roleplay perks and Full Color World map for over a year and a half with no previous issues.

 

Currently I'm going through a complete re-install of my game - Steam was unable to verify 7 files, so I'm wondering if they were corrupted when I had my little glitch the other day. Assuming my re-install actually gets completed tonight, I'll re-deploy my modlist and see what happens.

 

Took forever to get permissions re-set for the files to allow the download to actually happen.  Everytime I re-set the game files out of 'Read Only' mode, they went straight back into it, so I couldn't just update the game.

 

Fingers crossed I can just re-deploy, and don't have to go through re-installing everything one at a time, trying to remember what order I have to install and enable things in. AAF was a nightmare to get running right........

[IBAGadget]

Well, re-installing did no good whatsoever, other than making it so that the game won't even start. I get the initial launch screen, press play, and a few seconds later it just stops.

 

Sadly, it looks like I'm going to have to do a complete purge of the entire install folder, as well as the My Games folder, and start from scratch.

 

 

 

FML.

 

so not looking forward to having to re-do my entire mod list.

 

At least I have everything saved in a central mod storage location. Just going to be a bitch to remember what needs to be installed in what order, and what clothing mods need the CBBE file installed and then the Fusion Girl Bodyslides, and what ones are standalone FG conversions.

 

I need another week's vacation for this....

[Sgt. Marge]

Ah.  Reinstalling is seldom a cure.  The problem is that it does not remove stuff vortex added.  What you can use is DCU from Moddingham.  It's the same website that hosts the latest version of AAF.

 

DCU resets the data folder to a "vanilla" state.  From there you'd just need to verify files in steam, reinstall F4SE.

Since you've reinstalled the game now, make sure modding is enabled in the Fallout4Custom.ini file after running the game once from the launcher.

also make sure you've got buffout installed, and you don't have any "missing masters"

 

If you are still super stuck you can always join the AAF discord, the invite link is in the guide (along with the buffout instructions and how to enable modding etc).

[IBAGadget]

In this instance, there is only going to be a 'vanilla state' when I am done. As the Fallout 4 folder in 'My Games' will not accept being outside of a 'Read Only' state, my re-install cannot create or access the ini file.

 

I'm going to email myself my modlist, then do the following:

 

Un-manage FO4 from Vortex.

Uninstall FO4

Delete the Fallout 4 folders and their entire contents in My Games and Program Files locations.

Re-install FO4

Run the game to create the ini file

 

Manage the game with Vortex

Begin the laborious task of re-installing my mod list, eliminating some mods that I really don't use anymore (a lot of clothing mods are going to get binned from the modlist)

[travelmedic]

Having the game crash a few seconds after you hit "Continue" or "New Game" may be a sign that you've hit the BA2 limit.  Too many archives can also cause the game to crash, just like too many esp or esm files.  The difference is, we know there's a limit of 255 for esps, but the BA2 limit varies for everyone, but starts with about 450 archives and goes up from there.

 

I ran into this same problem just recently setting up a new game, and ended up deleting a few mods and unpacking the archives for a few smaller files so they loaded as loose files instead.  I think it was in the SSE section of Nexus that I found a really simple, handy BA2/BSA unpacker program.

 

If you have an extensive load order, this is something to consider.  You can try disabling a few mods that have archives and see if that makes a difference.

[IBAGadget]

My mod list is actually smaller than it used to be. I was running about 367 active mods at one point, but I've pared that down to 297 now. That is going to get pared down even more when I remove a few more clothing mods that I just don't use from my rebuild list..

[IBAGadget]

Ok, this is frustrating.

 

complete clean re-install of FO4, files verified by Steam.

Complete reinstall, following the guides, of F4SE, Buffout 4, etc etc etc.

 

Vanilla game launch successful (once I got my resolution/display options set correctly)

Added mods, updating to newer versions where they were available.

 

Launch game. 

Runs Fine

 

After many hours of new playthrough, I can no longer draw a weapon without having an instant CTD, before the weapon drawing animation even finishes.

Hunting through Reddit, Steam Community, etc etc etc. no luck. CTD persists.

 

Common result from all crashes - PipboyMapData (whatever the hell this is - I cannot find any information on what this means)

Here is my latest Crashlog, as well as the Autoscanner results.

 

For the life of me, I cannot narrow this down. 

 

Some folks say that this:

 

"EXCEPTION_ACCESS_VIOLATION" at 0x7FF7608D5819 Fallout4.exe+0C25819

 

Points to the culprit plugin (in my case, 0C is Videos of the Wasteland ESM)

 

This doesn't seem to make much sense though, as what would VoTW have to do with equipping a weapon?

 

Help? Please?

 

 

crash-2022-09-19-01-28-20.log crash-2022-09-19-01-28-20-AUTOSCAN.md

[Sgt. Marge]

8 hours ago, IBAGadget said:

Ok, this is frustrating.

 

complete clean re-install of FO4, files verified by Steam.

Complete reinstall, following the guides, of F4SE, Buffout 4, etc etc etc.

 

Vanilla game launch successful (once I got my resolution/display options set correctly)

Added mods, updating to newer versions where they were available.

 

Launch game. 

Runs Fine

 

After many hours of new playthrough, I can no longer draw a weapon without having an instant CTD, before the weapon drawing animation even finishes.

Hunting through Reddit, Steam Community, etc etc etc. no luck. CTD persists.

 

Common result from all crashes - PipboyMapData (whatever the hell this is - I cannot find any information on what this means)

Here is my latest Crashlog, as well as the Autoscanner results.

 

For the life of me, I cannot narrow this down. 

 

Some folks say that this:

 

"EXCEPTION_ACCESS_VIOLATION" at 0x7FF7608D5819 Fallout4.exe+0C25819

 

Points to the culprit plugin (in my case, 0C is Videos of the Wasteland ESM)

 

This doesn't seem to make much sense though, as what would VoTW have to do with equipping a weapon?

 

Help? Please?

 

 

crash-2022-09-19-01-28-20.log 19.95 kB · 0 downloads crash-2022-09-19-01-28-20-AUTOSCAN.md 4.96 kB · 0 downloads

 

You can try running GFV from Moddingham, that can tell you if one of your F4SE scripts is being overwritten.

 

Other than that, the place you may need to go is the Collective Modding Discord (Check the sticky note in that article for the invite link) as there's a channel there for posting Buffout Logs and is monitored by folks that understand them much better than I do.  I just ran a search on their discord and there's one person that reported this specific crash back in April, in the exact way you did:  Drawing weapon causing crash and PipBoyMapData peppered into the crash log.  Here's what fixed it for them.

(First, it might be a good idea to find a safe container in your settlement and remove all non quest items from your inventory and place them into the container)
Open the command console with the `~ key
 

player.unequipall

 

This command will remove any equipped item from your character including things you can't see in your pipboy inventory.  Supposedly they were able to run this command even on the save file from their previous game and were able to continue playing through it.

 

If that doesn't fix it, then I would encourage you to join that discord and check in with them.

 

They have 2 relevant channels for this: -fo4-crash-logs and -fo4-general-support

Edited September 19, 2022 by Sgt. Marge
Spelling

[IBAGadget]

@Sgt. Marge That did the trick. Thank you. Was pulling out what little hair I have left trying to figure this out.