karamille

Yep, changing to the correct MO fixed it, and at least one CTD is gone now. Thanks for kindly pointing out my silly mistake!

Oh. I'll be damned. It is MO2. I never even noticed, assumed that if it was 2, it'd say so! Well then. I'll see about swapping to 1.3 then. @GSDFan, it crashes regardless of whether I've only just opened MO or not, I restarted it a lot due to a separate issue that's only mildly irritating and is something I can live with. But perhaps I won't have the issue using the other version of MO that apparently I should have been using anyway. We shall see.

Sorry if this has been covered elsewhere, but I couldn't find anything that quite matched my situation. I've successfully used MO for Oblivion and SkyrimSE, and I thought it was working alright with FO3 as well, up until I tried to actually launch the game. FOSE runs fine if launched outside of MO, but from MO it immediately pops up with "A component of the Fallout Script Extender has stopped working". I've used LOOT to sort load order before trying to launch anything.