Game Crashing and "Out of Memory" when I use a texture pack.

[SimJuan]

Every time I try to play the game with a texture pack the "out of memory" error appears. Also when entering rooms the game will crash.

 

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 FCOMaster.esm
12 c Project Nevada - Core.esm
13 d Project Nevada - Equipment.esm
Project Nevada - Rebalance.esp
14 e Project Nevada - Cyberware.esp
15 f YUP - NPC Fixes (Base Game + All DLC).esp
16 10 Zan_AutoPurge_SmartAgro_NV.esp
17 11 Performance Of The Gods.esp
FCO - Russell.esp
18 12 Reload Sounds.esp
19 13 The Mod Configuration Menu.esp
20 14 FOVSlider.esp
21 15 ENB Performance Boost.esp
22 16 Mission Mojave - Ultimate Edition.esp
23 17 F4Quickloot.esp
24 18 FCO - NPC Changes.esp
25 19 FCO - OHSB NPC Edits.esp
26 1a ENB Performance Booster2.esp
27 1b ENB Performance Booster3.esp
28 1c ENB Performance Booster4.esp
29 1d ENB Performance Booster5.esp
30 1e CASM.esp
31 1f Project Nevada - Dead Money.esp
32 20 Project Nevada - Gun Runners' Arsenal.esp
33 21 Project Nevada - Honest Hearts.esp
YUP - PN.esp
34 22 Project Nevada - Lonesome Road.esp
35 23 Project Nevada - Old World Blues.esp
Project Nevada - Rebalance [Rarity Fixes].esp
36 24 ShilohDS-Color Maps and Icons.esp
37 25 dD - Enhanced Blood Main NV.esp
38 26 FNV Realistic Wasteland Lighting - All DLC.esp
39 27 NukaCola-Ojo.esp

[dubiousintent]

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.

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

You really need to use a "Merge Patch File" with that collection of mods. Please see the 'Maximizing use of memory', 'Third Rule: The Rule of One', 'Essentials for Getting Started' entries and 'Merge Patch File' section of the wiki "FNV General Mod Use Advice" article.

Recommend you get a stable game configuration before you complicate the situation with ENB. In addition, layering on multiple "performance" mods tends to create more problems than it solves unless they do not "overlap" in how they supposedly improve performance. Unless you have a really old system, "performance mods" are not going to help with your CTDs. Post your hardware info if you still think that is the problem.

 

"Texture packs" don't usually show up in the "load order". (They are replacing vanilla assets; thus they overwrite existing files.) And the issue with them is what size/resolution of the images you are using. Larger/"hi-rez" textures require more pixels, and larger screen display monitors multiply that requirement in a non-linear way. While your hardware may technically be able to handle it, the game is 7 years old, designed for Windows Vista with maximum screen displays of 1920x1080, with default image sizes of 512x512 pixels. The game engine texture cache tends to be the bottleneck: causing "stutter" and "out of memory" CTDs.

-Dubious-

Edited January 12, 2018 by dubiousintent