Freeze on Startup, MO2

[BinakAlgo]

Hello people, first, thanks for any help you can provide, I'm running desperate and I have no idea of what is going on.

 

First, some background. Around a year ago I tried to install Tale of Two Wastelands, the thing went horribly wrong and suddenly I wasn't able to play New Vegas at all. I uninstalled the whole thing and install it again on another drive. I got tired of all of it and I let it sleep for a while.

 

Now I'm trying to run again New Vegas, now with MO2. I uninstalled again and installed back on the previous drive on the same steam directory. The game unmodded ran fine, then I started to add mods one by one to test how they were and all seemed fine, I also installed the 4 GB patch. I go to sleep and the next day I try to run the modded game and it freezes on startup.

 

I made a new profile and started to add mods, but as soon as I enable any ".esp" file the game freezes. Also, this message appears:

 

 

I have no idea of what that means, but I click yes.

 

If I run from a profile with nothing activated, the game runs, but there is no music in the loading or the main menu and once I open a file the UI is messed up:

 

 

As soon as I activiate any mod with an .esp the game freezes again.

 

Also of note, if after a failed attempt to run I run LOOT, the game doesn't identify any plugins but the base game and DLCs, like it doesn't detect them at all, even clicking "refresh" does nothing.

 

 

I'm running in Win 10, with a Nvidia 970, 32 DDR3 of RAM and Intel i7 - 4970 at 3.60 ghz.

 

I'll gladly give... uh... kudos? to anyone who can help me.

 

 

[dubiousintent]

"Elevation required" means you have to run with "administrator privileges". This is not a good thing to do, period. IT also tells me that you have the game installed to the default "C:\Program Files" folder tree. 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. 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.

 

Please see the 'Vanilla "Load Order"' entry in the 'First Timer Advice' section; and '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 you 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 you failed to get a stable game previously.

-Dubious-

[BinakAlgo]

Thanks a lot, I'm going to read deep those pages. Albeit I don't think the C:\program files is not exactly the problem as I install my games in a separate physical drive. I'll post again if I found the cause if someone has the same problem in the future.

[dubiousintent]

If you did move Steam out of the default location, then likely any access privilege problem is one of "File and Folder permissions" on the parent "root" folder under which you installed the games. If this is not set correctly to allow at least "System", "Administrators", and "Users" to have "Full Control" then you can't overwrite other files or make changes. You then need to enable the "Properties | Security | Advanced | Change Permissions" setting of the parent folder to enable the box: "Replace all child object permissions with inheritable permissions from this object", so those changes get applied to the existing files and sub-folders.

-Dubious-

[BinakAlgo]

No, I did not move Steam from the original location in C:\program etc, etc. I found this very weird, especially because I think all this started when I tried to run the TTW app. That time I uninstalled NV from D: (as it is an SSD and I have most of my Bethesda modded games there) and moved it to another drive, F: (SATA) as the instructions said it shouldn't be run on solid drives. The procedure failed, uninstalled NV from F: (but not FO3).

 

Then, this year, I installed NV on D:, and I just noted that LOOT did not identify automatically, in fact, I remember that LOOT marked the game as TES: Oblivion, I had to direct it manually to the git archives for the master list updates. Then, sometimes it ran and sometimes it didn't. So finally I gave up and installed everything in F:, now everything works, I even installed the New California mod, all runs perfectly

 

So, the solution was to install everything back in F: again. I don' know what to make of all this.

 

Anyway, thanks dubiousintent, I needed to be reminded of the basics all over again. :thumbsup:

Edited November 4, 2018 by BinakAlgo