Had a stable mod configuration that happened to randomly freeze, now the whole game's broken

[Draghy]

I had tons of mods and installed them all correctly and patched everything, I've been playing this configuration for mod's and it did have ocasional freezes or crashes.

 

This morning I started up NV and loaded my savegame but it freezed on the loading screen, that happened before and since I can't actually close the game because of how the game was made by bethseda and windows wasn't responding at all, I restarted my laptop manually.

 

When I started the game again I had a bunch of error messages from every mod, also other mods initializing like when you start a new game, except I was at the title screen, and all kind of messed up UI, this never happened before.

 

http://thumbs2.imagebam.com/57/08/4b/42de1d1122740404.jpg

 

The console seems to work right and the game is responding, it's just doing all these messed up things.

 

 

http://thumbs2.imagebam.com/9d/68/fb/21a9eb1122740444.jpg

 

Is there any hope to save my game or do I have to manually reinstalled the game and all the 100 mods i have?..

 

[dubiousintent]

In general, if you haven't changed anything about your game and it suddenly stops working correctly you need to look to other causes: such as software updates to Windows, programming libraries such as ".Net", or hardware drivers. Older games eventually get dropped from product testing.

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. You can retain your mod load order and save games doing this by following these instructions and creating a backup copy of the game folder first.

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 mod FNV or it's been more than a year since you last did so.

-Dubious-

[Draghy]

In general, if you haven't changed anything about your game and it suddenly stops working correctly you need to look to other causes: such as software updates to Windows, programming libraries such as ".Net", or hardware drivers. Older games eventually get dropped from product testing.

 

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. You can retain your mod load order and save games doing this by following these instructions and creating a backup copy of the game folder first.

 

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 mod FNV or it's been more than a year since you last did so.

 

-Dubious-

 

I didn't have the game installed in Programs Files. I used the old Nexus Mod manager to manage and install my mods. I was wondering if either the game or the mods themselves got corrupted when I turned off the computer with the game frozen. Is that a posibility? Like I said it was working just fine up until this incident.

[Draghy]

In general, if you haven't changed anything about your game and it suddenly stops working correctly you need to look to other causes: such as software updates to Windows, programming libraries such as ".Net", or hardware drivers. Older games eventually get dropped from product testing.

 

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. You can retain your mod load order and save games doing this by following these instructions and creating a backup copy of the game folder first.

 

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 mod FNV or it's been more than a year since you last did so.

 

-Dubious-

 

Ok so after looking through the guides you sent, I found one mentioning UI problems since I thought my problem was UI related, so i went in the data folder and deleted start_menu.xml and reinstalled Vanilla UI Plus that fixed the game, but my old saves now have infinite loading screens so I'll guess I'll start a new game damn.

 

Thank you anyways!

[dubiousintent]

It is always possible you are having a disk drive problem. Never hurts to run "chkdsk" to "fix errors", ESPECIALLY after you are unable to safely shutdown properly. Files may be "locked", "open", or have "writes" pending by a program. Anytime you have to force a reboot you should first run a "chkdsk" of the "system drive" ("C:") and any other drives you suspect may have been affected the next time you boot up. Play it safe and scan them all.

 

When you say "the old Nexus Mod Manager", did you update it for the following:

 

As of 08 May 2018, the Nexus has changed some site security to come into compliance with the new "European Union General Data Protection Regulation" (EU GDPR) rules. This breaks older versions of NMM and other tools using the older unsecured API. It is usually reported as being "blocked by the Windows firewall" or causing a "script" or "W3C XML Schema" error installing mods. You will need to update it from NMM on GitHub (or this Nexus NMM download page but it's older than the GitHub version). Check the version numbers between those sites and use the latest release. Please see this Nexus site news article for details.

Some people are finding that even after updating NMM to v0.65.4 they still get a "script exception" message when installing some mods (such as UIO and MCM). This seems to be resolved by this suggestion from user ElysianMod:
* Run NMM as an "Administrator privileges" account.
* Go to NMM "Settings".
* Enable "Add Shell Extensions for Supported File Types".
* Then restart NMM. (You should not need "Administrator privileges" this time.)
(Supposedly this fix is included in "unofficial" update v0.65.7 and later to NMM on GitHub.)

Otherwise, as I mentioned in the initial reply: look outside of the game for the cause.

 

-Dubious-