TexGen is being terminated prematurely, suddenly closes

[3fast5you]

So I tried to look around and search for someone with a similar issue, but couldn't really find a fix that worked. Apologies if I missed something.

TexGen stops responding and eventually crashes when it reaches the "Creating billboards" part.

No TexGen logs, but Event Viewer has this to say:

Faulting application name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x61d2f1a9
Faulting module name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x61d2f1a9
Exception code: 0xc0000005
Fault offset: 0x0000000000895869
Faulting process ID: 0x3428
Faulting application start time: 0x01d800ea10b45f2b
Faulting application path: C:\Faens C\Modding Utilities\DynDOLOD\TexGenx64.exe
Faulting module path: C:\Faens C\Modding Utilities\DynDOLOD\TexGenx64.exe
Report ID: 835b9ca3-7c4d-4d3c-81cc-f79c3c6f1465
Faulting package full name: 
Faulting package-relative application ID: 

Don't know if it is worth mentioning, but originally I had a different error message in the Event Viewer, but then I ran System File Checker, and now I get the above error.
Here is the one before I ran SFC:
Faulting application name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x61d2f1a9
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1387, time stamp: 0x0b9a844a
Exception code: 0x0eedfade
Fault offset: 0x0000000000034f69
Faulting process ID: 0x592c
Faulting application start time: 0x01d800e553cf8a38
Faulting application path: C:\Faens C\Modding Utilities\DynDOLOD\TexGenx64.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report ID: 07b3f337-478d-4cc7-951e-9de7a42acf16
Faulting package full name: 
Faulting package-relative application ID: 

[sheson]

54 minutes ago, ExquisiteLemon said:

For whatever reason, adding the RealTimeLog=1  on TexGen ini made it run almost twice as long as it usually does, it still crashed at about the 3 minute mark though, leaving no logs.  I have also re ran SSELodGen to see if that was the issue, but I am still having the same crash.

Here are my real time logs;  https://drive.google.com/file/d/1wuwFXqWPvgZIKAUPmQdSOONnC2vN8Uhn/view?usp=sharing

SSELODGen output is irrelevant for TexGen.

Check the Windows Event log for related messages and post it if you find something.

[ExquisiteLemon]

1 hour ago, sheson said:

SSELODGen output is irrelevant for TexGen.

Check the Windows Event log for related messages and post it if you find something.

I do seem to be getting some sort of Nvidia Kernel error when looking at Event Viewer, and from what I could tell when looking it up, it has to do with a CPU GPU imbalance.  I've noticed my CPU gets pretty high when running Tex Gen, but I have an i9 and a 4700 (with my drivers updated) so I don't see how this could be a hardware issue when I've had no issues running TexGen before.

I will attach the two logs here, other than "update your drivers is the fix" I can't seem to make a lot of sense of this since my drivers are updated.

https://drive.google.com/file/d/1OUGUxEBfiYMwqAqf73k6J-dfocj7rdtr/view?usp=sharing

[ExquisiteLemon]

15 minutes ago, ExquisiteLemon said:

I do seem to be getting some sort of Nvidia Kernel error when looking at Event Viewer, and from what I could tell when looking it up, it has to do with a CPU GPU imbalance.  I've noticed my CPU gets pretty high when running Tex Gen, but I have an i9 and a 4700 (with my drivers updated) so I don't see how this could be a hardware issue when I've had no issues running TexGen before.

I will attach the two logs here, other than "update your drivers is the fix" I can't seem to make a lot of sense of this since my drivers are updated.

https://drive.google.com/file/d/1OUGUxEBfiYMwqAqf73k6J-dfocj7rdtr/view?usp=sharing

I re installed all drivers and it magically works now, that was way more of a headache than it should have been oh my gosh.

[ExquisiteLemon]

Is it important to disable SSE Tamriel Terrain Extended.esm BEFORE running TexGen?  Will it cause issues down the road or is it actually fine to leave it enabled for TexGen?

 

Also, just to clarify, should the mod remain enabled with just the ESM disabled or removed when running Dyndolod?

[sheson]

8 minutes ago, ExquisiteLemon said:

Is it important to disable SSE Tamriel Terrain Extended.esm BEFORE running TexGen?  Will it cause issues down the road or is it actually fine to leave it enabled for TexGen?

Also, just to clarify, should the mod remain enabled with just the ESM disabled or removed when running Dyndolod?

https://dyndolod.info/Help/xLODGen
Terrain LOD is generated from the data found in the game plugins. For memory and performance reasons Bethesda removed landscape information from the Skyim.esm which were restored from the vanilla terrain LOD meshes in the xLODGen Resource mods below.
...
Remove or disable the plugin after terrain LOD generation. No harm done if loaded in-game. Typically the player can not get close to these areas. There are no effects outside the far away added cells.

https://dyndolod.info/Help/TexGen
TexGen generates textures from full textures. For rendered textures and LOD billboards it uses full models or special models. TexGen does not care about terrain LOD meshes or textures or grass cache files.

The plugin is irrelevant for TexGen.

The archive/mod only contains the game plugin and nothing else. Disabling/removing the mod or just the plugin all has the same effect.

[Lodder373]

I made it to TexGen setup. I started it. Only for it to shut down on its own a minute later while it was generating.

[sheson]

8 hours ago, Lodder373 said:

It made it to TexGen setup. I started it. Only for it to shut down on its own a minute later while it was generating.

Moved post from the irrelevant thread.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen log and debug to upload when making posts or what to do if the OS terminates the tools prematurely.

[Aquos_666]

always crash after this

[sheson]

15 hours ago, Aquos_666 said:

always crash after this

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen log, debug log and bugreport.txt to upload when making posts.

Do not post screenshots of text. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text

[Aquos_666]

TexGen_SSE_log.txt
https://paste.ee/d/HMH7iOh4

[sheson]

50 minutes ago, Aquos_666 said:

TexGen_SSE_log.txt
https://paste.ee/d/HMH7iOh4

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen debug log and bugreport.txt to also upload when making posts.

[Aquos_666]

bugreport.txt https://paste.ee/d/b5VzAtwo

TexGen_SSE_Debug_log.txt https://ufile.io/ek492xvc

TexGen_SSE_log.txt
https://paste.ee/d/HMH7iOh4

[sheson]

7 hours ago, Aquos_666 said:

bugreport.txt https://paste.ee/d/b5VzAtwo

TexGen_SSE_Debug_log.txt https://ufile.io/ek492xvc

TexGen_SSE_log.txt
https://paste.ee/d/HMH7iOh4

Delete all old logs and bug report.

Get and run the test version of TexGen from this post https://stepmodifications.org/forum/topic/20153-error-opengl-framebuffer-objects-unsupported/#findComment-282545

Upload new log, debug log and bugreport.txt if there still is an issue.

[Aquos_666]

still crash no logs just bugreport.txt https://ufile.io/kgvx5gtr

bugreport.txt

[sheson]

11 minutes ago, Aquos_666 said:

still crash no logs just bugreport.txt https://ufile.io/kgvx5gtr

bugreport.txt 113.84 kB · 1 download

While this is a different bugreport.txt it still reports the date of the TexGen to be from 2024-10-11, which would be form the DynDOLOD 3 Alpha 182 release.

Close all open TexGen processes so it can be replaced. Make sure to download the test version and to replace the TexGenx64.exe in the DynDOLOD folder. It should have then a recent file date, typically from the time you downloaded.

The log and debug log are typically saved when the tool close. No need to change INI settings. Just leave default for now as the error is currently different to that in the other thread.

Delete old bugreport.txt before running again.

If there is still no logs saved next time, enable the real time log as explained https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs