Buffout 4 and crash troubleshooting

[Doomchild]

Here's the report (attached)

oh wow, that's a lot of interesting info, so it's my drivers causing the crash? gonna update those and see if it's fixed.
also a few very interesting suggestions. thanks for generating a readable report

 

[Kilo1-1]

oh wow, that's a lot of interesting info, so it's my drivers causing the crash? gonna update those and see if it's fixed.
also a few very interesting suggestions. thanks for generating a readable report

Yes and no. For whatever reason, driver versions after 445 don't mesh well with the game. You can be completely stable and then restart your game and crash the next cell you enter. Updating your drivers won't help but rolling them back will.

 

[Doomchild]

Yes and no. For whatever reason, driver versions after 445 don't mesh well with the game. You can be completely stable and then restart your game and crash the next cell you enter. Updating your drivers won't help but rolling them back will.

alright, I just updated to 511.79, I'll try it tonight, if the crashes continue, i'll see about downgrading my drivers.
thanks for the info

alright, that didn't work... ctd whenever I tried to load a save, nvidia dll, so I rolled back to an older driver, loaded the game just fine, fast traveled to sanctuary and ctd'd... this time fallout4.exe is the cause, so back to square one but at least I've ruled out driver crashes >.>

second edit... can't save anymore, think I broke my save file completely...

 

[Doomchild]

well, I'm pretty sure my save file is ruined, back to the drawing board and clean up my mods list I guess.
I can still quicksave and autosave but manual saves crash the game.

 

[GuardianMF]

Here's an excerpt from this article:

Papyrus | VirtualMachine (Papyrus Crash) [NEW] | Caused by a desync in the scripting virtual machine that can result in a partially or completely corrupted save file.

Solution: One of scripted mods that your save depends on is either missing or it got corrupted. Manually download the latest version of ReSaver and extract it somewhere, run Resaver.exe and open your latest save, then select Clean > Remove Unattached Instances and Clean > Purify FormLists. If same crash messages persist, that save is most likely unsalvageable. Try reverting to an older save or simply start a new game. You should never disable or uninstall scripted mods from existing saves, mid-playthrough.

You can do as suggested if you want to keep using your save. If you did remove mods during your playthrough, then there is no garantee that more issues won't pop up.

 

[Kilo1-1]

Your latest crash doesn't seem to be related to the Nvidia driver. It seems to be related to Better Locational Damage and maybe AWKCR. You didn't enable or disable any other mods in the meantime, right?

 

[Doomchild]

Here's an excerpt from this article:

You can do as suggested if you want to keep using your save. If you did remove mods during your playthrough, then there is no garantee that more issues won't pop up.

I did Clean up the save with ReSaver, made no difference. I'm reorganizing my mod list for a new start. getting rid of any mod that might cause issues. I've been working with this mod list for years now... I'm amazed there's so much dependent on AWKCR... might be for the best. I really gotta stop changing my mods midway through my game, in fact, changed something about it almost daily in the past 2 weeks. that really came back to bite me

 

[GuardianMF]

Nowadays you can get away from AWKCR and Armorsmith Extended by switching to mod versions that are not dependent on this framework (take a look at No AWKCR and AE For Mods File Dump for instance) and Equipment and Crafting Overhaul.

 

[Doomchild]

Nowadays you can get away from AWKCR and Armorsmith Extended by switching to mod versions that are not dependent on this framework (take a look at No AWKCR and AE For Mods File Dump for instance) and Equipment and Crafting Overhaul.

most dependencies were either old mods I didn't use anyway or patch esp's, I'll try Equipment and Crafting Overhaul. I hadn't played since 2019 and my mod list was a mix of old mods & new mods. it's the first time changing mods mid game turned out so badly. after I clean up my list I'll start a new game tomorrow.

thanks for the support, hopefully I can get back to Sim Settlements without anymore issues

 

[saintdeathclaw]

I'm not getting a crash, but am having a bad freezing issue in one particular area - entering the glowing sea, on the main questline and Fishing Expedition. I've run through it a number of different ways (with & without power armor, companion, & VATS use; entering the sea from different points) with the same events; initially brief freezes (I play with task manager up in another monitor, and during these FO4 CPU use drops down to single-digit percentage before bouncing back to 25-25% as it unfreezes) that increase in number and duration as I progress closer to Atlantic Offices.

At first it seemed the generation of enemies as I moved into a new section triggered it, but after 10 or so minutes the freezes also happened constantly while I'm still, even scrolling in the pipboy. I've tried fast-travelling to both near and far map locations to see if it was specific to the glowing sea area, but the freezing continues at the same increasing rate at all other locations, making those saves unplayable. If I load a previous save even without re-starting the game, no freezing.

So far I've double-checked for potential mod issues brought up on this forum (don't think I have any incompatibilities or anything that would particularly affect the glowing sea, but will post under a spoiler below just in case!); updated my nvidia driver, and installed Buffout (previously only had Baka Scrap Heap). Without an actual crash, tho, I've got no crash log to check for clues. Oh - and ReSaver shows nothing but the same single undefined instance that's like an old friend to me now this play-through. Any suggestions, or anyone else had a similar issue just at the glowing sea?
Active mods are:

Spoiler: mod list

*Unofficial Fallout 4 Patch.esp
*ArmorKeywords.esm
*HUDFramework.esm
*WorkshopFramework.esm
*MaccreadyCleanTeethOnly.esl
*CanarySaveFileMonitor.esl
*SS2.esm
*SS2_XPAC_Chapter2.esm
*SkillBooks.esl
*Starstruck Companions - Accelerated.esp
*MacsSoldierIsNotScrap.esp
*VisibleCompanionAffinity.esp
*The Collector's Guides AIO.esp
*SS2WalledGardensAndMore.esp
*SS2_CityPlanPack_RiseOfTheCommonwealth.esp
*Starting Stats Wife.esp
*More Where That Came From - Classic.esp
*More Where That Came From Diamond City.esp
*Nuka-World Collectable Markers.esp
*Molerat_Disease_Immunity_PA_Hazmat.esp
*SkjAlert_All_DLC.esp
*EveryonesBestFriend.esp
*SCM.esp
*Better Cooking.esp
*Genetical Father 1.0.1.esp
*SCM_EBF.esp
*Armorsmith Extended.esp
*Backpacks of the Commonwealth.esp
*Scroungers Weekly.esp
*SS2WastelandVenturers.esp
*SS2_ruined_simsettlement_addonpack.esp
*JunkTownTwo.esp
*LD50_Leaders.esp
*JTC.esp
*SS2Extended.esp
*SS2Extended_OutfitInjectionPatch.esp

 

[Tarkkh]

Hello if any kind soul would read this one for me!
I know is ss2 and Wastelands ventures addon pack related but would like to have the short version so I can send to @Tinuvia

 

[Doomchild]

Hello if any kind soul would read this one for me!
I know is ss2 and Wastelands ventures addon pack related but would like to have the short version so I can send to @Tinuvia

dont know if this is helpful, but the scan tool seems to think it's a generic crash?

Spoiler: Scan

crash-2022-03-14-21-29-21.log
This crash log was automatically scanned.
VER 2.00 | MIGHT CONTAIN FALSE POSITIVES.
====================================================
Main Error: Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0x0292BC0F3430
====================================================
Detected Buffout Version: Buffout 4 v1.24.5
Latest Buffout Version: Buffout 4 v1.24.5
You have the lastest version of Buffout 4!
====================================================
CHECKING IF BUFFOUT4.TOML PARAMETERS ARE CORRECT...
====================================================
Achievements parameter is correctly configured.
-----
Memory Manager parameter is correctly configured.
-----
Looks Menu (F4EE) parameter is correctly configured.
-----
====================================================
CHECKING IF LOG MATCHES ANY KNOWN CRASH MESSAGES...
====================================================
Checking for Stack Overflow Crash.........All Clear
Checking for Nvidia Driver Crash..........All Clear
Checking for Weapon Debris Crash..........All Clear
Checking for Render Driver Crash..........All Clear
Checking for Audio Driver Crash...........All Clear
Checking for Body Physics Crash...........All Clear
Checking for Invalidation Crash...........All Clear
Checking for Grid Scrap Crash.............All Clear
Checking for Load Order Crash.............All Clear
Checking for DLCBannerDLC01.dds...........All Clear
Checking for 0x0 (Zero Crash).............All Clear
Checking for CAO Crash....................All Clear
Checking for MCM Crash....................All Clear
Checking for Generic Crash................CULPRIT FOUND!

Priority Level: [2] | Detected number of tbbmalloc.dll : 3

Checking for Papyrus Crash................All Clear
Checking for BA2 Limit Crash..............All Clear
Checking for NPC Pathing Crash............All Clear
Checking for Object Model Crash...........All Clear
Checking for Plugin Limit Crash...........All Clear
Checking for Console Command Crash........All Clear
Checking for Particle Effects Crash.......All Clear
Checking for Weapon Animation Crash.......All Clear
Checking for Corrupted Textures Crash.....All Clear
-----
FOR DETAILED DESCRIPTIONS AND POSSIBLE SOLUTIONS TO ANY ABOVE DETECTED CULPRITS,
VISIT THE BUFFOUT 4 CRASH ARTICLE: https://www.nexusmods.com/fallout4/articles/3115
====================================================
CHECKING FOR MODS THAT CAN CAUSE FREQUENT CRASHES...
====================================================
IF YOU'RE USING DYNAMIC PERFORMANCE TUNER AND/OR LOAD ACCELERATOR,
remove these mods completely and switch to High FPS Physics Fix!
Link: https://www.nexusmods.com/fallout4/mods/44798?tab=files
-----
AUTOSCAN FOUND NO PROBLEMATIC MODS THAT MATCH THE CURRENT DATABASE FOR THIS LOG.
THAT DOESN'T MEAN THERE AREN'T ANY! HINT: RUN THE PLUGIN CHECKER IN WRYE BASH!
-----
====================================================
CHECKING FOR MODS WITH SOLUTIONS AND ALTERNATIVES...
====================================================
Autoscan found no problematic mods with alternatives and solutions.
-----
====================================================
CHECKING FOR MODS PATCHED THROUGH OPC INSTALLER...
====================================================
Autoscan found no problematic mods that are already patched through OPC Installer.
-----
====================================================
SCANNING THE LOG FOR SPECIFIC (POSSIBLE) CUPLRITS...
====================================================
LIST OF (POSSIBLE) PLUGIN CULRIPTS:

• [0A] SS2.esm
• [12] SS2WastelandVenturers.esp

-----
These Plugins were caught by Buffout 4 and some of them might be responsible for this crash.
You can try disabling any listed plugins and recheck your game, though this method is unreliable.
-----
LIST OF (POSSIBLE) FORM ID CULRIPTS:
Form ID: 0A012C61
Form ID: FF004E01
Form ID: 0000E1A8
Form ID: 0000003C
Form ID: 0A012C17
Form ID: FF004E00
-----
These Form IDs were caught by Buffout 4 and some of them might be related to this crash.
You can try searching any listed Form IDs in FO4Edit and see if they lead to relevant records.
-----
FOR FULL LIST OF MODS THAT MAY CAUSE PROBLEMS, THEIR ALTERNATIVES AND DETAILED SOLUTIONS,
VISIT THE BUFFOUT 4 CRASH ARTICLE: https://www.nexusmods.com/fallout4/articles/3115
====================================================
251221 | Author/Made By: Poet#9800 | END OF AUTOSCAN

 

[GuardianMF]

Here's the troubleshooting for the Generic Crash

Spoiler: Instructions for the generic crash

The game either failed to load some Buffout 4 requirements or this is simply a generic error that has no relevance to the crash log.

Solution: Make sure you haven't missed any Buffout 4 installation steps or programs required for it, listed at the start of this article.

- If you have xSE Plugin Preloader mod installed, open its xml file inside your Fallout 4 install folder (where Fallout4.exe is) with a text editor and change line 14:
<LoadMethod Name="OnProcessAttach"> to <LoadMethod Name="OnThreadAttach">. If that doesn't work, try <LoadMethod Name="ImportAddressHook">

- If the game fails to launch or crashes before the main menu, temporarily remove all Buffout 4 files and try again. If this works, restore all Buffout 4 files, then delete xSE Plugin Preloader.xml and IpHlpAPI.dll instead. xSE Preloader does not work properly for some players, but it's not a hard requirement for Buffout 4.

For the rest of the log, I would wait to see if you get a similar crash before trying to deep dive. It does point to material properties for the Ragstag Stew, and by pasting the path on MO2's Data tab, I'm not finding anything, which means it's probably not from SS2 or Wasteland Venturers since I run those. By the way I hope you'll get your Castle plan out soon!

 

[Tarkkh]

Here's the troobleshooting for the Generic Crash

Spoiler: Instructions for the generic crash

The game either failed to load some Buffout 4 requirements or this is simply a generic error that has no relevance to the crash log.

Solution: Make sure you haven't missed any Buffout 4 installation steps or programs required for it, listed at the start of this article.

- If you have xSE Plugin Preloader mod installed, open its xml file inside your Fallout 4 install folder (where Fallout4.exe is) with a text editor and change line 14:
<LoadMethod Name="OnProcessAttach"> to <LoadMethod Name="OnThreadAttach">. If that doesn't work, try <LoadMethod Name="ImportAddressHook">

- If the game fails to launch or crashes before the main menu, temporarily remove all Buffout 4 files and try again. If this works, restore all Buffout 4 files, then delete xSE Plugin Preloader.xml and IpHlpAPI.dll instead. xSE Preloader does not work properly for some players, but it's not a hard requirement for Buffout 4.

For the rest of the log, I would wait to see if you get a similar crash before trying to deep dive. It does point to material properties for the Ragstag Stew, and by pasting the path on MO2's Data tab, I'm not finding anything, which means it's probably not from SS2 or Wasteland Venturers since I run those. By the way I hope you'll get your Castle plan out soon!

Was to be today. But forgot the tedious Nexus descriptions etc... Tomorrow 100%
and thank you very much

 

[msalaba]

@Tarkkh if you have Better Console, you can PRID these objects to find out what the base object is.
Form ID: FF004E01
Form ID: FF004E00

Better Console - F4SE

This is a F4SE plugin which makes console menu show extra useful infomation about selected target,for example, target's name, ID, baseID, mod name and so on.This plugin also add some extra info lists

www.nexusmods.com

 

[Tarkkh]

@Tarkkh if you have Better Console, you can PRID these objects to find out what the base object is.
Form ID: FF004E01
Form ID: FF004E00

Better Console - F4SE

This is a F4SE plugin which makes console menu show extra useful infomation about selected target,for example, target's name, ID, baseID, mod name and so on.This plugin also add some extra info lists

www.nexusmods.com

Gyazo

gyazo.com

Gyazo

gyazo.com

 

[msalaba]

@Tarkkh what mod is at index 0A?
The first pic is a SCOL. I would assume this is something plot spawned. Its possible there is an object in the SCOL the engine doesn't like. You can find out by opeining 'mod 0A' in xEdit and search for 012C61 The reference tab should point to the building plan it is used in.

 

[Tarkkh]

@Tarkkh what mod is at index 0A?
The first pic is a SCOL. I would assume this is something plot spawned. Its possible there is an object in the SCOL the engine doesn't like. You can find out by opeining 'mod 0A' in xEdit and search for 012C61 The reference tab should point to the building plan it is used in.

SS2 itself is the 0A

 

[Tarkkh]

anyone has anyidea of what could cause this ctd

Keeps happening so often I m currently unable to play with the new load order

 

[GuardianMF]

Never had that crash. I would look for mods with navmeshes and either change the load order or remove the culprit, if you can find it. I'm no expert, though . By the way that warning against HUDCaps looks serious!