Fallout: New Vegas crashes when entering a loading are

[DunkBody]

Whenever I enter an area that has a loading screen -the one with the roulette-, the game crashes (for example, when entering camp McCarran, Caesar's tent, Crimson caravan company, etc). There's no pop up that explains the error or anything, it just closes entirely. It doesn't happen every time, but it does happen enough for it to make me post about it, and I don't know what's causing this.

 

Here's my PC's specs:

intel core i5 8600k (I have it OC to 4.5 Ghz)

GTX 1070 Ti

DDR4 2666 8gb RAM

 

I am using NVSE with some mods along with NMCs large texture pack and NVSR (mods in launch order):

[x]FalloutNV.esm

|

| ALL DLC

V

[x]YUP - Base Game + ALL DLC.esm

[x]NevadaSkies.esm

[x]NevadaSkies - Ultimate DLC Edition.esp

[x]YUP - NPC Fixes (Base Game + All DLC).esp

[x]The Mod Configuration Menu.esp

 

 

That's it.

Edited July 11, 2019 by DunkBody

[M48A5]

You don't mention having the game made large address aware in order for it to use more than 2GB of RAM. With NMC Large texture pack, that is a necessity.

 

That is probably the cause of the crash. Not enough memory allocated for the game.

[dubiousintent]

The most likely suspect is indeed not using the 4GB Patcher with the Steam version. (DO NOT use it with the GOG version, which is already patched. Applying the patch will break it. Revert to the backup copy created if you did run it.) If not, please see the 'Maximizing use of memory' section of the "FNV General Mod Use Advice" article. If you aren't sure if it was installed or working, just re-run the Patcher again. Make sure it's 4GB Patcher. Won't hurt and it will tell you if it is already patched. (If the Windows ("Task Manager" | Processes) tab entry for the game process has more than 2GB (2,097,152KB) "Memory(Private Working Set)" used, then the 4GB patch is definitely in effect. But being below that threshold doesn't mean it isn't.)

How can you tell if the 4GB Patch (for Steam) is working? The JIP LN NVSE Plugin (recommended for everyone) has a function which can be run from the console: "GetIsLAA" (not case sensitive).
Possible return codes:
* 0=patch is not applied
* 1=patch was applied to the executable, but extra memory is not being allocated
* 2=successfully allocated extra memory from the patch and is fully working.
If "GetIsLAA" is returning code "1", try running the game from a "local administrator" account. If that is successful, you need to move the game install location out of the "C:\Program Files" folder tree, or correct the "permissions" on the folder you moved it to, as you are going to have other problems down the road. Please see the wiki "Installing Games on Windows Vista+" article for details.
Alternatively: if the Windows "Task Manager" indicates the "FalloutNV.exe" program has more than 2GB (2,000,000KB) of "Memory (Private Working Set)", then the 4GB Patcher is in effect. However, to the contrary: less does not mean it is not working. The game simply hasn't needed that much memory as yet.

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.

 

Your "minimal mods" version is missing some stability game fixes. Please see the 'Vanilla Load Order' entry in the 'First Timer Advice' section; the 'Towards Game Stability'; and the 'Common Game Problems' section of the wiki "FNV General Mod Use Advice" article.

If the problem persists, then see either the 'Solutions to Starting the game problems' or the 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

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.

-Dubious-

[DunkBody]

I forgot to mention this, but I already have the game patched for it to run with 4gb of ram

 

the game still crashes either way

Edited July 13, 2019 by DunkBody

[dubiousintent]

So much for the easy solution. Now, have you eliminated all the other solutions provided in the previous response?

 

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

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. That may narrow down the problem.

-Dubious-