lighthouse-lady

So I just wanted to follow-up with this issue as I didn't want to rely on a workaround but also I was really curious what cause of it is especially after reading this windows error; "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." I know that windows errors can be rather cryptic when diagnosing application failures and this is especially true when I know myself that this could not be a hardware issue after stress-testing as you've mentioned and no other signs of failure (I forgot to mention that I am using a 12700kf cpu) and modern. So I looked over my windows firewall settings and which applications are allowed to run or not... but I could not find "Taking Your Firstborn" (lol) anywhere in the list so I decided to just add it. Well--it runs perfectly now without the workaround. I realized building LODs for Tamriel was the most resource intense which is probably why it was blocked by my firewall (don't know why the application wasn't listed though... maybe it updates in realtime when it encounters a supposed threat unlike ones it recognizes by default). Just thought this might help anyone who is having the same problem. Thanks again though for your time in helping me solve this!

Makes sense. I seriously doubt I would have managed to pin down the problem without you so thank you so much for helping a newbie like myself! Have a good one!

I see, do you think there is a clear explanation for this anyways? Have you encountered someone that this worked for as well? It just seems kind of strange but of course I'm glad that it works at least!

Ok I'm stupid I was editing the DynDOLOD non-sse config instead of sse one. So after running the tool not only was the log created but the tool ran flawlessly this time. Is there a specific reason why this is so? Here's the log anyways if that helps with that question: https://ufile.io/pltiwpme. I'm not sure if there was something possibly bypassed by enabling this setting and that's what allowed the tool to run without being halted--but if this doesn't sound like a true solution to you maybe I should be doing something else? I've tried things like running the tool in administrator mode (yeah I know stupid) yet that did nothing and this did...

Sorry, I got side-tracked for some time before getting back. So yes, I tried running it with the line pasted into the dyndolod.ini but I still only have the same logs as before. I'm not sure if mentioned load order or not but even though I have personally sorted my entire modlist according to what others have said optimal, I ran the tool with only the essential world building and texture mods and yet it still failed to complete its course. I'm trying not be annoying but I really just have no idea where to venture next. Of course I could skip the mod but I'm really interested in it...

So I added the line RealTimeLog=1 --does it matter where I place it in the ini file? I ran the tool after making this change and I didn't find any logs besides the ones I have already...

Hmm, well it consistently follows the trend of launching LOD generation (e.g Tamriel) and then once that window is closed the entire process just terminates after finding no trace of it in task manager. Is there a way I can enable realtime log even in spite of the program's abrupt termination?

In fairness I did in fact stress test but was doubtful anything would show since this is the single instance I've ever had an error of this sort before and the first time I've encountered an oddity like this. But following your advice, I did now try raising the memory pool and sadly it did not help. I understand if there isn't anything else you could say might work to solve this since I've exhausted through a lot just getting to the option of stress testing so I think I may have an issue with some conflicts between mods which was something I had to resolve before with SSEEdit (and was given the exact details via an error message) prior to it having the opportunity to terminate prematurely like it has now. Either way I really do appreciate your quick responses which I can imagine is probably frustrating since I lack a lot know-how with the "modding stage" aside from the basics. I think you've made a remarkably impressive mod that works wonderfully from what I've seen in user reports & video demonstrations, I just happen to be doing something wrong.

Nothing has stood out to me that would imply hardware error, I can use window event viewer and find no other violation or with the same code as this one. I did stress test though and everything runs smoothly with more than reasonable temps (I can play cyberpunk with 50-60 for gpu & cpu) with no crashing or artifacts of any kind w/o overclocking aside from xmp. I found something saying that memory page for my ssd could be the issue and to solve this I should try increasing the pool? Is it fair to say that this might be to with city/town expansion mods I have installed? I did try once to just generate Tamriel so that stuff like Beyond Reach wouldn't interfere somehow. Maybe looking through SSEedit is the only option left? I'm not sure where to begin looking though since I don't have anything to help diagnose this. EDIT: I did recently have my motherboard RMA'd and since it was the same model and everything I felt no need to reinstall windows but I suppose an OS issue could be causing this. I've thought that a corrupt OS would not only be obvious just with regular desktop usage but also through gaming (like crashing or low performance).

In case the log I provided is not relevant I've zipped the folder that includes all of them: https://ufile.io/z3r6heww

Sorry I meant to upload this log instead: https://ufile.io/5ihl5q8d. Since there is not an error report I found this by looking through the windows event viewer as lied out on the page: https://ufile.io/5s11wwng. Before it terminates a separate window launched for building LOD objects which afterwards never returns to the other window. Edit: For the other windows report, this is everything it says... Fault bucket 2078537651282966566, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DynDOLODx64.exe P2: 3.0.0.182 P3: 67084b88 P4: KERNEL32.DLL P5: 10.0.19041.5072 P6: 81ca7054 P7: c000001d P8: 0000000000020220 P9: P10:

After installing all pre-requisites that support both TexGen and the new DynDOLOD Alpha 3.0 then successfully running TexGen and installing it's respective zipfile added into the folder (which I have placed into my C: drive and not any specific one folder)--I tried running DynDOLOD and through every attempt the window just decides to close without following up with a hint or anything that would help diagnose and locate the cause. I've tried reinstalling it with even the help of video and reinstalling the complimentarily required .NET and C++ and still the issue persists. The one thing I haven't tried that I can think of is just reinstalling the game itself and both TexGen & DynDOLOD but that would suck if it were caused by user error (which I'm definitively sure that it's me) that I overlooked. I asked around on reddit and received help from someone generous and was routed to come here instead. I'll hand over the same link I gave to them: https://workupload.com/file/4jbWsStCqvr. Thanks to whoever can help!