Jump to content

Nonstop crashing on Windows 10


Recommended Posts

THE PROBLEM

I was following a modding guide ( https://www.sinitargaming.com/nv.html ). Everything was working nicely, until I installed an ENB ( https://www.sinitargaming.com/seven_sins.html ). The game simply stopped working - wether I used Steam or nvse_loader, the game crashed right after the initial menu (The one with the Play, Options, Tech Support, etc.) without any error messages. Black screen, then back to the Steam Library. I figured out that using FalloutNVLauncher.exe as an administrator *worked, and it fixed Steam as well, but nvse_loader still didn't work (even when ran as an admin). I uninstalled NVSE and reinstalled it, and it only made everything worse. Now the game will work up until the copyright screen (With the Bethesda logo) and then crash with a "Fallout New Vegas has stopped working" message.

NOTES

Running nvse_loader and FalloutNVLauncher.exe as an administrator and normally didn't work. The game also crashes when I try launching it through NMM or Steam.

LOOT, NMM and FNVEdit say there's nothing wrong with my plugins. The load order seems to be correct, and there are no conflicts.

I have no weather mods, and Seven Sins is the only ENB I have installed. In fact, all of my mods are related to the UI or basic things.

The game was working perfectly with Ultra settings before I installed the ENB, but I'm sure I did it correctly (I followed the guide).

None of the .ini files (Both in \Documents\My Games and in the FNV folder) are read-only.

The resolution is correct. I also turned all settings (Anti-asliasing, HDR, Bloom, etc.) off.

I checked the game's file integrity through Steam and there were no issues with it.

*When I temporarily fixed the problem, the ENB was working as expected.

Playing on windowed mode didn't work.

MODS AND LOAD ORDER

A few were installed manually, but most of my mods were installed by Nexus Mod Manager.

I'd be glad to recieve any advice, even if it doesn't work.

 

 

 

 

 

 

 

 

 

 

 

Link to comment
Share on other sites

When you start the game using the fallout_launcher, a new .ini file is created. So any edits made to the .ini are lost and have to be redone.

 

When using the Steam or Fallout launcher, the .ini files must be set to "Read Only", as stated on the FNV 4GB Patcher at Fallout New Vegas description page.

Link to comment
Share on other sites

You should only use the "Launcher" once. After that you should use the FNV4GB patched "FalloutNV.exe" (which automatically detects and launches NVSE).

 

Please see the 'Vanilla Load Order' entry in the 'First Timer Advice' section; and the 'Common Game Problems' section of the wiki "FNV General Mod Use Advice" article.

If the problem persists, then see either the 'Solutions to Starting the game problems' or the 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict 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.

* 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" or "C:\Program Files(x86)" 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. System updates often cause issues with games installed to these folder trees. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

-Dubious-

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...