In any case I am planning on trying to migrate to MO again, just not quite so soon as I've only just managed to get my Wrye Bash install done. This is highly frustrating, because I'd had 90% of my install already configured in MO-INI tweaks and such. In the absence of anything else, I am wondering if the absence of correct archive invalidation settings might be at fault (see my other thread on the subject in this subforum) ? I'll admit this is reaching, but it was already at the point where Oblivion simply wouldn't start but crashed before the main menu. I'm not sure what's going on here, since LODGen is a 32-bit app. I would also note that when I've run TESLODGen after installing mods in Wrye Bash, all LOD files are generated with no problems and in less than 5 minutes, and RAM usage for LODGen never breaks 500 - 600K. I've found no solution to this problem, since it doesn't seem to be any particular mod I've installed and thus have had to switch back to using Wrye Bash for the time being since installation and behaviour overall seem to work better with Oblivion. I have 8GB of RAM on my laptop, and an i7 CPU and frankly I don't see why this should even be an issue.

If I run LODGen through MO with only the official plugins and a small handful of mods, the LOD files are successfully generated however at some point it starts choking on lack of memory. Nothing was significantly changed in my mod setup between Wrye Bash and MO except the addition of a few house mods, which AFAIK should not have added many (if any) LOD items to be generated. Memory use as reported by Task Manager in Windows 7 shows the memory use balloons up to > 30000000 K, at which point LODGen usually fails. Installing mods for Oblivion through MO, I encountered an issue where TES4LODGen (needed to run Really AEVWD, which is an object LOD mod) consistently runs out of memory when generating LOD files.

Oblivion application load error