Anathena

Hey Sheson, thank you for the help! I updated MO2, the problem persists. Windows Event Log gives the following two Exception codes: 0xc000001d, 0xc0000005 as responsible for crashes at different instances (sometimes the former, sometimes the latter). For code 0xc000001d, it also states the following: Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Taking Your Firstborn because of this error. Program: Taking Your Firstborn File: The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

I am literally at my wit's end. I've never had trouble running DynDOLOD before, whether it is the old version or 3.0. For some reason, it has started to fail completely almost every time with no error message generated. The window for both Texgen.exe or Dyndolod.exe simply closes with no warning, with Mod Organizer still displaying that texconvx64.exe is still running (Task Manger also shows several instances of conhost.exe running). However, Texgen or Dyndolod closes on its own. Sometimes Texgen will be able to get through without crashing, but DynDOLOD almost always crashes. After trying a bunch of things to get it to work, I got Dyndolod to work yesterday once after setting it to run as admin, but I tried to run it again (changing nothing) and it went back to crashing. Things I've tried with no change or success: Adding all associated applications (Texgen, texconv, dyndolod, lodgen) as exceptions to Virus Protection Disabling virus protection entirely Running the apps as admin Both custom and automatic page file Lowering DynDOLOD settings. It happens no matter what settings I use Using DynDOLOD on a completely vanilla mod setup. No mods installed except DynDOLOD and requirements. The same problem persists. Adding TextureCache=10 to Dyndolod_SSE.ini as suggested on the FAQ Tweaking MaxLODGen setting to lower numbers (even 1) Sometimes it generates logs, sometimes it doesn't. It seems to depend on when it decides to crash. However, it almost always crashes around the time that it begins to create LODs, but sometimes it will also just crash when simply reading the load order (spitting out warnings).