Having problems with crashing around gun runners.

[KingIke22]

So I was having horrible crashing issues so I reinstalled the game, all plugins, and then started a new save. Thing is that every time I go near the gun runners and the surrounding area the game freezes and crashes. it also crashes when I try and fast travel to gun runners. I'm not sure what to do. Here is my load order In case it helps but I'm also using NMM and LOOT.

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 YUP - Base Game + All DLC.esm
11 b Project Nevada - Core.esm
12 c Project Nevada - Equipment.esm
13 d Project Nevada - Rebalance.esp
14 e Project Nevada - Cyberware.esp
15 f Military NV Backpacks.esm
16 10 Ambient Temperature.esm
17 11 SomeguySeries.esm
18 12 Weapons.of.the.New.Millenia.esm
19 13 Military NV Backpacks - Weapons.esp
20 14 YUP - NPC Fixes (Base Game + All DLC).esp
21 15 Readius_NV.esp
22 16 The Mod Configuration Menu.esp
23 17 EVE FNV - ALL DLC.esp
24 18 Vurt's WFO.esp
25 19 WeaponModsExpanded.esp
26 1a ColossusBOSXV.esp
27 1b JTmercgear.esp
28 1c JRougeRangerCoats4Loot.esp
29 1d JRougeRangerCoats4Free.esp
30 1e Military NV Backpacks - Vendor Script Replenish.esp
31 1f Military NV Backpacks - BumBagUseSlot1.esp
32 20 Military NV Backpacks - No Straps.esp
33 21 Project Nevada - Dead Money.esp
34 22 Project Nevada - Honest Hearts.esp
35 23 Project Nevada - Old World Blues.esp
36 24 Project Nevada - Gun Runners' Arsenal.esp
37 25 Project Nevada - WMX.esp
38 26 Alternative Start.esp
39 27 Weapons.of.the.New.Millenia.Store.esp
40 28 T60.esp
41 29 ADAM Complete.esp
42 2a ADAM - MERGE.esp
43 2b NCR Ranger Helmet Neck Cover.esp
44 2c NCR Rearmament v1.5 (Lore).esp
45 2d Project Nevada - Lonesome Road.esp
46 2e NewVegasBounties.esp
47 2f Donta1979 MK117 Prototype Armor.esp
48 30 Weapons.of.the.New.Millenia.Store.LITE.esp
49 31 JTmercgearlite.esp
50 32 XM4RAW.esp
51 33 Geonox_Restored_Riot_Armor_GLOVE_VERSION.esp
52 34 Geonox_Restored_Riot_Armor.esp
53 35 THOR.esp
54 36 Roberts_NewVegas.esp
55 37 M14.esp
56 38 DragsModernGunslinger.esp
57 39 Weapons.of.the.New.Millenia.Cheat.Cabinet.esp
58 3a Weapons.of.the.New.Millenia.Honest.Hearts.Grunt.Patch.esp
59 3b Weapons.of.the.New.Millenia.Leveled.Lists.esp
60 3c XFO - 4bb - Perks - Two per level.esp
61 3d CASM with MCM.esp

[dubiousintent]

Normally I would suspect a mod that changes things around "New Vegas" and Freeside, but don't see any I know do that. So we fall back on basic generalities first to see if any of them solve the problem.

 

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" 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. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

* Are you running Win10? Did you get the "Fall Creator's Update" of 2017 (FCU aka "RedStone 3")? Do you have "New Vegas Stutter Remover" (NVSR) installed? If all three are "true", then please see the 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play' (and other "heap size") entries in the 'Solutions to Performance problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

These "Creator's Updates" are Microsoft's replacement to the old "new release" and "service pack" improvement and bug-fix mechanism. They are scheduled to occur every six months, so they will be in the "Spring" and "Fall" of each year.

The FCU 2017 update was released in mid-November 2017, so a "brand new" system probably did not come with it installed. However, the default configuration is usually to have OS updates automatically installed. (Those usually start being distributed on the second Tuesday of each month, but may take a week or more to get to everyone.) See the MS "Get the Windows 10 Fall Creators Update" article for how to check your version release and manually pull down the update if necessary. It is important to keep your OS always "up to date" to prevent malware infections.

* If you are suddenly having a "slowdown" or lag; or a lack of sound; or problems getting NVSE to load, or really anything new unexpectedly, please see the 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. This may be due to a Windows Update for the "Meltdown and Spectre Vulnerabilities".

* Are you using the 4GB Patcher? If not, please see the 'Maximizing use of memory' section of the wiki "FNV General Mod Use Advice" article.

* The game has "memory leaks". Getting 2-3 hours before a CTD is pretty good. You might want to try using the tool "Memclean", which periodically (you can set the interval; default is every 15 minutes) tells the OS to perform it's built-in "clean up" of memory. It has a "mini-monitor" that displays memory usage. Doesn't seem to hurt and might help.

* If you are using the full 4GB of memory, most likely your CTD problem (now or in the future) is the default "heap size" is too small. It's so common you might as well deal with it now. Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* Move any "inactive" 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.

* 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. 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 Master" errors as well.

FYI: The "pre-order packs" (Caravan, Classic, Mercenary, and Tribal; available now in the "Courier's Stash" addon), are not considered "DLCs" by most mods and "compatibility patches". So their absence should not deter you from using "All DLC Merged" plugins. 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).

* Do not use an "Auto-purge" mod for game play. (That was old advice from before we knew better.) They are designed for debugging by mod creator's only, according to the author of the JIP extensions to NVSE. See the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu', "Cause-2", "Solution-3" entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide for the game settings that do the same job.

* Please see the paragraph about "auto-saves" under the 'Essentials for Getting Started' section of the wiki "FNV General Mod Use Advice" article. If you have been using the built-in "auto-save" feature and you get the endless "roulette wheel" when loading a save game, then your current save game file is corrupted and you will have to either go back to a save before the corruption occurred (hard to tell) or start over.

* 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.

-Dubious-