Crashing after 5 to 10 minutes

[JohnnyQuest101]

Where do I find the reason for crashes? Is it in the game folder? What file or folder am I looking for? I'm on windows 10 and there is no message that pops up. It just crashed to desktop. I have roughly twenty mods the biggest being bug patches so I'm not sure why the crash. It was working great yesterday now crashes every 5 minutes. Just looking for the file LOG report location that might tell me why the crash.

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

 

Logs generated by the game itself (not Windows) are found in the game folder, where the "FalloutNV.EXE" file is located.

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

'Expression Error: SYNTAX' is not uncommon, even in vanilla without any mods loaded. These are basically "typos". Such errors are reported by NVAC but ignored. Those lines of script code do not get executed, but also (when caught by NVAC) are not "fatal" to the game. They are the sort of thing mods like "Yukichigai Unofficial Patch - YUP", "JIP LN NVSE", "JohnnyGuitar NVSE", "lStewieAl's Tweaks" etc. are designed to fix or supplement if possible.

* 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)" mod instead. However, until NVTF includes the option, you may want to continue to use NVSR for the "iThreadsFixedToCPUs" setting. However, 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.

 

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

-Dubious-

Edited August 24, 2020 by dubiousintent

[JohnnyQuest101]

The mod list didn't have any conflicts. It might be another windows 10 update issue. I re-installed the game. I reinstalled NVSE, made NVSE ini file with this line "DefaultHeapInitialAllocMB=400" 4GB Patcher, JIPLN NYSE, NVAC. I use a controller so JIP added features is nice with the controller. Honestly it was working okay until level 20.

 

I removed Istewiea tweats, Unofficial patch nvse, YUP, NVTF new vegas tick fix, Mod Configuration menu, perk every level and Weapon mod expanded. This game with windows 10 on steam has issues so I decided to keep it simple.

 

Checked Window Event: From what I found in error it looks like Microsoft was downloading updates and their were errors in version.

 

[JohnnyQuest101]

I checked with windows and ran the game as an admin. It took a while before an actual crash occurred. I played over an hour before it happen. This is what I saw in the event log.

 

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

Faulting module name: jip_nvse.dll, version: 55.55.0.0, time stamp: 0x5f428b1d

Exception code: 0xc0000005

Fault offset: 0x000068e6

Faulting process id: 0x1824

Faulting application start time: 0x01d67a5e8e830529

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

Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas\Data\NVSE\Plugins\jip_nvse.dll

Report Id: 1c4818d0-77d1-453f-b907-74df54614852

Faulting package full name:

Is it having a problem with JIPLN NYSE.

[dubiousintent]

Note that "JIP LN NVSE" has recently required the Visual C++ 2015-19 x86 Redistributable.

 

"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).

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) have causes 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.

-Dubious-

[JohnnyQuest101]

Thanks you so much. That was it exactly. I thought I had Visual C++ and was confused. I needed the 32 bit Visual C++ 2015 x86.

[dubiousintent]

Just for clarification: If you are running a 64-bit version of Windows, then you can (and are recommended to have) both the 64-bit AND the 32-bit versions of libraries installed. They go into different folders (and are the reason you have both 'C:\Program Files' and 'C:\Program Files(x86)' folders). Depending upon which set of libraries a given app is compiled with, it automatically uses the correct version.

 

-Dubious-

[JohnnyQuest101]

Good information. I will do that. Thanks for pointing that out.