[HELP] Fallout Character Overhaul causes crash

[a04771]

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 ELECTRO-CITY - CompletedWorkorders.esm

13 d ELECTRO-CITY - Highways and Byways.esm

14 e Project Nevada - Cyberware.esp

15 f Project Nevada - Extra Options.esm

16 10 FCOMaster.esm

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

18 12 The Mod Configuration Menu.esp

19 13 DYNAVISION 3.esp

20 14 ProjectRealityMkIv5HDR.esp

21 15 Project Nevada - Cyberware Additions.esp

NVKOR_FINAL_JSawyer.esp

22 16 NVKOR_FINAL.esp

23 17 EVE FNV - ALL DLC.esp

NVKOR_FINAL_nosorter.esp

24 18 Radio_KOR.esp

Radio_KOR(noDLC).esp

25 19 Better Casinos.esp

26 1a Casino UnBanner.esp

27 1b Better Burned Man.esp

28 1c FCO - NPC Changes.esp

PC Specs:

CPU: i7-4790

GPU: GTX 1070

RAM: 16GB

OS: Windows 10

So I've downloaded some mods for New Vegas following these instructional videos

I'm currently at Part 6 of this video series, where you install the FOC.

I installed FCO without any options except teeth textures.

Because I've found a post on Reddit that says Glowing ghouls option can cause crashes.

I also tweaked the ini. files as the instruction said. Adding bLoadFaceGenHeadEGTFiles = 1 to both ini files.

Than I installed the FCO and ran LOOT first to organize my load order.

Before launching the game, there were no missing load order.

But when I tried to load my game, the game does not proceed from the loading screen. The roulette spins and background changes, but it stays there.

I've also tried to make a new game and load my older save.

This temporarily solved the loading problem, but after about 5 mins, the game crashes.

When I try to fast travel, or enter a building, or even just opening up my pip-boy causes the game to crash.

When the game crashes, the music repeats constantly but the game freezes.

I've tried formatting my PC twice but this still happens.

Anyone could help me solve this problem?

I've also included pictures for my Mod Organizer.

https://imgur.com/a/Nuzcr

[dubiousintent]

From your report, the problem lies in your save game file is missing a "master file" it is expecting. Which is why a "new game" does start, but then loading the save game crashes.

 

Please see the 'Solutions to Starting the game problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

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.

* 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. (For MO this means do not include in the "Profile", not even "unchecked". The "Profile" determines what gets copied to the "Data" folder for that game session.) 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 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.

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

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

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

-Dubious-