NVAC Log error Interpretation / Perma-Freeze issue

[Broblin]

So I'm having a recurring freezing issue while playing the game. I've done the S.T.E.P. guide, made numerous ini tweaks to the game for performance and stability as well as NVStutterRemover, EnBoost, etc. My load order is mostly loot but also manually tweaked.

 

 

 

The issue now (even on new saves) is that sometimes I fail to load up a save. Be it infinite loading screen and then entering into an *empty* world space (only hud is visible, literally as if in limbo). If the game manages to load a save (75% of the time), I can do everything in the game as intended but the game is likely to freeze within ~1 hour period. When I installed EnBoost I'm sometimes able to recover past the event and chalk it up to "long stutter" (and overall improved stability immensely), but it often times still perma-freezes whatever I'm doing and I have to forcefully sign out or restart my computer as it won't even allow me to force quit the game.

 

There were instances when it crashed before ("FNV has stopped working) and I've been able to rectify the problem by fixing mods, bashed patch, merged patch, etc. I've even been able to fix "Out of memory" errors through EnBoost and allowing the 4GB Patch to handle Heap scripts (NVSR is apparently outdated and buggy in its handling of heaps, but still does a good deal of other things). It is just this perma-freeze issue that I can't work past, and is the one thing that needs fixing now (I've had a lot of free time recently, I've worked for hours on trying to get this game to not be a buggy mess...).

 

*I think I've managed to find the culprit of this problem but I need help interpreting what it means, if it is the actual issue. I check the NVAC log and more often than not I found that I have seen this error recurring whenever the game fully perma-freezes:

 

07190748 ; DEFAULT: Unknown file type on file 0

07190835 ; script 'Expression Error: SYNTAX' (001633FD).

07190840 ; script 'Expression Error: SYNTAX' (001633FD).

 

Any advice?

 

edit: I'm using Win10 and have the full, but short, log:

 

edit2: Although it has been drastically been reduced in frequency, the error returned in conjunction with a DirectX9 error in a very graphics intensive area (in a mod-added AWOP zone) after several hours of game-time. I believe the initial issue was resolved by disabling DEP, but all that is needed is some texture pack swap-outs to remove the second time it came up. Pretty much solved.

Edited January 10, 2018 by Broblin

[dubiousintent]

I don't see anything obviously wrong with your load order (and didn't expect to if you get an hour of play out of it). At 112 plugins you shouldn't be having anything like "too many plugins", though you are a bit heavy on "overhauls".

 

Unfortunately those NVAC error messages don't really tell us which file or lines have the syntax errors. You might want to check for entries on either side of those lines that mention more details; and also your NVSE log to see if that can help pin down the source. Whenever you get a CTD, be sure to immediately check the Windows EventLog for "system" and "application" errors at the time.

 

Please see the 'Solutions to Performance problems' and 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. Sounds like you covered most of those bases, but perhaps there is something listed you haven't tried.

 

You didn't mention your OS version. The Win10 "Fall Creators Update" (FCU; aka "Redstone 3") and subsequent patches have started breaking some of our older tools, such as NVSR and (recently it appears) NVSE. It's worth noting if you were having the same problems before or after FCU or later patches.

 

-Dubious-

Edited January 8, 2018 by dubiousintent

[Broblin]

I've definitely hit the overhauls pretty hard, but I've seen a Let's Play on Youtube (Gopher) with most of the same mods I'm using; he may have to be incredibly nuanced in their tweaks to get it to work but it does work.

 

I'm using Win10 and have done several recommended tweaks to NVSR (heap disable) and even things like the 4GB patch; but I've just started modding FNV after doing Skyrim and Oblivion so I sadly don't have a comparison to pre-FCU days.

 

Might just be something I'm missing so I'll be sure to check out the NVAC log and solutions guides, thank for those I oddly enough didn't come across the mod conflict troubleshooting link.

 

 

I'm going to edit the post and include the whole NVAC log if it helps, but it's not entirely forthcoming in details lol.

Edited January 8, 2018 by Broblin

[dubiousintent]

The NVAC log, in addition to showing an unknown file type error, is also reporting "Exception code: 0xc0000005". Please see "Cause-3" in the 'Issue: Application load Windows error(s)' entry under the 'Solutions to Starting the game problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

I would check the comments on the NVAC download page to see if there is anything on that "file 0" filetype error.

 

-Dubious-

Edited January 8, 2018 by dubiousintent

[Broblin]

Without trying to speak to soon, I do believe this has been solved. THANK YOU!

 

I added the FNV.exe's that I was using (nvse_loader.exe, NVSE, 4gb patch, etc) to the exceptions in the "Disable Data Execution Prevention" Windows Application as described in the guide under "Issue 6.2, Cause 3, Solutions-3b and 3c". Pretty sure only the nvse_loader.exe had to be added to fix it but I added them all just for the sake of overkill. I've also toned down some of the .ini values that I tweaked at the start of modding that can be performance hogs for a bit of good measure (like grass detail, shadow load distance, etc).

 

It's been almost 2.5 hours of game time before FNV crashed to an unrelated issue; an actual crash that I was able to alt-tab out of, something I'd never thought I'd be happy to see. Even with the crash the 0xc0000005 error has ceased showing up in NVAC logs, and Window's event viewer didn't indicate a memory issue (which I checked and found it was giving for every other time FNV crashed prior to disabling DEP for the executables).

 

Still entirely unsure about the "DEFAULT: Unknown file type on file 0" issue, but searching the mod posts brought up nothing. There are several people with the same issue in their logs but it seems to occur from other crashes (rather than being the cause?).

 

I'll give it some more game time to be sure but I'll add a solved tag if I don't get it for a while longer. Might still crop up in big fire fights/graphics intensive moments but we shall see.

 

Cheers!

 

edit: Although it has been drastically been reduced in frequency, the error returned in conjunction with a DirectX9 error in a very graphics intensive area (in a mod-added AWOP zone) after several hours of game-time. I believe the initial issue is resolved by disabling DEP, but all that is needed is some texture pack swap-outs. Solved for the initial issue.

Edited January 10, 2018 by Broblin