Game crashing every 20 minutes

[XavierB34]

Hi, I need help with a bigger problem this time. My game is crashing every 20 minutes without any apparent reason. It started a few months back after a major Windows 10 update and is present ever since. I have tried many things- installing 4gb patch, ENBoost, playing with few mods or even no mods at all, even NVAC, NVSR, NVSE, various compatibility modes, disabling fullscreen optimisations, reinstalling GPU drivers, installing Directx 9 June 2010 (the one recommended in the NV Troubleshooting guide on nexus), reinstalling the game (few times), and NOTHING works. Recently I have noticed that the 4gb patch is not working, because the game doesn't use 3gbs of memory like it used to when I played it on Windows 7, and I am 100% sure that this isn't out of memory issue (no error message when the crash occurs and NVAC crash logs don't show any evidence that system ran out of memory). I am running out of ideas what might be the issue to this :sad:

Edited November 18, 2017 by XavierB34

[dubiousintent]

Most likely this a "heap size" issue. Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

However, your 4GB Patch should be working. If the latest "Creator's Update" somehow broke that, a lot of older games are going to start running out of memory as well. The 4GB limit is due to the game being 32-bit (max addressable memory), and the patch tells the system that the game can use up to 4GB. (See the "2-4GB game memory limits" article in my signature for more details.) This issue is one to pursue. The NTCore tool will let you see if the "LAA Flag" has been set on the FalloutNV.exe file.

 

-Dubious-

[XavierB34]

Most likely this a "heap size" issue. Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

However, your 4GB Patch should be working. If the latest "Creator's Update" somehow broke that, a lot of older games are going to start running out of memory as well. The 4GB limit is due to the game being 32-bit (max addressable memory), and the patch tells the system that the game can use up to 4GB. (See the "2-4GB game memory limits" article in my signature for more details.) This issue is one to pursue. The NTCore tool will let you see if the "LAA Flag" has been set on the FalloutNV.exe file.

 

-Dubious-

 

https://imgur.com/a/j2G0p

 

As you can see, I have Sheson Memory patch (inside NVSE folder) and LAA flag is enabled on my FalloutNV.exe. And the game still use 1,3 GB memory max (screen was taken after 15 minutes of playing).

Edited November 19, 2017 by XavierB34

[dubiousintent]

Just to confirm, you are running a 64-bit version of Win10? Please provide ALL the information requested in the wiki "How to ask for help" article. Look for any Windows "Eventlog" entries around the time of game CTDs under either "System" or "Application" events.

Did you install Steam to it's default location? 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" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. 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. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

In the meantime, suggest you work through the "Checklist" in the "Troubleshooting" guide for anything else that might have changed or will help.

 

-Dubious-

Edited November 19, 2017 by dubiousintent

[XavierB34]

Alright, here we go then:

 

My rig is a MSI notebook; it's running on Windows 10 Home Edition x64, recently updated with Fall Creator Update; the Steam is outside Program Files; it has 8GB RAM, CPU is Intel i5-4200M 2,50 GHz (not overclocked, 2 cores), GPU is GeForce 765M with 2 Gb of memory; when the game crashed there were 3 logs in the Windows event viewer;

 

FalloutNV.exe 1.4.0.525 stopped working with Windows and was closed. To check for more information about this issue, check the problem history in the Security and Maintenance window in Control Panel.
Process identifier: 139c
Start time: 01d36164c632c6ef
End Time: 13
Application Path: D: \ Steam \ SteamApps \ common \ Fallout New Vegas enplczru \ FalloutNV.exe
Report ID: cfe843e5-9475-4d11-bf6d-260479cbe4a1
Full name of the package causing the error:
Application identifier for the error package:

 

The second one is about DCOM user privileges:

 

Application-specific permissions are not granted Local Activation to a COM server application with a CLSID class identifier

{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID identifier
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
BugattiVeyron \ Piotrek user with SID security identifier (S-1-5-21-417395759-699099359-2840874104-1001) from the LocalHost address (using LRPC) running in the application container with SID ID Not available (Not available). You can modify this security by using the Component Services administration tool.

 

My problems with the game started a few months ago, I solved most of the problems that appeared after Win 10 Anniversary update, but now I am unable to solve this problem :sad:

 

Thank you very much for looking into it, if you need any more info please ask away!

 

EDIT: Found another log from today:

 

Name of application causing the error: FalloutNV.exe, version: 1.4.0.525, timestamp: 0x4e0d50ed
Name of the module causing the error: d3d9.dll, version: 10.0.16299.15, timestamp: 0xca6561c3
Exception code: 0xc0000005
Error offset: 0x00070056
Process ID causing error: 0x16cc
Run time of application causing error: 0x01d361125313c2a2
Application path causing error: D: \ Steam \ steamapps \ common \ Fallout New Vegas enplczru \ FalloutNV.exe
Path to the error causing module: C: \ WINDOWS \ SYSTEM32 \ d3d9.dll
Report ID: 6fb690d8-55e6-4938-8c50-c28b98f899d6
Full name of the package causing the error:
Application identifier for the error package:

 

It points to the DirectX files, could it be the issue?

Edited November 19, 2017 by XavierB34

[dubiousintent]

Re: The "stopped working" message. This didn't have anything helpful, except to point to the need to examine the Eventlogs and to tell me that you have the "enplczru" Eastern European version of FNV. The latter is important to know, as there are sometimes issues specific to that version when running in a language other than English (INT). (That does not appear to be the issue in this instance. Just pointing out it is useful info to provide in future.)

 

Re: the DCOM user privileges. Please see the TechNet article "Event ID 10016 - The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID". Suggest you read the entire thing to get a grasp on the potential difficulties, and then try first proposed solution.

 

Re: the third (last) report. Now this has "Exception code: 0xc0000005". This is a fairly common error. That is the Win10 system "fixed" d3d9.dll; not one from the game folder itself (typically ENB). Might be related to the second report (I don't know for certain). Unfortunately there do not seem to be any reports specific to the "Fall Creator's Update" so far. Please see "Cause-3" in the 'Issue: Application load Windows error(s)' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide for more general solutions. If none of those work, then you will need to raise the issue on an MS support forum.

 

One thing that was reported earlier was that some "background" applications can interfere with that DLL, so try shutting down everything you can (including anti-virus by running Steam in "offline mode") and see if that helps.

-Dubious-

Edited November 20, 2017 by dubiousintent

[JimboUK]

This is useful for that error http://www.errorlive.com/exception-code-0xc0000005 as said it's not uncommon.

[XavierB34]

After rolling back GPU driver, recent Windows 10 update, HDD defrag and removing New Vegas Stutter Remover (this time for good) my game is not hanging as it used to. I will keep an eye on my game for now, but it's doing good so far, my thanks to both of you for your help :)

As a note for everyone else that has similar problems and is using NVSR on Windows 10- get rid of it, as it was reported as a main culprit behind 20-30 minutes crashes that appeared out of nowhere. Looks like it's incompatible with recent Windows 10 updates.

[dubiousintent]

Re: NVSR and recent Win10 "Fall Creator Updates" (FCU). That's interesting to hear. Do you have any links to those reports? Would like to confirm such findings from more than one source.

 

Edit: Nevermind. Finally found the reports in recent comments from 13 Nov 2017 onwards on the download page. (Weird threading on the new site design.) The key seems to be disabling bHookCriticalSections (=0), which will also disable the heap related algorithm and size settings in NVSR. The "bfastexit" fix still reportedly works.

 

The downside is that large sized texture replacers are still likely to cause stutter due to the internal game art asset bottleneck loading new cells. About the only thing left to help with that is the NVSE "Sheson memory patch"; and ENBoost, which is in between the speed of VRAM and an HDD ... so not ideal. Use smaller size texture replacements (e.g. not over 2048x2048).

 

-Dubious-

Edited December 3, 2017 by dubiousintent

[XavierB34]

It's also confirmed by RoyBatterian on NVAC posts (from 25th November) and from what I know this guy knows this stuff rather good :wink: and yeah, game crunches a lot when my character is outdoors now, but is (more or less) playable, so the tradeoff isn't so bad :tongue:

bFastExit works fine, but the bManageFPS caused a lot of stutter to my game, I just disabled it and turned on in-game VSync (by setting iPresentInterval=1 in the game .ini files) and it's good now.

ENBoost 0.278 doesn't work for me, I get a blackscreen and main menu music on startup. 0.203 causes a lot of stutters to my game so I abandoned it as well.

Edited December 3, 2017 by XavierB34