Fallout New Vegas Crashing Constantly With Mods

[dredd011]

My load order

0 0 FalloutNV.esm

1 1 DeadMoney.esm

2 2 HonestHearts.esm

3 3 OldWorldBlues.esm

4 4 LonesomeRoad.esm

5 5 GunRunnersArsenal.esm

6 6 ClassicPack.esm

7 7 MercenaryPack.esm

8 8 TribalPack.esm

9 9 CaravanPack.esm

10 a Project Nevada - Core.esm

11 b FCOMaster.esm

12 c Project Nevada - Equipment.esm

13 d Project Nevada - Rebalance.esp

14 e Project Nevada - Cyberware.esp

15 f CommonwealthSurplus.esm

GreatKhanGreatOverhaul.esm

16 10 oHUD.esm

17 11 SomeguySeries.esm

WEATHER RUDY ENB.esp

18 12 EVE FNV - ALL DLC.esp

19 13 dD - Enhanced Blood Main NV.esp

20 14 FCO - NPC Changes.esp

FO4 Power Armors - TTW Standard Edition.esp

FO4 Power Armors - FNV Standard Edition.esp

21 15 boa ncrpahelmet.esp

22 16 Boacombat2glove.esp

FO4 Power Armors - FNV Compatibility Edition.esp

23 17 Reload Sounds.esp

24 18 Weapon Retexture Project.esp

25 19 Asurah_reanimation.esp

26 1a The Mod Configuration Menu.esp

AmmoChecking.esp

27 1b Real Recoil.esp

28 1c CommonwealthSurplus - Sounds.esp

29 1d B42Inertia.esp

30 1e NVBountyBoards.esp

31 1f T60.esp

32 20 ADAM Complete.esp

NCROverhaul.esp

33 21 ADAM - MERGE.esp

34 22 MojaveSandyDesert.esp

35 23 NewVegasBounties.esp

36 24 NewVegasBountiesII.esp

37 25 CommonwealthSurplus - LevelList.esp

38 26 1nivVSLArmors.esp

39 27 NewVegasBountiesII Fixes - DLCs.esp

40 28 Sit Anywhere.esp

41 29 pyDoF.esp

42 2a FOVSlider.esp

43 2b The Weapon Mod Menu.esp

44 2c Russell.esp

45 2d NewVegasBountiesIII.esp

PowderIsTheNewBlack.esp

46 2e NukaCola-Ojo.esp

47 2f TGsArmorCollectionVegas.esp

48 30 TGsArmorCollectionLeveledList.esp

49 31 CAGE 1.9.3.2.esp

50 32 pipboy2500_edisleado.esp

BrotherhoodReforged.esp

BoomersGoBoom.esp

51 33 FCO - GlowingOne.esp

52 34 FCO - OHSB NPC Edits.esp

53 35 FCO - Russell.esp

[dubiousintent]

In future, please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as the version of Windows, if you are using a "regional language version" of the game (even if you are playing it in English); using the FNV4GB Patch, NVSE and it's related plugins; replacements for textures (specifically their larger image sizes: 1024x1024, etc.), animations, or "bodies", etc.; and "post-processors" like ENB or SweetFX. It saves us playing "20 questions" and gets you a more specific answer more quickly. (The usual turn-around on post and reply in an older game forum is 24 hours.) Screenshots don't usually work so well because they tend to cut off or fail to display needed information and are hard to "piece together" into a complete and coherent picture.

* See "How to markup images (etc) in forum posts and comments" article for how to use "Spoiler tags". LOOT already includes those tags in the "load order" it copies to your clipboard, so you can just paste it's list into your post.

Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article.

 

As a consequence of not having all the related information to narrow things down, you get the following wall of text with possible problems and solutions. All of the following may not apply to your specific situation, but are worth repeating anyway.

* Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so.

* Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" or "C:\Program Files(x86)" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. System updates often cause issues with games installed to these folder trees. With the game moved out of the default location you will not need to be running it as an "Administrator Account", which is safer. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

Disabling "User Account Control" (UAC) only stops Windows from prompting you to grant "administrative" credentials to an application that the system says must have a "UAC elevation". Disabling UAC does not automatically then enable the permission for such applications. Instead, (for all intents and purposes) it automatically denies them. (Please read this MS article on how it works in Win10. The basics have been there since the inception of UAC with Vista.)

If you did move Steam out of the default location, then likely any access privilege problem is one of "File and Folder permissions" on the parent "root" folder under which you installed the games. If this is not set correctly to allow at least "System", "Administrators", and "Users" to have "Full Control" then you can't overwrite other files or make changes. You then (while logged in as an "Administrator Account") need to enable the "Properties | Security | Advanced | Change Permissions" setting of the parent folder to enable the box: "Replace all child object permissions with inheritable permissions from this object", so those changes get applied to the existing files and sub-folders.

Do you have "New Vegas Stutter Remover" (NVSR) installed? If so, please see the 'Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)' and 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' entries in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* Move any "inactive/disabled" plugins out of the game "Data" folder. They count against the "plugin cap" because they get loaded by the game engine if found, and can cause "Missing Master" problems. Please see the wiki "Missing Masters" article if you get that error message. If those plugins without the "mod index" numbers are "deactivated by the "Bash Patch", then you failed to have them "ghosted" by "Wrye Bash/Flash" when you built your "Bashed Patch". Please see the wiki "Bashed Patch file with Marked Mergeables" article.

* Don't install every optional file for a mod. Read the install instructions carefully. Optional files need to be selected on a "case by case" basis. For example: with any mod you usually only need one ESP (and possibly one ESM) "base" file depending upon whether you have all the DLCs active or not. Only if you don't have them all active do you need to install any specific DLC versions if there is an "Ultimate Edition/All/Merged DLC" version.

* "Compatibility patches" to make one mod work with another need to be placed after (as in "physically lower, higher numbered") in the "load order" than ALL of the plugins they are designed to make compatible. (This also applies to "fix" files.) ESMs should always be placed at the top (lowest numbered) positions in the "load order", followed by the related ESPs though they can be separated from their ESMs by other plugins. LOOT does a good job of determining those basic orders. Getting the "load order" incorrect will cause "Missing Masters" errors as well. You can make minor adjustments to the order and tell LOOT how to remember them. It's in the on-line documentation under "Metadata".

FYI: The "pre-order packs" (aka "POPs": Caravan, Classic, Mercenary, and Tribal; available now in the "Courier's Stash" addon), are not considered "true DLC expansions" by most mods and are treated as "compatibility patches" because they just add certain unique items. So their absence should not deter you from using "All DLC Merged" plugins. Where they are included, they should come after "GunrunnersArsenal.ESM" which is a true DLC expansion. When in doubt, follow the process in the wiki "Missing Masters" article to confirm they are not "master files" for that plugin.

* Don't install compatibility patches for mods you do not have installed/active (e.g. get rid of any "TTW" patches if you aren't running TTW). The reverse also holds true: don't install mods that are not compatible with, or specific to, TTW or FNC if you are playing with them.

* If you have more than one mod that makes any change to the same record or set of records in the vanilla game, then you really need to use a "Merge Patch File" with that collection of mods. Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki "FNV General Mod Use Advice" article. When in doubt, create a "Merge Patch" file anyway.

Please see the 'Vanilla Load Order' entry in the 'First Timer Advice' section; and the 'Common Game Problems' section of the wiki "FNV General Mod Use Advice" article.

If the problem persists, then see either the 'Solutions to Starting the game problems' or the 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

I recommend anyone read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with; especially if this is your first attempt to play a modded FNV or it's been more than a year since you last did so.

-Dubious-