Fallout New Vegas Crashing with my mods.

[rerabox]

Alright, so I have a lot of mods, which I know is what is causing it to crash, however even when I disable mods it just still seems to crash. I already have the NVAC and the 4GB installed and set up, but nothing seems to work.

 

Here are my PC Specs:
CPU: Intel - Core i7-8700K 3.7GHz 6-Core Processor

CPU Speed: 3.7GHz

Graphics Card: Zotac - GeForce GTX 1070 Ti 8GB Mini Video Card
Amount of RAM: 8GB

Screen Resolution: 1920x1080

Laptop?: No
Version of Windows: Windows 10 Home 64 Bit

Game Location: C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas
Run as Administrator?: No, I run NVSE directly from FOMM

Version of Fallout: Unaware, I cant seem to find it but its the latest version as of 9/19/2018

DLC's: All of them
Mod Tool: Fallout Mod manager (FOMM) Version 0.14.14.4

Game Construction Kit?: None
Helper Programs: NVSE

Gameplay Enhancements: None, I am not using any ENBs or Post Processors and the only thing that appears is the Discord Overlay for if you integrate Discord with your Steam Account.

4GB Patches: Yes, I have FNV 4GB Patcher | 4GB Fallout New Vegas & 4GB Fallout New Vegas Updated
Game Status: Well it does work, I start up the game and go through the whole thing with Doc Mitchell, however, the second I go to the door for the outside, it crashed or freezes up. Even when I load a save outside it crashes/ freezes up.
Steam Verify Files: I have not done that
Hide known file extensions: That is not Enabled

And here is my Load Order:

FalloutNV.esm

DeadMoney.esm

HonestHearts.esm

OldWorldBlues.esm

LonesomeRoad.esm

TribalPack.esm

MercenaryPack.esm

ClassicPack.esm

CaravanPack.esm

GunRunnersArsenal.esm

Project Nevada - Core.esm

Project Nevada - Cyberware.esp

Project Nevada - Equipment.esm

Project Nevada - Rebalance.esp

Project Nevada - Extra Options.esm

FCOMaster.esm

Niner.esm

NVWillow.esp

SomeguySeries.esm

D.E.I.M.O.S..esm

NVR-Strip.esm

RockwellPursuit.esm

The Mod Configuration Menu.esp

Project Nevada - Cyberware Additions.esp

Reactive People - Ultimatum.esp

The Sword of Truth.esp

LevelersHouse.esp

FCO - NPC Changes.esp

FCO - Niner.esp

FCO - OHSB NPC Edits.esp

FCO - Willow.esp

Project Nevada - Rebalance Complete.esp

Project Nevada - All DLC.esp

FCO - GlowingOne.esp

FCO - Willow (Cazy).esp

delilah.esp

FCO - Delilah.esp

Fellout.esp

Russell.esp

FCO - Russell.esp

NewVegasBounties.esp

dD - Enhanced Blood Main NV.esp

NewVegasBountiesII.esp

NewVegasBountiesIII.esp

EVE FNV - ALL DLC.esp

Mission Mojave - Ultimate Edition.esp

UnlimitedCompanions.esp

FPSWeaponWheel.esp

NVR-NPCs.esp

NVR-Version_10.esp

FNV Realistic Wasteland Lighting - All DLC.esp

IMPACT.esp

Project Nevada - IMPACT.esp

WeaponModsExpanded.esp

I also had NMC's Texture Pack for NV LARGE Parts 1, 2 and 3 Enabled at first but they are currently disabled in Nexus Mod Manager only. Those were 2048 x 2048 Textures & 2048 x 2048 Bumpmaps/Normal maps

I thought I figured out what mod was causing the game to crash: A World of Pain (AWOP) mostly because it crashed when it was enabled and worked when it was disabled, but even with that disabled it still doesn't work. I wanna limit how many mods actually are disabled and I do want all of my Graphic/ Texture changing mods to stay enabled to make the game look nicer.

EDIT: Added the Specs to provide more info.

Edited September 19, 2018 by rerabox

[dubiousintent]

Don't confuse "disabled" with "uninstalled". Much depends upon which mod manager you use and how it handles what files are effective in the game "Data" folder. "Disabled" plugins may still be present in the "Data" folder, and if so the game engine will still load them and consequently may CTD.

 

Please see the 'Essentials for Getting Started' and 'Vanilla "Load Order"' entries in the 'First Timer Advice' section; and the 'Towards Game Stability' section and '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 you read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with.

 

Please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as NVSE and it's related plugins, texture replacements (specifically their larger image sizes: 1024x1024, etc.), and "post-processors" like ENB or SweetFX.

* See "How to markup images (etc) in forum posts and comments" article.

-Dubious-

[rerabox]

Don't confuse "disabled" with "uninstalled". Much depends upon which mod manager you use and how it handles what files are effective in the game "Data" folder. "Disabled" plugins may still be present in the "Data" folder, and if so the game engine will still load them and consequently may CTD.

 

Please see the 'Essentials for Getting Started' and 'Vanilla "Load Order"' entries in the 'First Timer Advice' section; and the 'Towards Game Stability' section and '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 you read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with.

 

Please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as NVSE and it's related plugins, texture replacements (specifically their larger image sizes: 1024x1024, etc.), and "post-processors" like ENB or SweetFX.

 

* See "How to markup images (etc) in forum posts and comments" article.

 

-Dubious-

 

 

Alright, I updated the post with more info about my PC and the mods.

[M48A5]

Have you read any of the articles Dubious linked? If so, have you made the changes listed in the articles?

 

If you have made the changes in the articles, is there any change in the game performance?

 

Do you launch the game with NVSE or another program? If so, which one?

 

You can use only one mod that changes the same thing. Having three 4GB patchers does not ensure that the game is patched. You can use only one. Also, read the instructions that come with the patcher.

[rerabox]

I have followed the articles, but now I am getting an Out of Memory error 90% of the time whenever I load up the Outside. Still using the same method and I will run NVSE as Administrator to see if that fixes anything.

 

To provide more information, I downloaded New Vegas Stutter Remover (NVSR) Yukichigai Unofficial Patch (YUP) and it still does nothing.

EDIT: It does nothing still says Out of Memory

Edited September 19, 2018 by rerabox

[rerabox]

Don't confuse "disabled" with "uninstalled". Much depends upon which mod manager you use and how it handles what files are effective in the game "Data" folder. "Disabled" plugins may still be present in the "Data" folder, and if so the game engine will still load them and consequently may CTD.

 

Please see the 'Essentials for Getting Started' and 'Vanilla "Load Order"' entries in the 'First Timer Advice' section; and the 'Towards Game Stability' section and '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 you read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with.

 

Please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as NVSE and it's related plugins, texture replacements (specifically their larger image sizes: 1024x1024, etc.), and "post-processors" like ENB or SweetFX.

 

* See "How to markup images (etc) in forum posts and comments" article.

 

-Dubious-

 

 

Alright, I actually got it to work! Somehow I did it by complete accident. First, I went into my files and saw that the patcher wasn't where the FalloutNV.exe file was, so I moved it there and ran it. Then I ran the Fallout NV 4GB patcher and it got me outside of Doc Mitchells. Then I Saved the game and quit, went to my FNVSE loader shortcut and ran as administrator and it worked perfectly.

 

My question is, what did I do right? Did I need to run the patcher that was in the games files?

[dubiousintent]

Based upon what you recall doing, I would say you solved your problem by: 1) running the "FNV4GB Patcher" with it in the "game root" folder with the game EXE files; 2) launching the game as "Admin", which should only be necessary if you still have the game installed in the default "C:\Program Files" folder. Please see the "Installing Games on Windows Vista+" article in my signature. Leaving the game in that folder tree will cause all kinds of problems. You should not need to run as an "Admin" once the game is moved out of that folder tree.

 

Once you have run the "FNV4GB Patcher", you only need to launch the game (once you have setup for your hardware) from the game executable: "FalloutNV.exe". It will automatically detect and launch NVSE if it is installed correctly.

 

Have no idea what "patcher" you ran before the "FNV4GB Patcher". There isn't one (unless you acquired an earlier version of the game and need to install an update patch; in which case it does need to be installed before FNV4GB). What is the exact file name?

 

-Dubious-

[rerabox]

Based upon what you recall doing, I would say you solved your problem by: 1) running the "FNV4GB Patcher" with it in the "game root" folder with the game EXE files; 2) launching the game as "Admin", which should only be necessary if you still have the game installed in the default "C:\Program Files" folder. Please see the "Installing Games on Windows Vista+" article in my signature. Leaving the game in that folder tree will cause all kinds of problems. You should not need to run as an "Admin" once the game is moved out of that folder tree.

 

Once you have run the "FNV4GB Patcher", you only need to launch the game (once you have setup for your hardware) from the game executable: "FalloutNV.exe". It will automatically detect and launch NVSE if it is installed correctly.

 

Have no idea what "patcher" you ran before the "FNV4GB Patcher". There isn't one (unless you acquired an earlier version of the game and need to install an update patch; in which case it does need to be installed before FNV4GB). What is the exact file name?

 

-Dubious-

 

The patcher was called FalloutNVPatch.exe

[dubiousintent]

That's an older, now superseded version of the FNV4GB Patch. You want to be using the one from here instead. Don't use both. The older one moved the vanilla EXE into another folder and replaced it with one that linked to the moved file. The new one eliminates the move so it will now work with other mods like ENB seamlessly.

 

Because you ran both, I'm not sure just what got changed. Suggest you "verify local files" and patch correctly again.

 

-Dubious-