Im about 45 hours into F:NV and its going really well
I loaded all the Viva FV mods and stability recommendations but then I also loaded about 25 additional mods and accepted that this could create some CTD because they outside the Viva list
And I was getting about 2-3 random CTD in a 3 hour session which is fine, it takes literally 30 seconds to reload the game in MO2 and I save often so I dont lose anything. But then on Sunday I went on a Bounty Hunter quest to the Fiend territory and the game started crashing every minute in one region. And this area is notoriously bad for CTD and its well known and there are lots of solutions to resolve it but as usual with troubleshooting and CTD one solution doesnt mean it will resolve your specific problem
So I decided to use MO2 to troubleshoot and the advantages of using multiple profiles, multiple profiles lets you disable mods and enable mods and it wont impact your main game
But before I started disabling mods in my troubleshooting MO2 profile I read a suggestion on Viva and the FNV performance guide and it was an .ini setting around the NV Tick Fix mod
https://performance.moddinglinked.com/falloutnv.html#NVTF
" Double-click on NVTF in Mod Organizer, then open NVTF.ini in the INI Files tab, and set:
bModifyDirectXBehavior = 1"
So I made the change and guess what? No more crashes in the Fiend territory and I havent had one CTD since making that single .ini change which is about DirectX
I am amazed that a single .ini tick box could improve the overall stability so much, Im not complaining of course and Im sure I will still get CTD but its an interesting lesson around how sometimes CTD are not about particular mods you use but rather a specific setting or recommendation in a mod file
Moral of the story, always read your mod recommendations around performance and stability and how this type of mod can be configured