FNW Win10 RS3 patch crash

[Derialund]

Good day to everyone. This is my problem.

 

Until yesterday I have postponed a Win10 RedStone 3 Patch released some weeks ago. Until yesterday, I was able in someway to play with Fallout New Vegas. Until today, that I decided completely unaware of the issue it would followed from installing the windows patch.

 

Now If I launch the main FNV executable, the game start and CTD at the Bethesda logo. Until yesterday this never happened.

 

If I launch NVSE_Loader, sometimes it says that is unable to inject DLL, while until yesterday I have never seen such error.

 

There's no problem with mods or else. Yesterday I have played the game, then turn off the PC and everything was working. Today I have decided not to postpone the OS patch and this evening I tried to play the game, just to find out this odd error.

 

I have added the executable on the exception lists of the main antivirus and in Windows Defender (active in passive mode). I have tried to add some sort of exception even on the new anti-exploit feature introduced on RedStone 3, with no positive result. The Folder protection of Windows Defender, due to the fact that is only active in passive mode, is not enabled.

 

If someone can give me some clues about this...

 

Thank you and Happy New Year.

[dubiousintent]

Are you running Win10? Did you get the "Fall Creator's Update" (FCU aka "RedStone 3")? Do you have "New Vegas Stutter Remover" (NVSR) installed? If all three are "true", then please see the 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play' (and other "heap size") entries in the 'Solutions to Performance problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

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.

If those suggestions are not sufficient, Please see the 'Solutions to Starting the game problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

-Dubious-

[Derialund]

Are you running Win10? Did you get the "Fall Creator's Update" (FCU aka "RedStone 3")? Do you have "New Vegas Stutter Remover" (NVSR) installed? If all three are "true", then please see the 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play' (and other "heap size") entries in the 'Solutions to Performance problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

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.

 

If those suggestions are not sufficient, Please see the 'Solutions to Starting the game problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

-Dubious-

 

Running in Win10 RedStone 3 x64 (the last major update). The game isn't installed with Steam and running the main executable with the "Running as Admin" option, makes FalloutNV pass over the Bethesda logo, just to crash after, due to the presence of NVSE mods. The NVSE loader even if launched as admin, crash just a moment after the logo. I will give a check to the links you quoted here. I'm simply upset for the fact that, since yesterday everything was quite fine and now, after a OS patch, everything is messed up.

[Derialund]

It seems that NVSE have stopped to work properly. I have reinstalled it, but when I launch the nvse_loader it says "can't inject DLL". If I try to launch it again, the game start (for I have removed a mod that was using NVSE probably), but when I load the save file, I get a message saying that NVSE is not loaded. I don't understand how can this happened, for the NVSE folder inside "data" is present, among with its plugin files.

[dubiousintent]

When someone tells me they run the game "as administrator", that immediately tells me they have it installed to the default "C:\Program Files(x86)" folder tree. (You don't need to be "administrator" when it is run from anywhere else.)

 

When they then tell me that everything had been fine until the latest OS update and nothing else has changed, the answer is obvious: Microsoft changed security settings on it's "protected system folders and system" again. Things located there that worked in ways MS doesn't like have been blocked because malware behaves in a similar fashion as well (i.e. "DLL injection").

 

THIS is why we have been telling people for years now that they HAVE to move their games out of that folder path. MS will screw over your game any time it wants without warning. You might work around it for a while, but eventually you WILL get bit. Leaving it in that location is just begging for such a headache. This has been known for years, but Steam took forever to recognize it and change it's default install procedure.

 

If you will look back at my original reply your solution is in the second paragraph. (Mumble, mumble, "horse ... water ... drink".)

 

-Dubious-

[Derialund]

When someone tells me they run the game "as administrator", that immediately tells me they have it installed to the default "C:\Program Files(x86)" folder tree. (You don't need to be "administrator" when it is run from anywhere else.)

 

When they then tell me that everything had been fine until the latest OS update and nothing else has changed, the answer is obvious: Microsoft changed security settings on it's "protected system folders and system" again. Things located there that worked in ways MS doesn't like have been blocked because malware behaves in a similar fashion as well (i.e. "DLL injection").

 

THIS is why we have been telling people for years now that they HAVE to move their games out of that folder path. MS will screw over your game any time it wants without warning. You might work around it for a while, but eventually you WILL get bit. Leaving it in that location is just begging for such a headache. This has been known for years, but Steam took forever to recognize it and change it's default install procedure.

 

If you will look back at my original reply your solution is in the second paragraph. (Mumble, mumble, "horse ... water ... drink".)

 

-Dubious-

But I have installed it on "D:\Fallout New Vegas Ultimate Edition" not on the C:\ original path.

[Derialund]

Yes, I have supposed that the issue was caused by a security measure introduced by the patch. The problem is that both on Windows Defender (active in passive mode) and Malwarebytes Premium (that contains even an anti-exploit feature that could be highly related to this issue), contain in their exception lists the FNV path.

The only thing that I can say is that I don't have configured the new Win10 RS3 EMET integrated functionality, that works similary to the MBAM Anti-Exploit. And the strange thing is that if I launch the NVSE_loader sometimes it stops saying "Could not Inject DLL", sometimes it starts. The issue seems happening randomly.

There's a way to trace or debug NVSE_loader more deeply? For I have checked the logs dumped on the main game folder, but they don't seems to report anything unusual.

[Derialund]

I was reading the Wiki page you reported some posts ago, about the NVSE section. So I dediced to double-check the log files.

Inside nvse_loader I have found this:

 

nvse loader 05010040 01D3842EB82C3C8B
procPath = D:\Fallout New Vegas Ultimate Edition\FalloutNV.exe
launching: FalloutNV.exe (D:\Fallout New Vegas Ultimate Edition\FalloutNV.exe)
dwSignature = FEEF04BD
dwStrucVersion = 00010000
dwFileVersionMS = 00010004
dwFileVersionLS = 0000020D
dwProductVersionMS = 00010004
dwProductVersionLS = 0000020D
dwFileFlagsMask = 00000017
dwFileFlags = 00000000
dwFileOS = 00000004
dwFileType = 00000001
dwFileSubtype = 00000000
dwFileDateMS = 00000000
dwFileDateLS = 00000000
version = 000100040000020D
normal exe
hook call addr = 00ECC46B
load lib addr = 00FDF0B0
dll = D:\Fallout New Vegas Ultimate Edition\nvse_1_4.dll
main thread id = 5684
remote memory = 013B0000
old winmain = 01E1F720
couldn't write memory (update winmain)
couldn't init hook
Couldn't inject DLL.
terminating process

"old winmain = 01E1F720
couldn't write memory (update winmain)
couldn't init hook
Couldn't inject DLL.
terminating process"

What is this?

[dubiousintent]

Well then, (lucky you) you've discovered an entirely new problem; not reported here before. Though it is possible the problem is your "Data Execution Prevention" (DEP) settings. Check those first, please.

 

Suggest you read the "troubleshooting FAQ" at the NVSE site, and once you can say you have done everything suggested, send that report in an email to: "team [at] nvse [dot] silverlock [dot] org". Be sure to recap your first post, and include that your game is installed on the "D:" drive.

 

BTW: your report was the first I've seen calling that the "Redstone 3" patch. When I searched on it, took me straight to the "FCU" patch pages. So I would use both names to avoid unnecessary confusion. (Not everyone is on Win10.)

 

-Dubious-

Edited January 3, 2018 by dubiousintent

[Derialund]

Adding all the three executables on the DEP exception list didn't resolved the problem. I'm going to submit this to the NVSE dev team, reporting the patch ID number:

KB4058043