Need help with mods and fps/crash issues

[Deleted51168816User]

So I'm new to modding and I finally got all my mods to work and my game looks amazing, however I get bad mini freezes throughout the game and it sometimes results in a crash. My fps also dips every 20 seconds or so and over a while I just can't handle it. Should I delete any of these mods that could help the problem?

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 YUP - Base Game + All DLC.esm

11 b Interior Lighting Overhaul - Core.esm

12 c Project Nevada - Core.esm

13 d IWR.esm

14 e ELECTRO-CITY - CompletedWorkorders.esm

15 f FCOMaster.esm

16 10 Project Nevada - Equipment.esm

17 11 Project Nevada - Rebalance.esp

18 12 ELECTRO-CITY - Highways and Byways.esm

19 13 Project Nevada - Cyberware.esp

20 14 Interior Lighting Overhaul - L38PS.esm

21 15 NVStripOpen.esm

22 16 NevadaSkies.esm

23 17 YUP - NPC Fixes (Base Game + All DLC).esp

24 18 B42Inertia.esp

25 19 Mission Mojave - Ultimate Edition.esp

26 1a EVE FNV - ALL DLC.esp

27 1b dD - Enhanced Blood Main NV.esp

28 1c FCO - NPC Changes.esp

WeaponModsExpanded.esp

29 1d IWR - Rebuilt.esp

30 1e ADAM Complete.esp

31 1f Lucky 38 Lights.esp

32 20 ADAM - MERGE.esp

33 21 NCRTrooperOverhaul.esp

34 22 Book of Steel.esp

35 23 boa ncrpahelmet.esp

36 24 Boacombat2glove.esp

37 25 ADAM - Trooper Gloves.esp

FCO - Delilah.esp

FCO - Niner.esp

FCO - OHSB NPC Edits.esp

FCO - Russell.esp

FCO - Willow (Cazy).esp

FCO - Willow.esp

38 26 NukaCola-Ojo.esp

39 27 ILO - PipBoy Light.esp

40 28 ILO - YUP Patch.esp

41 29 PerkEveryLevel.esp

42 2a Project Nevada - Dead Money.esp

43 2b Project Nevada - Honest Hearts.esp

WMX-DLCMerged.esp

44 2c Project Nevada - Old World Blues.esp

45 2d Project Nevada - Lonesome Road.esp

46 2e Project Nevada - Gun Runners' Arsenal.esp

47 2f Project Nevada - EVE All DLC.esp

48 30 UnlimitedCompanions.esp

49 31 The Mod Configuration Menu.esp

50 32 christinecos.esp

51 33 tkEyelashesFNV.esp

52 34 tkEyelashesFNV_FemalesOnly.esp

53 35 Better Burned Man.esp

54 36 PipBoyLight.esp

55 37 GRA-WRP-Patch-Two_Unofficial.esp

56 38 MiscItemIconsNV.esp

57 39 Distributed Necklaces and Chains.esp

58 3a FCO - Roberts Patch.esp

59 3b populatedcasino.esp

60 3c NevadaSkies - Blueberry Nights.esp

61 3d Sprint Mod.esp

62 3e FOVSlider.esp

63 3f StripOpenMain.esp

64 40 FasterAccessToLucky38.esp

65 41 Lucky 38 Reloading and Cooking.esp

66 42 Wearable SS Deputy Badge.esp

67 43 ImmersivePickupSoundsFNV.esp

WMX-ArenovalisTextures.esp

WMX-EVE-AllDLCMerged.esp

68 44 Interior Lighting Overhaul - Ultimate Edition.esp

69 45 ILO - GS Shack.esp

70 46 NevadaSkies - Ultimate DLC Edition.esp

I'm also on Windows 10, any help for that ?

Edited February 2, 2018 by Guest

[dubiousintent]

First of all, let's clean up your "load order" a bit, so you have a good foundation. While that isn't horrible, it could be better. It will also eliminate possible complicating factors.

 

All of the following may not apply to your specific situation, but are worth repeating anyway.

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

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

* Are you running Win10? Did you get the "Fall Creator's Update" (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.

The FCU 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.

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

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

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

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

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

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

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

Now, with that out of the way, let's move on to your "micro-stutters" and CTDs (which are separate issues).

 

For the CTDs, Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. Pay particular attention to the several solutions referring to "heap size".

 

For the FPS drops, there will always be some. Don't concern yourself unless they get down around 20FPS. Otherwise, stop monitoring it and enjoy the game. If it does drop enough to be a problem, please see the 'Solutions to Performance problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

Re: Stuttering or "micro-stutters". All visual stuttering problems are caused by the video stream having to wait for the "art assets" required to render the display. Mostly these are due to the hard disk drive being orders of magnitude slower than VRAM, with System RAM (e.g. "ENBoost") and "solid state drives" (SSDs) being in between. Keep in mind that this game was designed for older PC and XBox console systems, and it is now possible for your new "latest and greatest" gaming machine to be faster than it can handle. There are internal design choices that cannot be overcome. The following are "mitigations" that have been found to help some people.

Please see the following entries under the 'Solutions to Performance problems' section in the wiki Fallout NV Mod Conflict Troubleshooting" guide if you haven't already.
* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'
* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed'
* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'
* 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' for other settings that can indirectly affect micro-stutter.
* There are also some NVSR configuration suggestions under the 'Issue: Game in slow motion' and entries.
* The 'Issue: What's with these Solid Green billboard signs in the distance (LOD)?' entry under the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section can also help if your problems started after you installed VWD/LOD texture packages.

As you can see, there are a number of things that can underlie your problem. If one of these doesn't fix it, I would be interested to hear about any eventual solution that does.

-Dubious-

Edited February 2, 2018 by dubiousintent