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: 

[MrTanku]

43 minutes ago, sheson said:

I assume you mean TexGen instead of LODGen

If you could just let me know if there is any difference with the test version. Most likely not.

You have an AMD graphics card right? No idea if it matters, just taking notes.

Oh, and if could check if the event log entry is always the same or not. Especially the exception address /fault offset.

....crap lol  anyway I do use a AMD GPU (6900xt) I did rerun with the test version since I downloaded some of the seasons of skyrim additional mods and so far I'm getting these times (29 min 47 sec non-test version and 31min 21 sec on the test version) 

[sheson]

26 minutes ago, MrTanku said:

....crap lol  anyway I do use a AMD GPU (6900xt) I did rerun with the test version since I downloaded some of the seasons of skyrim additional mods and so far I'm getting these times (29 min 47 sec non-test version and 31min 21 sec on the test version) 

That's for generating LOD with DynDOLOD right? That's close enough to be the same.

OK, one last thing: can you run this test version of TexGen with the RenderThreads=2 and RenderContexts=2 setting and see if works or if it creates a bugreport.txt in case it terminates? In case it creates a bugreport.txt upload it please.

[MrTanku]

9 minutes ago, sheson said:

That's for generating LOD with DynDOLOD right? That's close enough to be the same.

OK, one last thing: can you run this test version of TexGen with the RenderThreads=2 and RenderContexts=2 setting and see if works or if it creates a bugreport.txt in case it terminates? In case it creates a bugreport.txt upload it please.

TexGen_SSE_log.txtTexGen_SSE_Debug_log.txtTexGen_SSE_realtime_log.txt ctd without error messages again...really strange behavior when threads =/1. It did not create a bugreport 

 

[Zaire82]

I'm having trouble with TexGen and DynDOLOD. I run the programs but it just abruptly exits them part-way through. In TexGen it was in the creating LOD textures stage. No logs are generated, no messages of any kind.  Curiously, MO2 will crash if I run TexGen a second time after this happens. MO2's logs say it crashes immediately after rerunning TexGen.

After some testing, I realised it doesn't like SSE Engine Fixes. Does that sound right? I disabled that and got through the TexGen stage fine.

Then I started the DynDOLOD stage. I can select the options in the menu and start, but after a couple of seconds, the message window starts flooding with errors like "[thing] does not fit naming conventions [blah blah]", "property not found", and "file not found". Then shuts down the same way TexGen was, except there are some logs. The attached are the only ones created from that run.

DynDOLOD_SSE_Dynamic_LOD.txt DynDOLOD_SSE_Object_LOD.txt

[sheson]

1 hour ago, Zaire82 said:

I'm having trouble with TexGen and DynDOLOD. I run the programs but it just abruptly exits them part-way through. In TexGen it was in the creating LOD textures stage. No logs are generated, no messages of any kind.  Curiously, MO2 will crash if I run TexGen a second time after this happens. MO2's logs say it crashes immediately after rerunning TexGen.

After some testing, I realised it doesn't like SSE Engine Fixes. Does that sound right? I disabled that and got through the TexGen stage fine.

Then I started the DynDOLOD stage. I can select the options in the menu and start, but after a couple of seconds, the message window starts flooding with errors like "[thing] does not fit naming conventions [blah blah]", "property not found", and "file not found". Then shuts down the same way TexGen was, except there are some logs. The attached are the only ones created from that run.

DynDOLOD_SSE_Dynamic_LOD.txt 28.18 kB · 0 downloads DynDOLOD_SSE_Object_LOD.txt 423.13 kB · 0 downloads

Sounds like one of the usual problems: wrong/bad installation or output folder of the game, MO2 or tools. OS/Antivir interfering.

Add RealTimeLog=1 under [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini, then check/upload that log.

"Blah blah" is not a useful problem description. See https://dyndolod.info/Messages to learn what certain log messages mean.

[Zaire82]

2 hours ago, sheson said:

"Blah blah" is not a useful problem description. 

Yea, sorry. I wrote what I could remember from before it shut itself down. Unfortunately the fine details didn't make it.

[Zaire82]

I added the line to the .ini file and updated MO2 since it was a bit outdated. This time I ran it, it just went and finished the process. Still half a million warnings, but it works.

 

[z929669]

Just want to report an ongoing issue with all of the alpha versions since like alpha 33. I haven't reported these for a while, since we got nowhere with a similar but worse issue about a year ago (it was mysteriously resolved for me with a subsequent alpha update).

I will try again. This happens at the very end of running either TexGen or DynDOLOD about 25% of the time for me. The processing completes and the exit/view log dialog appears in a partially-rendered state before the program quits disgracefully ... NO logs or bug report is ever created, since there is no hand-off to the process that creates the logs ... or in the case of DynDOLOD: saves the plugins.

With TexGen, this is not an issue, since I run against the same mod list pretty much constantly in testing, and I know my output bit sizes, which are always consistent, given the nearly identical LO each run. I just use the TexGen output in such cases and move on to DynDOLOD without issue.

With DynDOLOD, it's quite frustrating, as it's a waste of 15-50 minutes of processing, depending. Reason being because the program disgracefully halts without generating the plugins (I could probably reuse those from other runs, but I don't ... they are usually the same exact bits).

Anyway, the only clue is in the Win event log, and it's always the same for either program:

Faulting application name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x63207073
Faulting module name: KERNELBASE.dll, version: 10.0.22000.918, time stamp: 0xb42fa627
Exception code: 0xc000041d
Fault offset: 0x000000000004474c
Faulting process id: 0x2604c
Faulting application start time: 0x01d8c7dd47b3dae2
Faulting application path: C:\Modding\Tools\DynDOLOD\TexGenx64.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Info on the error: https://github.com/dynamorio/drmemory/issues/1355

[sheson]

4 hours ago, z929669 said:

Just want to report an ongoing issue with all of the alpha versions since like alpha 33. I haven't reported these for a while, since we got nowhere with a similar but worse issue about a year ago (it was mysteriously resolved for me with a subsequent alpha update).

I will try again. This happens at the very end of running either TexGen or DynDOLOD about 25% of the time for me. The processing completes and the exit/view log dialog appears in a partially-rendered state before the program quits disgracefully ... NO logs or bug report is ever created, since there is no hand-off to the process that creates the logs ... or in the case of DynDOLOD: saves the plugins.

With TexGen, this is not an issue, since I run against the same mod list pretty much constantly in testing, and I know my output bit sizes, which are always consistent, given the nearly identical LO each run. I just use the TexGen output in such cases and move on to DynDOLOD without issue.

With DynDOLOD, it's quite frustrating, as it's a waste of 15-50 minutes of processing, depending. Reason being because the program disgracefully halts without generating the plugins (I could probably reuse those from other runs, but I don't ... they are usually the same exact bits).

Anyway, the only clue is in the Win event log, and it's always the same for either program:

Faulting application name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x63207073
Faulting module name: KERNELBASE.dll, version: 10.0.22000.918, time stamp: 0xb42fa627
Exception code: 0xc000041d
Fault offset: 0x000000000004474c
Faulting process id: 0x2604c
Faulting application start time: 0x01d8c7dd47b3dae2
Faulting application path: C:\Modding\Tools\DynDOLOD\TexGenx64.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Add realtimelog=1 to TexGen_SSE.INI/DynDOLOD_SSE.ini and upload that log if it happens again.

See if it happens when using the default "Windows" theme.

[z929669]

7 hours ago, sheson said:

Add realtimelog=1 to TexGen_SSE.INI/DynDOLOD_SSE.ini and upload that log if it happens again.

See if it happens when using the default "Windows" theme.

TexGen ran fine this time. DynDOLODx64.exe had the 0xc000041d error though. Running non default Windows theme under Win 11 this time.

logs (no bug report produced)

Admin Event

Log Name:      Application
Source:        Application Error
Date:          9/14/2022 8:41:38 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DHVP
Description:
Faulting application name: DynDOLODx64.exe, version: 3.0.0.0, time stamp: 0x63207073
Faulting module name: KERNELBASE.dll, version: 10.0.22000.918, time stamp: 0xb42fa627
Exception code: 0xc000041d
Fault offset: 0x000000000004474c
Faulting process id: 0x5038
Faulting application start time: 0x01d8c83a4d7ca852
Faulting application path: C:\Modding\Tools\DynDOLOD\DynDOLODx64.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 1e08a2da-ad58-4b3b-8ea1-ec7b15462800
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2022-09-14T13:41:38.6155810Z" />
    <EventRecordID>1538</EventRecordID>
    <Correlation />
    <Execution ProcessID="49696" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DHVP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DynDOLODx64.exe</Data>
    <Data>3.0.0.0</Data>
    <Data>63207073</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.22000.918</Data>
    <Data>b42fa627</Data>
    <Data>c000041d</Data>
    <Data>000000000004474c</Data>
    <Data>5038</Data>
    <Data>01d8c83a4d7ca852</Data>
    <Data>C:\Modding\Tools\DynDOLOD\DynDOLODx64.exe</Data>
    <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
    <Data>1e08a2da-ad58-4b3b-8ea1-ec7b15462800</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

[sheson]

2 hours ago, z929669 said:

TexGen ran fine this time. DynDOLODx64.exe had the 0xc000041d error though. Running non default Windows theme under Win 11 this time.

logs (no bug report produced)

  Reveal hidden contents

Log Name:      Application
Source:        Application Error
Date:          9/14/2022 8:41:38 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DHVP
Description:
Faulting application name: DynDOLODx64.exe, version: 3.0.0.0, time stamp: 0x63207073
Faulting module name: KERNELBASE.dll, version: 10.0.22000.918, time stamp: 0xb42fa627
Exception code: 0xc000041d
Fault offset: 0x000000000004474c
Faulting process id: 0x5038
Faulting application start time: 0x01d8c83a4d7ca852
Faulting application path: C:\Modding\Tools\DynDOLOD\DynDOLODx64.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 1e08a2da-ad58-4b3b-8ea1-ec7b15462800
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2022-09-14T13:41:38.6155810Z" />
    <EventRecordID>1538</EventRecordID>
    <Correlation />
    <Execution ProcessID="49696" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DHVP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DynDOLODx64.exe</Data>
    <Data>3.0.0.0</Data>
    <Data>63207073</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.22000.918</Data>
    <Data>b42fa627</Data>
    <Data>c000041d</Data>
    <Data>000000000004474c</Data>
    <Data>5038</Data>
    <Data>01d8c83a4d7ca852</Data>
    <Data>C:\Modding\Tools\DynDOLOD\DynDOLODx64.exe</Data>
    <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
    <Data>1e08a2da-ad58-4b3b-8ea1-ec7b15462800</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

Are you clicking/doing anything after it prompts to save/exit?

Switch to default theme to see if it makes a difference.

Upload a debug log from TexGen or DynDOLOD from a successful run.

[z929669]

5 hours ago, sheson said:

Are you clicking/doing anything after it prompts to save/exit?

Switch to default theme to see if it makes a difference.

Upload a debug log from TexGen or DynDOLOD from a successful run.

When the run completes, I am usually at the keyboard waiting for it. I try not to maximize the LODGen CMD windows or have other windows open. The save/exit dialog appears over the xEdit processing window. 50-75% of the time, I simply click Check Log or Save/Exit without issue, but the rest of the time, the dialog is not fully rendered, which indicates to me that the process governing that is about to close disgracefully (and does).

I will test default windows theme to see if it helps.

I just completed successful runs of TexGen and DynDOLOD 97, so here's those logs.

[Rakz]

Hello,

I am new here and I'd like to start by thanking you for developing this tool.

I have started using it recently, but I am having a problem with TexGenx64. It closes mid process.

Unfortunately, it closes without generating any of the log files requested in the OP (bugreport.txt or any file in the Logs folder).

I have been having this problem with versions 114, 115 and 116. The interesting thing (maybe) is that I still have version 106 in my computer and it does seem to work with this version: it completes and generates an output.

Is there any useful information you would need to further investigate this issue?

Thanks and good work!

PS: I am pretty sure that I have installed all prerequisites. I have run SSEEdit and also generated the terrain LOD.

[sheson]

8 hours ago, Rakz said:

Hello,

I am new here and I'd like to start by thanking you for developing this tool.

I have started using it recently, but I am having a problem with TexGenx64. It closes mid process.

Unfortunately, it closes without generating any of the log files requested in the OP (bugreport.txt or any file in the Logs folder).

I have been having this problem with versions 114, 115 and 116. The interesting thing (maybe) is that I still have version 106 in my computer and it does seem to work with this version: it completes and generates an output.

Is there any useful information you would need to further investigate this issue?

Thanks and good work!

PS: I am pretty sure that I have installed all prerequisites. I have run SSEEdit and also generated the terrain LOD.

Check the Windows Event log for related entries.

Add RealTimeLog=1 under [TexGen] to ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI run again and upload that log.

[Rakz]

On 2/24/2023 at 2:54 AM, sheson said:

Check the Windows Event log for related entries.

Add RealTimeLog=1 under [TexGen] to ..\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI run again and upload that log.

Hi,

I tried what you asked:

• No logs in Event Viewer related to TexGen
• Managed to get a successful run with version 118
• Then, TexGen started closing again without apparent reason (real time logs attached).

Thanks!

TexGen_SSE_realtime_log-BaseSize256-HDTreeDisabled.txt