0x800705aa exceptions about modorganizer HOT 8 CLOSED

I also just got this issue, but with Fallout 4. Tried to load a different cell and it fell over.

Followed by the following error messages:

I have 16GB of RAM, so whatever system resources the application thinks are insufficient should be more than sufficient. mo_interface log also attached:
mo_interface.txt

from modorganizer.

Seems to be happening still with version 2.0.8.3. Got it three times in a row now regardless if I start up the game itself or another tool like FO4Edit, etc.

I have lots of mods (300+) with zillions of files. Might this be the problem? Does not happen with 2.0.8.0 though.
usvfs.zip
MO_logs.zip

attaching log files...

Hope that helps.

from modorganizer.

How big is your mods list?
How long till you see the crash?
If it happens again please upload the logs (should be in your profile folder under logs)

from modorganizer.

I got similar symptom. In addition to that, if I close MO2 I get some error messages that it was unable to write to its ini file ( C:/Users/Username/AppData/ModOrganizer/modorganizer.ini ) and update its settings although the path seems fine and the file exists. As I am running MO as admin, it shouldnt be a rights issue but might be related to your error description.

Disk space and RAM should not be an issue here as well (>200 GB disk free space, 64 GB RAM, Win 10)

This never happened with MO 2.0.8.0b.

from modorganizer.

I have also seen this problem. similarly I am also running MO2 as admin and just in case installed Steam outside Program Files directory

from modorganizer.

I see this error in 2.0.8.2:

Canceling produces this error:

Steps to Reproduce

1. Launch MO.
2. Launch TESV through SKSE, or perhaps any game.
3. #50 occurs, so MO might be in a bad state at this point.
4. Exit game to desktop.
5. Close error dialog from Step 3.
6. Close MO.

from modorganizer.

Not the issue, I had way less then that, and still got these errors.. (Somewhere between 10-13, I Recently Installed MO.) I'll try to get logs of it next time it happens as well. I deleted the files for installing on a different SSD.

from modorganizer.

Long-standing memory crashes. Fixed on latest builds.

from modorganizer.