MO 2.0.8.2 - app crash on game exit, or right after game start? also F4SE

[noctred]

I posted this on the github issue tracker but I'm not sure how much traffic that place gets, so figured I'd repost here along with a brief video demonstration (below).

 

--

 

Without fail, every time I quit FO4, Mod Organizer dies. Sometimes, it dies right after FO4 starts rather than waiting for me to exit.

 

Basically, the symptoms are - nearly all flags disappear from the mod pane, the filetree for most (but not all) mods turns empty, and nearly everything vanishes from the plugin pane, as if MO is no longer able to properly interact with the VFS. If I try to interact with MO in any way at this point (for example, if I open up the details pane for a mod), it either crashes outright, or I get some series of errors. For example -

 

failed to write log to /path/to/mo_interface.log: Insufficient system resources exist to complete the requested service.

failed to write /path/to/mod/meta.ini: error 1

An error occurred trying to write back MO settings to /path/to/ModOrganizer.ini.new: File is write protected

 

Sometimes the errors are different (see video), but it always errors out in one way or another.

 

The MO directory is not write protected and I'm definitely not constrained by resources at the hardware level. Once I close and restart MO, all functions seem to work normally until the next time I play and exit FO4. Reproducible 100% of the time. I am on Windows 10 and I am using MO in portable mode. I also tried using instance mode and ran into the same issues. Tried reinstalling MO several times.

 

As a side note, this version of MO is also behaving strangely with F4SE for me. When I launch F4SE through MO, I get a popup stating that some component of F4SE has stopped working - however, I can click cancel on the popup and F4SE seems to initialize properly anyway (I can pull the F4SE version from game console and F4SE-reliant mods seem to work normally). Not really sure what's going on there.

 

--

 

Brief video example - first clip is of MO throwing a bunch of errors and then crashing (errors aren't the same every time; sometimes I see the ones mentioned above). Second is just a straight crash -

 

https://www.youtube.com/watch?v=mtOJlIIizho

 

Thanks.

[noctred]

Similar things happen with other executables also. For instance, MO will throw errors and crash after I've been in xEdit for a while, or after I use Bodyslide... but it doesn't seem to be as consistent.

[GrantSP]

Welcome to STEP @noctred

 

While I commend you on providing this video to help us see what is happening, logs and INIs would be of more use.

The first question I will ask you is: what is the name of the profile you are running? It looks like it contains extended ASCII characters and if so this should be rectified.

Second thing is not all 'write protection' errors are due to Windows and you should check that no other utilities are running in the background whilst MO/Fallout4 is active. Things like game utilities from Steam, AMD/NVidia etc. that may also be trying to write to those folders/files or just interfering with the VFS MO sets up. Related to that 'Insufficient system resources' may also be MO's way of saying something else is stopping it from continuing, other than your total system RAM and/or disk space. Check where those files are being written to and see if other utilities are interfering.

[noctred]

Welcome to STEP @noctred

 

While I commend you on providing this video to help us see what is happening, logs and INIs would be of more use.

The first question I will ask you is: what is the name of the profile you are running? It looks like it contains extended ASCII characters and if so this should be rectified.

Second thing is not all 'write protection' errors are due to Windows and you should check that no other utilities are running in the background whilst MO/Fallout4 is active. Things like game utilities from Steam, AMD/NVidia etc. that may also be trying to write to those folders/files or just interfering with the VFS MO sets up. Related to that 'Insufficient system resources' may also be MO's way of saying something else is stopping it from continuing, other than your total system RAM and/or disk space. Check where those files are being written to and see if other utilities are interfering.

 

I'm using the default profile that is created by the application - it is named 'Default', minus quotes. I haven't created any new profiles and I did not rename the default profile.

 

I don't think I'm running anything that would create file or directory locks. I killed my AV software (including the background helper processes), turned off Steam overlay for FO4, killed GeForce Experience, killed my virtual drive apps... there's nothing else of any consequence running.

 

Here's the ModOrganizer.ini, usvfs.log, and crash dump from my most recent session - 

 

https://www.mediafire.com/?8x2qe9bjdje1u5v

 

Thanks.

Edited February 5, 2017 by noctred

[GSDFan]

@noctred, Both times when you ran ModOrganizer.exe it was like you were running the setup program again. That should not happen after the first install. The MO interface should open up without asking for an instance. I would say you have a bad install. I would run the setup over again, choosing the type of install you want, and point it to another folder. With the new install try running the base game with the script extender. If it works you can copy over your mods, downloads and profile folders to the new install.

[noctred]

@noctred, Both times when you ran ModOrganizer.exe it was like you were running the setup program again. That should not happen after the first install. The MO interface should open up without asking for an instance. I would say you have a bad install. I would run the setup over again, choosing the type of install you want, and point it to another folder. With the new install try running the base game with the script extender. If it works you can copy over your mods, downloads and profile folders to the new install.

 

I figured that was happening because I'm using a portable install and not an instanced install. If I swap to an instance-based install, the particular scenario you're talking about goes away (MO launches straight into its UI), but I still get all the same errors and crashes regardless.