Just another thread working on game stability and crashes :)

[fluidityG]

Hello,

 

First I know what it's like to be "that one guy that helps everyone" in a forum so THANK YOU to everyone that devotes their free time to helping us enjoy these games <3

 

I've tried to search around and troubleshoot on my own, but I figured I may as well post here as well. I've noticed the frequency of crashes has gone up recently, so I'm reaching out.

 

Generally I will crash:

 

75%+. Prospecting when nothing else is really going on

20%+. Loading screen into a room or area

~5%. I'm sure some other times I haven't really noticed too much though

 

Some notes:

 

- These are all FREEZES not CTD.

 

- I cannot find a nvac.log file in my NVSE/Plugins folder to try to decipher what's going on. just the NVAC.dll

 

- Also I know that I should try uninstalling things and then toggling them back on slowly to try to pinpoint, but this is my first playthrough... and I only really installed things that would help with RP. Since the nature of the crashes is random (generally every 45-60 mins) I'd rather just put up with the crashes than try to play without the mods too see which one is responsible (if any).

 

Specs:
2500k, 8gb ram, 7970 3gb, Windows 10

 

Other stuff:
Jip NVSE

4gb thingy

No crash mod

(i don't have stutter remover installed as it seemed to not help any)
Small (512) Texture Pack NMC

No real .ini tweaks other than turning off mouse acceleration and the one line for NCO.

 

Mod List:

 

 

GameMode=FalloutNV

FalloutNV.esm=1

DeadMoney.esm=1

HonestHearts.esm=1

OldWorldBlues.esm=1

LonesomeRoad.esm=1

GunRunnersArsenal.esm=1

Project Nevada - Core.esm=1

FCOMaster.esm=1

Interior Lighting Overhaul - Core.esm=1

YUP - Base Game + All DLC.esm=1

FCO - OHSB NPC Edits.esp=1

FCO - NPC Changes.esp=1

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

Interior Lighting Overhaul - Ultimate Edition.esp=1

ILO - PipBoy Light.esp=1

ILO - YUP Patch.esp=1

Agility Affects Movement Speed.esp=1

WMIMNV.esp=1

MOD.Time.Scale_10.esp=1

LessAnnoyingMojaveDialogues.esp=1

CloseMenuHotkey.esp=1

noconsole.esp=1

NoFastTravel_NV.esp=1

No Dialogue Tags.esp=1

Edited October 28, 2019 by fluidityG

[dubiousintent]

The log files for most FNV addons (and NVAC and NVSE in particular) are found in the game root folder (where the EXE resides).

 

A "hang" (for all practical purposes) is not really that different from a CTD, except that the OS has not detected anything blatantly wrong but can't tell what it's next instruction is, unless it is caught in an "infinite loop" of code. There typically won't be any Eventlog entries. Not much you can do about it except minimize the background processes you have running to reduce the possibility of data memory overwrites.

 

The following is a "boilerplate" response to Win10 problems in general. Not all apply to your particular symptoms at the moment.

 

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.

Please see the following entries under the 'Solutions to Performance problems' section in the wiki Fallout NV Mod Conflict Troubleshooting" guide if you haven't already.
* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'
* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed'
* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'
* There are also some NVSR configuration suggestions under the 'Issue: Game in slow motion' and entries. (These will not help with the "Tick Fix" alternative mod, but the author of NVSR now has a suggested configuration for Win10 linked there.)
* The 'Issue: What's with these Solid Green billboard signs in the distance (LOD)?' entry under the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section can also help if your problems started after you installed VWD/LOD texture packages.
* If you are using CASM or some similar "auto-save" mod to manage your save game files (recommended), try increasing the "time between saves" set in the "save frequency"; and reducing the number of occasions it saves to the minimum (e.g. disable most "Autosave Events" in CASM) and see how that impacts the game seeming to freeze temporarily.
* If you have "NVSE logging" enabled (see the 'Checklist Item #4' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide), disable it until actually needed.

Reading from or writing to disk for any reason is the slowest thing the game does.

The size of your image files also has an impact. Larger/higher resolution is not always "better". Please see the wiki "Display resolution versus Image Size" article.

The 'Issue: What INI edits seem to be most beneficial to performance' entry of the wiki "Fallout NV Mod Conflict Troubleshooting" guide) may also be some help. However, the above mitigations are more likely to have a fundamental beneficial effect with or without any INI adjustments, so consider them as the last resort.

 

See also the 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

As you can see, there are a number of things that can underlie your problem. If one of these doesn't fix it, I would be interested to hear about any eventual solution that does.

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-

[fluidityG]

@dubious thanks, were you suggesting I get NVSR? Also, nothing dubious in the load order? (Yay!) Should I try uninstalling all the mods then reinstalling them, and in which order/overwrite? :thinking:

 

here is the nvac log

 

28061241 _ NewVegasAntiCrash FalloutNV.exe

28061241 _ 03950000 07050000 nvac.dll

28061241 _ 0AE90000 05010040 nvse_1_4.dll

28061241 _ 77150000 0A0047BA ntdll.dll

28061317 a 0055945A 00456660 FalloutNV.exe

28061317 h 004A8AEA 668B4008 FalloutNV.exe

28061651 _ 00400000 00000000 FalloutNV.exe

Edited October 29, 2019 by fluidityG

[dubiousintent]

You generally need either NVSR (with the minimal Win10 config) or the lighter alternative "Tick Fix" (linked in the 'Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)' entry) to prevent that issue. You won't see an immediate effect but I suspect this is your primary problem.

 

Please see the 'First Timer Advice', the 'Towards Game Stability', and the 'Common Game Problems' sections (at a minimum) of the wiki "FNV General Mod Use Advice" article.

"NVAC - New Vegas AntiCrash" error log entries are described on the "Description" page. None you listed appear to be anything you can directly affect (that I know of).

 

I don't see anything in your "load order" that re-installing in a different order will make any difference. The primary place where "install order" matters (beyond the obvious) is covered in the wiki "HUD-UI-Menu issues" article and you aren't using any of them (at the moment).

 

FYI: Because of the "MOD.Time.Scale_10.esp" plugin, you should read the 'Issue - Can Timescale adjustments break certain quests' entry of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

-Dubious-

[fluidityG]

You rock.

 

I swear I've tried reading a ton of stuff before posting but you always know where more is @-@()

[dubiousintent]

You are welcome.

 

All I can take credit for is collecting the various solutions others have discovered and pulling them together in one place over the last 5 years. But there is so much that I understand that asking me is quicker than wading through it all. I do try to "triage" it into the most likely solution first to avoid too much information overload. Now it's mostly "copy-and-paste" work for me.

 

-Dubious-

[wfandrews]

Just a side note which made a large difference in my game. My OS is Win10 and I had Tick Fix installed thru NMM and still had problems running FNV. When I installed it manually, just dropped the two files into nvse\plugins, it made an immediate difference in my game.

 

I do not know if it was just my setup that made the difference but it might be something to keep in mind.

[dubiousintent]

@wfandrews: That is an interesting bit of information. I don't use the newer "clean data folder" managers (NMM, MO/MO2, and Vortex) so this is not something I have personal experience with. But based upon my understanding of how those managers work, this doesn't surprise me. By design they basically only load those plugins called for by the "load order".

 

Ancillary plugins that "extend" engine functionality (such as those for NVSE) are typically "libraries" of functions that get loaded by the engine when their functionality is called upon. As such they are expecting to be always available upon demand by any and all profiles. This is contradictory to the basic concept behind the "empty folder" design, though such do usually have a means to accommodate them. (NVSE being a case in point.) My suggestion would be to treat such ancillary plugins the same way you do NVSE: as something that has to always be included, just like the game ESM files.

 

If you can't install a mod using the manager (and again, I don't have experience with this but would assume it applies to any mod that has to be manually installed), then don't expect to be able to so with anything that has to go into the same or a similar "additional" folder for similar reasons.

 

Appreciate the feedback.

 

-Dubious-