Just Another Crash Issue Thread

[BenTheGamingGuy]

- (Main Topic) -

 

Hi yall, I'm 38 hours into a good playthrough, although now it's become unplayable due to crashing which I think is due to memory. The crashes always occur when FNV hits 2.7GB of memory usage in task manager, so I'm thinking the 4gb patcher isn't working?

 

On a side note that may be related, I've had an audio issue where the audio of some actions (holstering, pip boy, walking) is delayed by a few seconds every once and a while. I was able to ignore it but I wonder if it has something to do with the memory also? Music isn't effected, neither is everything outside of the game. I use Voicemeeter Potato too if that's something important.

 

- (Side stuff, not my focus rn) -

 

On ANOTHER side note (not as important), archive invalidation keeps screwing up my pip boy screen (I've started using the manual archive invalidation from Nexus over the inbuilt Vortex one as vortex wasn't seeming to work properly). LOD is also being screwed up despite using LodGen before playing, as it seems some Lods aren't loading in (walls of vegas, most of helios) and the distance for loading things in has decreased (I probably should check the launcher or ini, but I'm unable to launch the original launcher because of nvse and 4gb patch).

 

/

 

Here's some other stuff, if anything is useful:

 

PC Specs: Ryzen 5900 12 core, RTX 3070 8gb, 16gb Ram

 

Load Order:

# Automatically generated by Vortex

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

FCOMaster.esm

SomeguySeries.esm

NVInteriors_Core.esm

BraveNewWorld.esm

New Vegas Redesigned 3.esm

Gomorrah Redesigned v2.esp

TLD_Travelers.esm

NVInteriors_ComboEdition.esm

More Perks.esm

More Perks for Dead Money.esm

A World of Pain Revised.esm

More Perks for Honest Hearts.esm

Afterschool Special.esm

Bitter Springs Redesigned.esp

More Traits.esm

More Perks for Old World Blues.esm

Project Nevada - Core.esm

Project Nevada - Equipment.esm

DragsVGUArmorBase.esm

More Perks for Companions.esm

WeAreLegion.esm

GreatKhanGreatOverhaul.esm

Project Nevada - Rebalance.esp

CFWNV.esm

Weapons.of.the.New.Millenia.esm

oHUD.esm

Unofficial Patch NVSE.esp

Vurt's WFO.esp

AAM.esp

Zan_AutoPurge_SmartAgro_NV.esp

B42Descriptions.esp

New Vegas Redesigned 3.esp

Psydeffexx Weapons pack - No Custom Ammo.esp

Psydeffexx Weapons pack.esp

WeaponModsExpanded.esp

More Perks Update.esp

CNR_Beta.esp

IMPACT.esp

Project Nevada - IMPACT.esp

WMX-DLCMerged.esp

NewVegasUncut 123457 Merged.esp

Tutorial Killer.esp

FO4 Power Armors - FNV Compatibility Edition.esp

More Perks for Companions Update.esp

More Perks for Dead Money Update.esp

More Perks for Old World Blues Update.esp

CourierCacheWSE.esp

MainStoryAlterations.esp

DragsNPCOverhaul.esp

Clarity.esp

NevadaSkies.esp

MojaveSandyDesert.esp

More Traits Update.esp

More Perks for Honest Hearts Update.esp

FNV Customizable Companion (P.A.L. 8000) DLC.esp

FNV Customizable Companion (P.A.L. 8000).esp

TTW Customizable Companion (P.A.L. 8000).esp

classicambientmusic.esp

NewVegasBounties.esp

NewVegasBountiesII.esp

TheInheritance.esp

Russell.esp

NukaColaVenderLightDisabler.esp

BraveNewWorld-YUP.esp

RaiderOverhaulPreview.esp

WeAreLegion.esp

BoomersGoBoom.esp

NVR3_ProjectNevadaEquipment Patch.esp

B42Inertia.esp

ImmersiveRecoil.esp

NPCs Can Miss.esp

More Realistic Aiming.esp

Project Nevada - Dead Money.esp

Project Nevada - Gun Runners' Arsenal.esp

Project Nevada - Honest Hearts.esp

Project Nevada - Lonesome Road.esp

Project Nevada - Old World Blues (No Cyberware).esp

Simple Reputation and Disguises.esp

TrooperOverhaul-Dragbody.esp

Delay DLC - DM + HH + OWB + LR + GRA.esp

NCRTrooperOverhaul.esp

NVR3_TrooperOverhaulDragbody Patch.esp

Drags20ArmorPack.esp

Drags20ArmorPackNoInteriors.esp

Weapons.of.the.New.Millenia.Store.LITE.esp

CourierRangerArmorV2.esp

BrotherhoodReforged.esp

BraveNewWorld-PN-Equipment.esp

CFW-DLC.esp

The Weapon Mod Menu.esp

WMX-ArenovalisTextures.esp

WMX-ModernWeapons.esp

WMX-POPMerged.esp

Weapons.of.the.New.Millenia.Honest.Hearts.Grunt.Patch.esp

Weapons.of.the.New.Millenia.Leveled.Lists.esp

FOVSlider.esp

JIP Improved Recipe Menu.esp

JustModsAssorted.esp

Quickthrow.esp

WEATHER RUDY ENB.esp

The Mod Configuration Menu.esp

DarNifiedUINV.esp

FCO - GlowingOne.esp

Asurah_Reanimation_Handgrips.esp

Asurah_reanimation.esp

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

NVR3_YUP Patch.esp

FNVLODGen.esp

Any help would be appreciated if possible, if not, well I'm gonna start modding FO4 aha :)

[M48A5]

This is a problem: TTW Customizable Companion (P.A.L. 8000).esp, since you don't have TTW.

[BenTheGamingGuy]

This is a problem: TTW Customizable Companion (P.A.L. 8000).esp, since you don't have TTW.

That shouldn't be a problem, it's actually disabled + the esp was deleted, it's just vortex doesn't want to undetect it

[gnarly1]

Firstly, ensure you have all the recommended bug and engine fixes/utilities installed, as listed in the Viva New Vegas documentation under the Utilities and Bug Fixes sections.

 

Then have a look at the Mods to Avoid section as you're using some of those mods. I'm not saying don't use them, but one of more of them could be the source of your problem.

[dubiousintent]

* Did you install Steam to it's default location? (GOG is not a problem as it places the game correctly.) 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" 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.

* Do you have "New Vegas Stutter Remover" (NVSR) installed? If so, please see the 'Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)' and 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' entries in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. Note the default NVSR settings do not work with Win10, but there are some recommended by the author for Win10 further down in the article.

:* Currently, the recommended alternative to NVSR, if you are running Win7 or Win10, is to try using the "New Vegas Tick Fix (NVTF)" and "New Vegas Heap Replacer (NVHR)" mods instead. However, until NVTF includes the option, you may want to continue to use NVSR for the "iThreadsFixedToCPUs" setting. Note though, use of NVSR along with NVTF is unsupported.

* Related to the NVSR problem, for problems AFTER a save game is loaded see also 'Issue: Incomplete save game load' in the "Troubleshooting" guide.

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

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

* You can also get "out of memory" errors from the graphics system (which is separate from exhausting system memory), even with the game 4GB enabled. The video pipeline is known to have "memory leaks", and these occur faster with "beautification mods". Here the cause is a combination of larger image sizes ("higher resolutions", aka "hi-rez"), hi-rez texture packs for skin, hair, clothes, weapons, and landscape; along with mods that increase the number of NPCs in a given cell. (All those hi-rez texture "personal accessories" get multiplied by the number of Actors.) Please see the wiki "Display resolution versus Image Size" article. While "ENBoost" can help, you may need to switch to lower resolution/ smaller sized images or even lower quality in your game graphics configuration.

 

* 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. If those plugins without the "mod index" numbers are "deactivated" by the "Bash Patch", then you failed to have them "ghosted" by "Wrye Bash/Flash" when you built your "Bashed Patch". Please see the wiki "Bashed Patch file with Marked Mergeables" article.

* The mod FNV Mod Limit Fix (20 Apr 2020) fixes the smaller "plugin cap" problem by increasing (4x) the maximum number of file handles to the common "2048" normally used by Windows to enable the full 255 plugin limit of 32-bit games. This appears to have the side benefit of smoother (possibly a few FPS faster) play and reduced or eliminated audio stutter reported by some users.

* Any time you remove a plugin from your current play-through "load order" you risk corrupting your save game files. This is because plugins typically store information there as to the state of their variables and quests. If you picked up a unique (non-vanilla) item added by a mod, that item (like any item you pick up) is stored in the save game, but also requires the plugin it came from to be available as that item's "source records". In the case of "body replacement" mods, especially if they use a "custom race", it is highly likely you will have to start over if you can't switch back to a vanilla race first. Hence the general advice to never remove a plugin from your current game.

 

(38 hours is not much time invested in this game. It will easily provide hundreds of hours of play. Starting over with a properly configured setup is well worth the sacrifice.)

Report other problems after you get the previous suggestions implemented.

 

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

 

-Dubious-

[BenTheGamingGuy]

T

 

* Did you install Steam to it's default location? (GOG is not a problem as it places the game correctly.) 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" 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.

* Do you have "New Vegas Stutter Remover" (NVSR) installed? If so, please see the 'Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)' and 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' entries in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. Note the default NVSR settings do not work with Win10, but there are some recommended by the author for Win10 further down in the article.

:* Currently, the recommended alternative to NVSR, if you are running Win7 or Win10, is to try using the "New Vegas Tick Fix (NVTF)" and "New Vegas Heap Replacer (NVHR)" mods instead. However, until NVTF includes the option, you may want to continue to use NVSR for the "iThreadsFixedToCPUs" setting. Note though, use of NVSR along with NVTF is unsupported.

* Related to the NVSR problem, for problems AFTER a save game is loaded see also 'Issue: Incomplete save game load' in the "Troubleshooting" guide.

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

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

* You can also get "out of memory" errors from the graphics system (which is separate from exhausting system memory), even with the game 4GB enabled. The video pipeline is known to have "memory leaks", and these occur faster with "beautification mods". Here the cause is a combination of larger image sizes ("higher resolutions", aka "hi-rez"), hi-rez texture packs for skin, hair, clothes, weapons, and landscape; along with mods that increase the number of NPCs in a given cell. (All those hi-rez texture "personal accessories" get multiplied by the number of Actors.) Please see the wiki "Display resolution versus Image Size" article. While "ENBoost" can help, you may need to switch to lower resolution/ smaller sized images or even lower quality in your game graphics configuration.

 

* 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. If those plugins without the "mod index" numbers are "deactivated" by the "Bash Patch", then you failed to have them "ghosted" by "Wrye Bash/Flash" when you built your "Bashed Patch". Please see the wiki "Bashed Patch file with Marked Mergeables" article.

* The mod FNV Mod Limit Fix (20 Apr 2020) fixes the smaller "plugin cap" problem by increasing (4x) the maximum number of file handles to the common "2048" normally used by Windows to enable the full 255 plugin limit of 32-bit games. This appears to have the side benefit of smoother (possibly a few FPS faster) play and reduced or eliminated audio stutter reported by some users.

* Any time you remove a plugin from your current play-through "load order" you risk corrupting your save game files. This is because plugins typically store information there as to the state of their variables and quests. If you picked up a unique (non-vanilla) item added by a mod, that item (like any item you pick up) is stored in the save game, but also requires the plugin it came from to be available as that item's "source records". In the case of "body replacement" mods, especially if they use a "custom race", it is highly likely you will have to start over if you can't switch back to a vanilla race first. Hence the general advice to never remove a plugin from your current game.

 

(38 hours is not much time invested in this game. It will easily provide hundreds of hours of play. Starting over with a properly configured setup is well worth the sacrifice.)

Report other problems after you get the previous suggestions implemented.

 

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

 

-Dubious-

Thank you for the great reply. I will start looking into all you've mentioned.

[BenTheGamingGuy]

Returning to say that I've tried a couple suggestions in the CTD section with not much results (I think I've eliminated the audio issue though), however I started a new save with the load order and replicated what was causing the crashes on my main save - just fast traveling to a far location. I got the exact same result of a crash. The other fix idea I have yet to try is making merge patches, mainly because I'm very unfamiliar with the practice (the S.T.E.P guide is nice, but intimidating), although I think it would benefit as I am using a lot of things that add to leveling lists.

 

I also removed ALL disabled esps and found that 4gb was successfully installed. Heap size has also been increased to 496 in NVSE, although according to NVHR, doing that is pointless because it already manages that, but oh well. "bPreemptivelyUnloadCells=1" has also been added to ini files as per one of the suggestions (isn't that also the same thing?).

 

Thank you for your help. I'll update after I figure out merge patches.

 

T

 

* Did you install Steam to it's default location? (GOG is not a problem as it places the game correctly.) 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" 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.

* Do you have "New Vegas Stutter Remover" (NVSR) installed? If so, please see the 'Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)' and 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' entries in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. Note the default NVSR settings do not work with Win10, but there are some recommended by the author for Win10 further down in the article.

:* Currently, the recommended alternative to NVSR, if you are running Win7 or Win10, is to try using the "New Vegas Tick Fix (NVTF)" and "New Vegas Heap Replacer (NVHR)" mods instead. However, until NVTF includes the option, you may want to continue to use NVSR for the "iThreadsFixedToCPUs" setting. Note though, use of NVSR along with NVTF is unsupported.

* Related to the NVSR problem, for problems AFTER a save game is loaded see also 'Issue: Incomplete save game load' in the "Troubleshooting" guide.

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

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

* You can also get "out of memory" errors from the graphics system (which is separate from exhausting system memory), even with the game 4GB enabled. The video pipeline is known to have "memory leaks", and these occur faster with "beautification mods". Here the cause is a combination of larger image sizes ("higher resolutions", aka "hi-rez"), hi-rez texture packs for skin, hair, clothes, weapons, and landscape; along with mods that increase the number of NPCs in a given cell. (All those hi-rez texture "personal accessories" get multiplied by the number of Actors.) Please see the wiki "Display resolution versus Image Size" article. While "ENBoost" can help, you may need to switch to lower resolution/ smaller sized images or even lower quality in your game graphics configuration.

 

* 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. If those plugins without the "mod index" numbers are "deactivated" by the "Bash Patch", then you failed to have them "ghosted" by "Wrye Bash/Flash" when you built your "Bashed Patch". Please see the wiki "Bashed Patch file with Marked Mergeables" article.

* The mod FNV Mod Limit Fix (20 Apr 2020) fixes the smaller "plugin cap" problem by increasing (4x) the maximum number of file handles to the common "2048" normally used by Windows to enable the full 255 plugin limit of 32-bit games. This appears to have the side benefit of smoother (possibly a few FPS faster) play and reduced or eliminated audio stutter reported by some users.

* Any time you remove a plugin from your current play-through "load order" you risk corrupting your save game files. This is because plugins typically store information there as to the state of their variables and quests. If you picked up a unique (non-vanilla) item added by a mod, that item (like any item you pick up) is stored in the save game, but also requires the plugin it came from to be available as that item's "source records". In the case of "body replacement" mods, especially if they use a "custom race", it is highly likely you will have to start over if you can't switch back to a vanilla race first. Hence the general advice to never remove a plugin from your current game.

 

(38 hours is not much time invested in this game. It will easily provide hundreds of hours of play. Starting over with a properly configured setup is well worth the sacrifice.)

Report other problems after you get the previous suggestions implemented.

 

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

 

-Dubious-

Thank you for the great reply. I will start looking into all you've mentioned.

[dubiousintent]

You should always start troubleshooting from any error messages you can see. (They are your best "clue"; and why they exist at all.) We don't expect you to be able to interpret those messages, but reporting such accurately and in detail (i.e. screenshots) 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 both the game engine and Windows itself 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.

Re: problems after "fast travel". 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.

-Dubious-