CTD after loading more than 3 worldspaces

[lolface0512]

Hi guys,

 

I have a bit of an issue here. My game crashes after loading more than three worldspaces in one session. So, if for example I fast travel to the strip, then to goodsprings and enter the saloon, my game will just CTD. Listed below is my mod order. Some of them I installed after starting a new game and I might have lost a couple ones as well, because I had a HDD crash and didn't backup my modlist. Can anyone help fix my issue? I'd rather not start a new game because of this issue, because it runs fine just walking around the map.

 

Modlist:

01 FalloutNV.esm

02 t/m 09 all DLCs and packs

10 Yukichigai's patch.esm

11 New California

12 Beyond boulder dome

13 The Strip Open 1.4

14 D.E.I.M.O.S

15 Fallout Character Overhaul

16 Nevada Skies

17 Yukichigai's patch.esp

18 Fallout Character Overhaul NPC changes

19 FLVJOD-the Strip

20 The Mod Configuration Menu

21 CASM for MCM

22 New California Stash control

23 New California DLC control

24 Pimpboy shine fix

25 Breezes males

26 JIP Companions

27 B42 Bash

28 FCO-beyond boulder dome compatibility fix

29 FCO-glowing one

30 FCO-OHSB NPC edits

31 Darkwads nuclear laser rifle

32 Populated casinos

33 the ARES project

34 BNB

35 Sunny Companion mod

36 Autumn Leaves

37 Breezes Armour

38 GatlingTesla

39 Hk 416 Nuclear Laser Rifle

 

PS: I have tried to use LOOT and have got the 4 GB patch installed(from the start). I also have got ENB series and the NMC texturepack installed, but I already had the problem before installed them, so I don't think these are the cause.

Edited February 24, 2020 by lolface0512

[dubiousintent]

I see you have FNC installed. But that "load order" (LO) doesn't look right to me for FNC (not that I am an expert on it; but don't gloss over the LO of the DLCs). Make sure you are using the FNC compatible versions of mods. As you are already having to re-install the game on a new HDD, take things slowly and make sure you get the basic FNV setup working first, and only then add in the complication of FNC.

 

* 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 but didn't change it for older games); 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.

Alternatively, try using the "[https://www.nexusmods.com/newvegas/mods/66537 New Vegas Tick Fix (NVTF)]" mod instead.

* 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 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu') entry in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* You can also get "out of memory" errors from the graphics system (which is separate from exhausting system memory), even with the game 4GB enabled. The video pipeline is known to have "memory leaks", and these occur faster with "beautification mods". Here the cause is a combination of larger image sizes ("higher resolutions", aka "hi-rez"), hi-rez texture packs for skin, hair, clothes, weapons, and landscape; along with mods that increase the number of NPCS in a given cell. (All those hi-rez texture "personal accessories" get multiplied by the number of Actors.) Please see the wiki "Display resolution versus Image Size" article. While "ENBoost" can help, you may need to switch to lower resolution/ smaller sized images or even lower quality in your game graphics configuration.

* 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 for your overall "load order" anyway.

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.

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. It is designed for someone who has never played a modded PC game before, so it tries to avoid making any assumptions, is kept "up-to-date", and covers years of "lessons learned".

-Dubious-

[lolface0512]

Thank you for all the help, I'll try out your solutions.

[dubiousintent]

Since my initial response to your post, another user has provided the information on installing FNC in "Issue - Unable to install FNC with MO2" under the "Solutions to Starting the game problems" section of the "Mod Conflict Troubleshooting" article.

 

-Dubious-