Crash to Desktop approaching the Wasteland Holotape near Kaelyn's Bed & Breakfast

[TheHDog]

When approaching the Broken Steel encounter between Kaelyn's Bed & Breakfast VAPL-58 power station, the game crashes to desktop while approaching the table that wastelander holotape #1 is sitting on.  The encounter appears after completing Take It Back! and beginning Broken Steel. 

System Specs:

OS: Windows 7 Home 64Bit

CPU: AMD FX-6300

RAM: 12.0GB Dual-Channel DDR3

Mod Manager and Version: Nexus Mod Manager 0.49.3

Attempts to resolve: Disabled all TTW unrelated mods up to and including Ephemeral Ash and Goo Piles, fast traveled away from the encounter and rested for a week (In the Megaton player house), dropped the graphics settings to the lowest settings, launched the game from Steam and not the 4GB launcher. 

FO3 Version: Steam GotY edition.

[TrickyVein]

Your load order is incorrect so it's surprising that you've made it this far if that really is your true load order. The correct load order is listed under step 3 of the manual installation instructions on the alpha download page, here.

I'll just go ahead and reproduce what your load order should be for TTW here as well:

• 
  Fallout NV


• 
  Dead Money


• 
  Honest Hearts


• 
  Old World Blues


• 
  Lonesome Road


• 
  Gun Runners Arsenal


• 
  (stash packs)


• 
  Fallout 3


• 
  Anchorage


• 
  The Pitt


• 
  Broken Steel


• 
  Point Lookout


• 
  Zeta


• 
  TaleofTwoWastelands

Once you've reordered your plugins see if you 1) can even load your save game from before and 2) if you can, or if you start a new game if you still get crashes in that area. 

[MarchUntoTorment]

Wow. That load order's so broken I'd say that you're a genius for just avoiding CTDs on startup :P

[TheHDog]

Thank you for your time. My save loaded just fine, I am still experiencing the same crash issue. 

[TrickyVein]

Have you at any time ever download the official bugfixes pack for TTW? If yes, then take inventory of what's left in your NV data folder. Some resources were found to be responsible for CTDs and have been removed in recent updates. 

Other than loose files, it's going to be a mod that's giving you trouble since vanilla TTW runs fine in that area. Disable those other ones and see what happens.

[TheHDog]

I do not have any memory of installing that mod and I try to keep disabled mods saved in the editor as a record.  Tried again with everything up but excluding TWW disabled same issue.

 

Edit: I also noticed that the TribalPack esm was in the wrong location while disabling said mods and moved it during the test.

[TJ]

It sounds to me like you're disabling mods, and not uninstalling them. I know, I know, it's a pain in the ass. Here's why it's the right way to do it: When you load New Vegas, Gamebryo hoovers up every single thing in your data folder. Disabled mods, loose files, all those lovely readmes.. All of them get loaded when Gamebryo does this. This is called reading your data folder. It then tosses everything that's not needed for the mods loaded out of it's chunk of memory.... except the loose files. All the loose files stay loaded even if they aren't needed. So for example the one broken mesh in TTWFixes that Tricky mentioned? It still caused crashes even if the mod was disabled or even removed from the data folder.

[TheHDog]

By that, do you mean deactivate them from the Mods tab in NMM or completely delete all references to them from my computer?  If it is the latter, I am unsure of how to go about that, should I nuke FO3 and NV and install them from scratch? 

[TJ]

No just deactivate from the mods tab. The mods in that tab aren't actually in your data folder until they're activated.

[TheHDog]

Alright, after doing that, I just have the Wrye Bash esp remaining.  I'll need to look up how to uninstall Wrye Bash but, without doing that, it is still crashing at the same location.  It fixed a texture issue with barricades I've been having though.