DynDOLOD suddenly closes without any pop-up (usually after 3 minutes or so)

[lighthouse-lady]

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!

[sheson]

12 minutes ago, lighthouse-lady said:

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!

The provided debug log only shows the tool being started and then closed.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log, debug log and bgreport.txt to upload when making posts. It also explains what to do in case the tool is being terminated prematurely and can not write the logs.

Reinstalling the game makes no sense.

[lighthouse-lady]

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: 
 

Edited Wednesday at 10:32 PM by lighthouse-lady

[lighthouse-lady]

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

[sheson]

7 hours ago, lighthouse-lady said:

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

There seem to be no realtime log included in any of the uploads.

In any case, the exception c000001d from the Windows Event log hints at unstable hardware, overclocking, BIOS settings, memory timings or OS problems. Make sure the system is stable by running something like prime96/OCCT.

[lighthouse-lady]

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). 

Edited yesterday at 03:36 PM by lighthouse-lady

[sheson]

1 hour ago, lighthouse-lady said:

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). 

No realtime log was provided.

Playing a game is not the same as actual stresstesting with prime95 or OCCT.

I typically suggest to let the OS handle page files / virtual memory. If that is already the case, you can test if setting the same amount as the main memory makes a difference.

Switching hardware should not require reinstalling the OS.

[lighthouse-lady]

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. 

[sheson]

41 minutes ago, lighthouse-lady said:

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. 

No realtime log has been provided, so it is not clear what is being worked on at the moment of the crash or if it happens always at the same time.

c000001d from the event log is all I have to go on at the moment.

This should not really be an issue caused by mods or the compiled program code itself when everything works normally. Typically the error and crash handlers catch all normal issues and write them to the log or at least a bugreport.txt.

[lighthouse-lady]

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?

[sheson]

7 minutes ago, lighthouse-lady said:

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?

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs what to do in case the tool is being terminated prematurely and can not write the logs.

[lighthouse-lady]

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...

[sheson]

14 hours ago, lighthouse-lady said:

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...

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
Add RealTimeLog=1 under [TexGen] or [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\[TexGen|DynDOLOD]_[GAME MODE].INI respectively.

Adding it at the bottom of the INI file for example. By the time the options window shows, the real time log file should be in the log folder already.