Game crashing after Bethesda slide

[fredbob392]

Hi, I recently reinstalled New Vegas and downloaded a bunch of my favorite mods. It worked fine, but I realized I'd forgotten to click to activate some of the ESM and ESPs. Now that I've activated the rest of them, the game won't load without crashing. Unfortunately, I don't' remember what specifically I had active while it was working and what I activated after. If I provide my load order, would anyone be able to give me a suggestion of what might be the issue? It's been about 5 years since I last did a full play through of New Vegas, so I apologize if I made any obvious mistakes.

 

FalloutNV.esm

DeadMoney.esm

HonestHearts.esm

OldWorldBlues.esm

LonesomeRoad.esm

GunRunnersArsenal.esm

ClassicPack.esm

MercenaryPack.esm

TribalPack.esm

CaravanPack.esm

YUP - Base Game + All DLC.esm

IWR.esm

MoreMojave.esm

ELECTRO-CITY - CompletedWorkorders.esm

NVInteriors_Core.esm

TLD_Travelers.esm

NVInteriors_ComboEdition.esm

Lucky38Suite_Reloaded.esm

SomeguySeries.esm

ELECTRO-CITY - Highways and Byways.esm

Niner.esm

NVStripOpen.esm

NVR-Strip.esm

NVWillow.esp

JokerineDiner.esm

Project Nevada - Core.esm

Project Nevada - Equipment.esm

Project Nevada - Rebalance.esp

Project Nevada - Cyberware.esp

Project Nevada - Extra Options.esm

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

CASM.esp

The Mod Configuration Menu.esp

NVR-Version_10.esp

Project Nevada - Dead Money.esp

Project Nevada - Honest Hearts.esp

Project Nevada - Gun Runners' Arsenal.esp

Project Nevada - Cyberware Additions.esp

Project Nevada - Rebalance Complete.esp

Project Nevada - All DLC.esp

Oven Cooking.esp

Uncut Wasteland.esp

outsidebets.esp

CNR_Beta.esp

IWR - Rebuilt.esp

StripOpenMain.esp

NewVegasBounties.esp

NewVegasBountiesII.esp

TheInheritance.esp

1nivVSLArmors.esp

GRA - The Right to Bear Arms.esp

1nivPNSLPatch.esp

FlashlightNVSE.esp

MiscItemIconsNV.esp

EVE FNV - ALL DLC.esp

Project Nevada - EVE All DLC.esp

Russell.esp

CourierCacheWSE.esp

NevadaSkies.esp

NVR-NPCs.esp

Badmothaf*#@a.esp

AtomicWranglerCrier.esp

SunnyCompanion.esp

WastelandNecklaceCollection.esp

UnlimitedCompanions.esp

PipBoysToThePeople.esp

LevelersHouse.esp

Project Nevada - Gun Runners' Arsenal (Rebalance).esp

Couriers Blunder + Rifle.esp

NVR-ELECTRO-CTIY_Patch.esp

NCRTrooperOverhaul.esp

Roberts_NewVegas.esp

MoreMojave - NVBI Patch.esp

Novac Motel - Couriers Room.esp

CasinoHeistPack.esp

LilMacNV.esp

DLC Weapon Integration.esp

FNVLODGen.esp

tmzLODadditions.esp

Total active plugins: 79

Total plugins: 97

[dubiousintent]

You should always start troubleshooting from any error messages you can see. (They are your best "clue"; and why they exist at all.) Reporting such messages accurately is an essential first step.

Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog because the game engine was not able to predictably handle the error. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article.

Logs generated by the game itself (not Windows) are found in the game folder, where the "FalloutNV.EXE" file is located. They generally have the ".log" file extension, or a filename with "_log" in the name and a ".txt" extension.

A "CTD" is a "fatal" error, meaning the program/game did not know how to handle the error, nor how to proceed from that point; and shutdown to let the Windows Operating System (OS) take over again from the "desktop". The only thing worse is the so-called "Blue Screen of Death (BSoD)", which means the OS itself encountered a similar fatal error and entire computer has to be "rebooted"("reset" switch or "power off-for-10-seconds-and-on-again") to return to function. DO NOT attempt to resume the game again from the point of a CTD, as your system memory is in an unpredictable state and make cause "save game" corruption even if it does get past the point where it crashed before. Reboot first.

* Move any "inactive/disabled" plugins out of the game "Data" folder. They count against the "plugin cap"(see Smaller 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.

In the meantime, please see the 'First Timer Advice' section; as well as the 'Towards Game Stability' and the 'Common Game Problems' sections of the wiki "FNV General Mod Use Advice" article.

If the problem persists, then work through 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 set it up. 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". It is NOT a list of various mods to install that happen to work on the author's machine. It addresses fundamentals underlying how to get the basic game and mods to work together. At least 90% of everything I post in the "Technical Support" sub-forum is already in that article.

-Dubious-

[fredbob392]

Ok, what the error said was

Faulting application name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed

Faulting module name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed

Exception code: 0xc0000005

Fault offset: 0x002fcf03

Faulting process id: 0x2bec

Faulting application start time: 0x01d6c1f8b38f5834

Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe

Googling that exception code got me a lot of info. Gonna try a few things, hopefully one of them works. If you have anything you'd recommend I try from that, I'll give it a shot

EDIT:

Tried verifying integrity of game files, updating drivers, removing inactive plugins, and installed NVTF and Mod Limit Fix. Nothing so far. From what I've read, it sounds like the 4GB patch should fix this, but I already installed it and it hasn't. The thing is, I can't remember if I installed if before or after New Vegas started crashing, so I'm trying to figure out if there's a way to uninstall it just to see if it makes a difference

Edited November 24, 2020 by fredbob392

[dubiousintent]

* You installed Steam to it's default location. (GOG is not a problem as it places the game correctly.) Consequently, 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. Among other things, later versions of Windows (since the game was released) force files in "system protected" folder trees to be "read only" regardless of how you set them manually. It includes instructions on how to correctly move the Steam folders out of that folder path.

Don't move it to a folder under "User\Documents" either, as "executable" files are not permitted to run from there for similar "anti-malware" reasons.

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.

* "Windows Exception code: 0xc0000005". The "Faulting Application" is often the victim of another program rather than the actual culprit, making it virtually impossible for the user to trace the source. In at least one instance it appears to be caused by VWD/LOD files that had not been regenerated (when caught by NVAC as "DISABLED _LOD_ERR"). Any recent update since the last time it was working correctly is suspect, as are viruses even if you have anti-virus (AV) running. Run AV from multiple sources when checking for infections. There are a number of free online scanners on the internet (though they are all going to try to sell you their services after the first time).

You may need to exclude FNV from "Data Execution Protection (DEP)" and configure " Windows Defender Exploit Guard (WDEG)" (or Microsoft's "Enhanced Mitigation Experience Toolkit (EMET)" for Win7). Please see "Issue - NVSE - fails to load after update KB4058043 to Win10 FCU v1709" under the 'Solutions to Starting the game problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

Try turning off any unnecessary background processes, such as "anti-virus" or "anti-malware" programs (unneeded if you are running your game in "offline" mode once you have scanned since the last connection), multiplayer "overlays" like "OverWolf" (this is single-player after all), the Steam overlay, etc., at least on a temporary basis to see if they are interfering. There are also tools (often called "Game Boosters") to help you determine "unnecessary when offline" Windows services you can temporarily shut down.

It is also possible that any recent change to your mods (such as updates) or your existing "load order" (such as additions or removals) has caused a corruption of the current save game file. Try going back to a save game from before the problem started. Often starting a "new game" with a vanilla test character can help confirm if the problem lies in the current load order.

 

* How can you tell if the 4GB Patch is working?
: Look for the "Data\NVSE\NVSE_CONFIG.INI" file which for GOG users will otherwise will not get created without the "nvse_steam_loader". Check the "nvse_steam_loader.log" file (in the game root folder with the FalloutNV.EXE file) for errors.
: The [http://www.nexusmods.com/newvegas/mods/58277 JIP LN NVSE Plugin] 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 successfull, you need to move the game install location out of the "C:\Program Files" folder tree, or correct the "permissions" on it's folder if you have moved it, 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.

-Dubious-

[fredbob392]

Ok, if I understood correctly one thing you said was that it might be LOD related. I had a couple of LOD mods on, turned them off and the game worked fine. Looked a little further into it, apparently Someguy's Russell follower conflicts with one of them. Unfortunate, I was hoping to have New Vegas look a little better this time around, but ultimately I'd rather have another well written follower than have a somewhat better looking game. Thank you for everything!

[dubiousintent]

Your should be able to have both.

 

If you add (or remove) any VWD/LOD textures (such as NMC, Vurt's WFO, or Ojo Bueno), please see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the need to run both TES4LL and FNVLODGen; or xLODGen - Terrain LOD beta for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL. Also recommend you read the 'LOD/VWD Texture Packs' section of the wiki "FNV General Mod Use Advice" article first.

 

There are some "quirks" in specific locations of the Someguy mods. Be sure to check out the mod comments page when you encounter them.

-Dubious-