Game crashing during load screens; FNV appears broken

[VAULTRENEGADE]

I'm at my witts end

 

It seems problems thought once resolved (mentioned in a previous topic here) have returned with a vengeance. In short, New Vegas once again appears broken for me. I've began experiencing:

 

a). frequent crashing during load screens

 

b). infinite load screens

 

c). a broken game in the rare case a load screen actually finishes; missing sounds/ world items. (at one point I was able to save when this happened and I reloaded from it- the problems appeared to be temporarily resolved)

 

The aforementioned problems occur nearly any time I fast travel to or enter an area. Contrary to the solution noted in bullet "c).", sometimes saves either fail to load or crash shortly thereafter. (However, none are actually labelled as corrupted following a crash)

 

Given the sometimes random (and thus far un-fixable) nature of these problems, I've had major difficulty diagnosing the root cause. I'm led to believe it's either the result of corrupted saves or low memory. Keep in mind that in my last post, I started experiencing problems after loading a number of mods containing plugins roughly 30 hours into my character as well as removing a few plugins (obviously a mistake that can lead to a corrupt save). Shortly thereafter, I removed enboost and received one occurrence of the "out of memory" glitch/ crash. Since then I've drastically reduced the size of my load order and things appeared to resolve for about 3 hours. During trouble shooting today, I even went as far as to remove all my texture mods (easily the greatest consumption of in-game memory) and my problems STILL persist!!! Am I correct in assuming this would indicate the presence of a corrupted save rather than low memory?

 

I have yet to test my load order with a new character which will be my next step (I'll follow up with the results), but in the mean time I'm hoping someone can provide me with some help/ insight here. Please keep in mind I'm already properly utilizing NVAC, NVSR, 4GB PATCH, NVSE/ SHESON'S MEMORY PATCH (currently set to a heap of 420mb). I've also been utilizing cell purging from the start via bPreemptivelyUnloadCells=1, bSelectivePurgeUnusedOnFastTravel=1 (along with other .ini tweaks)

 

 

My Specs: NVIDIA GTX 1070 (8gb V-RAM), i7-8750H, 16gb RAM

 

windows 10

steam version of the game boots from a 1TB SSD (NOT the default "C drive" install path)

 

 

My load order:

 

(the nomenclature "07" indicates a plugin that I've either created or heavily modified. Also keep in mind some of the plugin names may seem obscure due to the fact they are solely meant for TTW 2.9 or VR)

 

 

FalloutNV.esm
DeadMoney.esm
HonestHearts.esm
OldWorldBlues.esm
LonesomeRoad.esm
GunRunnersArsenal.esm
Fallout3.esm
Anchorage.esm
ThePitt.esm
BrokenSteel.esm
PointLookout.esm
Zeta.esm
CaravanPack.esm
ClassicPack.esm
MercenaryPack.esm
TribalPack.esm
TaleOfTwoWastelands.esm
Project Nevada - Core.esm
TTW Redesigned.esm
Project Nevada - Equipment.esm
Project Nevada - Rebalance.esp
Project Nevada - Cyberware.esp
Project Nevada - Extra Options.esm
SolidProject.esm
HumanTrafficking.esm
JHBCloverPlus.esm
oHUD.esm
wsex.esm
TTW_NoKarmaDCFollowers.esp
TTWOptions.esp
JIP Companions Command & Control.esp
Book of Steel.esp
LodFixer.esp
Slave In Pose NV Edition.esp
Project Nevada - Rebalance Complete.esp
Project Nevada - All DLC.esp
Project Nevada - Cyberware Additions.esp
Project Nevada - TTW.esp
wsexInnuendoNPCs.esp
wsex-DSI.esp
HumanTraffickingEX.esp
MoriartysTestFix.esp
TTWVaultSuitHotfix.esp
bzBodySuits.esp
The Mod Configuration Menu.esp
B42Inertia.esp
07RoadFighterArmorEN.esp
MCPipBoy2000MK6.esp
MCPipBoy2000MK6_clock.esp
07MERGE- Alice underwear+skirt and shirt.esp
07JHBCloverPlusOverride.esp
07MERGE- item tweaks+music edits.esp
07KillableKids.esp
07 No bobble head effects.esp
07Distributed Necklaces and Chains.esp
No VATS Animations.esp
HumanTraffickingSIP.esp
wsexInnuendoAnims.esp
Wsex - Disable Sex XP LvlUp - Add Book.esp
Wsex - Disable STD and Effects.esp
Book of Steel - TTW.esp
ChristieOutfitsforT3.esp
R.A.C.E. Station.esp
MERGED PATCH 1.4.esp
TTW - Realistic Interior Lighting.esp

Total active plugins: 65
Total plugins: 65

Edited September 20, 2019 by VAULTRENEGADE

[dubiousintent]

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.

"NVAC - New Vegas AntiCrash" error log entries are described on the "Description" page. This an important log for "in-game" errors. Some are intended to assist mod authors; while others are there to help "you, the player" trying to resolve a problem. You are interested in the entries which are NOT automatically handled successfully by NVAC. Key entries to look for are the following "letter codes":
* "e" entries are Exceptions handled specifically by NVAC's targeted code changes
* "h" entries are exceptions identified Heuristically by NVAC's "global" exception handler, sometimes handled unsuccessfully.
* "m" entries are "Middle of nowhere" exceptions, sometimes handled unsuccessfully.
* "ñ" entries are Null instruction exceptions, sometimes handled unsuccessfully.
* "n" entries are Null pointer call exceptions, sometimes handled unsuccessfully.
* "o" entries are stack Overflow exceptions, usually handled unsuccessfully.
* "q" entries are program self-termination information; these are effectively crashes.
* "u" entries are Unhandled exceptions reported from the Unhandled Exception Filter; these are crashes (and the NVAC author wants to hear about them).
* "v" entries are unhandled exceptions reported by NVAC's "global" exception handler; these are crashes.
* "w" entries are informative, relaying exception information as it passes through New Vegas's final exception handler.
* "x" entries are critical errors in Windows exception data; these entries should never occur.
* ":" entries are output from OutputDebugString calls.
* ";" entries are output from the game's own error checking.
Other codes may be of interest, but are not things the player is likely to be able to resolve, They are useful for informing the author of the mod to aid them in fixing their plugin. In particular, pass along the
* "_" entries are informative, relaying that NVAC was loaded and the base address of various DLLs
* "!" entries are informative, relaying human-readable text for the user
entries.
Any error codes found in the log but not listed on the mod "Description" page should be reported to the NVAC comments page.

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

Please see 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 notice you are playing TTW. You really have to get a stable FNV game setup before you install TTW. TTW will only make an unstable setup more difficult to diagnose, primarily because you will not be sure if the underlying problem is an incompatible mod that is not listed on their FAQ page.

 

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-

[VAULTRENEGADE]

Things have only gotten worse...

 

I've viewed the error log entries from NVAC/ NVSE and they've appeared largely inconsistent between crashes with few common errors. NVAC LOG- the "script 'Expression Error: SYNTAX' (19000C1F)" pertains to a script from solid project (overhaul mod) though I'm not sure what purpose it serves.

 

I've now experienced a number of windows errors in addition to the CTD's/ inifinite load wheels.

 

windows errors:

 

a). "c++ runtime error the application has requested the runtime to terminate it in an unusual way"

 

b). "the instruction at 0x0000006000000000 referenced memory at 0x00000000000 the memory could not be written"

 

Things I've tried ...

 

a). created an exemption for NVSE from DEP

b). created a new character w/ mods enabled. I experienced an infinite load wheel upon entering the first area (everything worked fine up until then, however).

b). reinstalled enboost in an effort to determine whether or not it would solve my problems; I still experienced a CTD after a loading screen which resulted in error "a).". Multiple trials and I was still met with an infinite loading screen upon fast traveling... This would indicate that whatever is causing my game to crash is not a memory issue..

 

I've literally never experienced Fallout this bad before with so many problems. I'm going to do a clean reinstallation and start from there without mods. Of note, I reinstalled windows a few weeks ago but I haven't experienced any problems other than with FNV since then, so I doubt that's what's causing this.

 

 

UPDATE: After a clean install of FNV, I verrified the vanilla version to be running stable however i ran into issues after installing TTW (I also have NVAC, NVSR, 4GB patch, JIP, and NVSE installed). I encountered an infinitie load screen almost instantly after leaving the vault.

 

i could use some help deciphering the crash logs here...

 

NVAC LOG -infinite load screen

 

NVSE LOG- infinite load screen

 

*********************************

NVAC LOG- CTD

 

NVSE LOG-CTD

Edited September 22, 2019 by VAULTRENEGADE

[dubiousintent]

The NVAC Log is spewing out "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. 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). (There are an on-going series of Windows patches related to how games use memory in order to prevent malware. You have a 10 day window to revert to the "restore point" created when the patch is installed if you decide to go that route. Otherwise you need to try to see if the problem has been raised with M$ and what (if anything) they are going to do about it.)

You may need to exclude FNV from "Data Execution Protection (DEP)" and configure " Windows Defender Exploit Guard (WDEG)". 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.

As you have "New Vegas Stutter Remover" (NVSR) installed, 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.

The NVSE log entries do not look to me as if they are "fatal" (as in "won't cause a CTD"). Rather they appear to be messages intended for the TTW team about things they (I'm guessing) decided not to implement from FO3. Problems specific to TTW need to be raised with that team on their Discord Server or Technical Support forum AFTER checking out their FAQ.

-Dubious-

[VAULTRENEGADE]

As always thanks for the help, Dubious. After much trial and error, it seems NVSR is responsible for the inumerable crashes I've been experiencing. After removing it all trials have resulted in ZERO crashes, while reinstalling it reproduced predictable crashes 100% of the time. From what I've read NVSR has a well-recorded history of incompatibles with windows 10 further complicated alongside TTW. For whatever reason, I was largely unaffected by issues with NVSR before but since reinstalling windows I've downloaded a number of newer updates that likely contraindicated NVSR.

 

It seems the only issue I'm experiencing now is missing sound effects following a load menu. This happens infrequently at random intervals and usually effects weapon draw, weapon fire, and footstep sounds. It only happens after a loading menu. Any thoughts on this?

Edited September 22, 2019 by VAULTRENEGADE

[dubiousintent]

Those "sound effects" (except "weapon fire") seem to be "havok material" related. In any case you might be having some audio "desync" immediately after the "loading screen". Try searching on the keyword "SOUND" in the wiki "Fallout NV Mod Conflict Troubleshooting" article.

 

I've also seen it suggested that having NVSE logging enabled might be causing it. (Writing log files is the slowest thing the game does.) As you are past your CTD issues, might try turning that off to see if it helps.

 

-Dubious-

[VAULTRENEGADE]

Disabled logging; everything seems good to go now. Haven't had any crashes or other issues since removing NVSR either. Thanks Dubious!