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]

10 minutes ago, Wulfga said:

I guess I did a bad job explaining that part. That window with the scolling text... if that's your debug log, it doesn't save at all when it just errors out and ends abruptly. I only get it to close normally and create the logs I've attached one out of every... maybe 9 attempts. I'm in the hundreds probably. 

I have removed overclocking from the CPU, yesterday I think. My graphics card memory is overclocked a little but extremely stable. Attached CPU-Z, because running out of ideas.

Attached the only additional log file that survived long enough in that temp folder to grab it. 

Error log from Event Viewer:
Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33
Faulting module name: nvoglv64.dll, version: 31.0.15.3598, time stamp: 0x646dfba9
Exception code: 0xc0000005
Fault offset: 0x0000000001550f2a
Faulting process id: 0x0x5484
Faulting application start time: 0x0x1D995612705F484
Faulting application path: H:\Modding\Tools\DynDOLOD\TexGenx64.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3c2bd4a1ec6d228e\nvoglv64.dll
Report Id: fabd6cbe-c4a7-44ed-9ac3-f7166bb8d365
Faulting package full name: 
Faulting package-relative application ID: 

Info log from event:

Fault bucket 1897463078308581007, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: TexGenx64.exe
P2: 3.0.0.128
P3: 646a6e33
P4: nvoglv64.dll
P5: 31.0.15.3598
P6: 646dfba9
P7: c0000005
P8: 0000000001550f2a
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.190bcaf4-91c6-4d6b-aaa4-a1c764e90a88.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.143f5221-3e03-4c96-b9e7-e10fa80b639e.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e5c8fd98-60a4-4bee-9a87-9c3566ef8a34.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.165cd335-cfd1-4050-92c5-b7d3037f165d.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.43564062-c08f-4f02-b8e7-7a71c81d2a0d.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_TexGenx64.exe_6f6a94369d9c1185cd99bbdf7a6bac316c9e971e_5b7d448d_8f98ccab-d9b2-4a22-81d8-9332586eff8a

Analysis symbol: 
Rechecking for solution: 0
Report Id: fabd6cbe-c4a7-44ed-9ac3-f7166bb8d365
Report Status: 268435456
Hashed bucket: 1dd0260b7426beeeea55249dd5008e8f
Cab Guid: 0

WER.297e2947-b1c3-4f61-b940-af707c587f6e.tmp.WERInternalMetadata.xml 6.53 kB · 1 download GHOST-CPUZ.txt 248.21 kB · 1 download

The log and debug log are both saved when the program is closed. Just send the signal to close once (e.g. clicking the X top right) and then wait a few seconds so the program can save the logs and shutdown properly.

As explained in the already linked page https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs, use the RealTimeLog=1 INI setting in case there are no logs or debug logs because the tool is being terminated prematurely.

If the screen goes black, then there is probably a hardware (including power supply), driver, overclocking, BIO setting, OS issue.

[Wulfga]

On 6/2/2023 at 12:03 PM, sheson said:

The log and debug log are both saved when the program is closed. Just send the signal to close once (e.g. clicking the X top right) and then wait a few seconds so the program can save the logs and shutdown properly.

As explained in the already linked page https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs, use the RealTimeLog=1 INI setting in case there are no logs or debug logs because the tool is being terminated prematurely.

If the screen goes black, then there is probably a hardware (including power supply), driver, overclocking, BIO setting, OS issue.

Thank you for squaring me away enough to get a bug report in. Was finally able to get far enough for one to generate on one of my attempts. In 40 or so runs this is the first time I've been able to generate a debug log. I PM'd you the bug report because honestly, it's got a decent amount of personal info in it, but I'd really like to not give up on this after all the time spent.

To anyone else who might know anything about this error, I absolutely can't get past this strange DLL error:

Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33
Faulting module name: nvoglv64.dll, version: 31.0.15.3598, time stamp: 0x646dfba9
Exception code: 0xc0000005
Fault offset: 0x0000000001550f2a
Faulting process id: 0x0xD40
Faulting application start time: 0x0x1D997D3012B155A
Faulting application path: H:\Modding\Tools\DynDOLOD\TexGenx64.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3c2bd4a1ec6d228e\nvoglv64.dll
Report Id: 31970090-ec36-4d74-b85b-fcaf1cfc50f9
Faulting package full name: 
Faulting package-relative application ID: 

I really don't want to give up on this, but no one has both the knowledge and the patience to get me past it.

Intel i9 13900k, RTX3070ti, completely fresh drivers, Alpha-128 Dyn from Nexus and the Alpha-36 Resources that the website links to. I'm sure this is somehow my fault but I've exhausted my ability to try more things. Ran SFC and DISM, both fine, I'm just at a loss.

Added the Realtime log (had to zip it, it's huge)

TexGen_SSE_realtime_log.7z

[sheson]

12 minutes ago, Wulfga said:

Thank you for squaring me away enough to get a bug report in. Was finally able to get far enough for one to generate on one of my attempts. In 40 or so runs this is the first time I've been able to generate a debug log. I PM'd you the bug report because honestly, it's got a decent amount of personal info in it, but I'd really like to not give up on this after all the time spent.

To anyone else who might know anything about this error, I absolutely can't get past this strange DLL error:

Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33
Faulting module name: nvoglv64.dll, version: 31.0.15.3598, time stamp: 0x646dfba9
Exception code: 0xc0000005
Fault offset: 0x0000000001550f2a
Faulting process id: 0x0xD40
Faulting application start time: 0x0x1D997D3012B155A
Faulting application path: H:\Modding\Tools\DynDOLOD\TexGenx64.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3c2bd4a1ec6d228e\nvoglv64.dll
Report Id: 31970090-ec36-4d74-b85b-fcaf1cfc50f9
Faulting package full name: 
Faulting package-relative application ID: 

I really don't want to give up on this, but no one has both the knowledge and the patience to get me past it.

Intel i9 13900k, RTX3070ti, completely fresh drivers, Alpha-128 Dyn from Nexus and the Alpha-36 Resources that the website links to. I'm sure this is somehow my fault but I've exhausted my ability to try more things. Ran SFC and DISM, both fine, I'm just at a loss.

Added the Realtime log (had to zip it, it's huge)

TexGen_SSE_realtime_log.7z 553.51 kB · 1 download

Do what I suggested in this post: https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-128/?do=findComment&comment=271741

Add RenderSingle=1 under [TexGen] in H:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini and check if it makes a difference. It helped other people one or two thread pages back that also had an exception in the NVIDIA driver nvoglv64.dll

The realtime log shows that it is not set to 1

[Wulfga]

52 minutes ago, sheson said:

Do what I suggested in this post: https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-128/?do=findComment&comment=271741

Add RenderSingle=1 under [TexGen] in H:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini and check if it makes a difference. It helped other people one or two thread pages back that also had an exception in the NVIDIA driver nvoglv64.dll

The realtime log shows that it is not set to 1

Ahh, that's fair. I had (I promise) set that to 1, but I did a fresh install of all DynDOLOD software and didn't set it back.

I DO THINK I FOUND PART OF THE PROBLEM.

When I completely uninstalled my Nvidia drivers rather than just doing fresh installs etc., it went WAAAY farther than I've ever seen it go before, and I finally got an "OpenGL version too low" error much farther in than normal. [02:52] Error: OpenGL: H:\Modding\Tools\DynDOLOD\TexGen_Output\Textures\dlc01\lod\dlc01dawnguardcastle01lod framebuffer objects unsupported.

I'm currently backing down through versions of the driver trying to find one that works. 531.41-desktop-win10-win11-64bit-international-dch-whql just failed, 531.61 failed previously. I'll add your "1" now for consistency. Thanks for catching that.

(attachments from no driver test where I let Windows 11 handle the GPU)

I'll test the RenderSingle=1 right now.

TexGen_SSE_log.txt bugreport.txt

[sheson]

8 minutes ago, Wulfga said:

Ahh, that's fair. I had (I promise) set that to 1, but I did a fresh install of all DynDOLOD software and didn't set it back.

I DO THINK I FOUND PART OF THE PROBLEM.

When I completely uninstalled my Nvidia drivers rather than just doing fresh installs etc., it went WAAAY farther than I've ever seen it go before, and I finally got an "OpenGL version too low" error much farther in than normal. [02:52] Error: OpenGL: H:\Modding\Tools\DynDOLOD\TexGen_Output\Textures\dlc01\lod\dlc01dawnguardcastle01lod framebuffer objects unsupported.

I'm currently backing down through versions of the driver trying to find one that works. 531.41-desktop-win10-win11-64bit-international-dch-whql just failed, 531.61 failed previously. I'll add your "1" now for consistency. Thanks for catching that.

(attachments from no driver test where I let Windows 11 handle the GPU)

I'll test the RenderSingle=1 right now.

TexGen_SSE_log.txt 156.58 kB · 1 download bugreport.txt 233.76 kB · 1 download

All I ask is this: Install latest driver only without any bloatware. Set RenderSingle=1. In case there is still a problem, upload new log, debug log or realtime log and bugreport.txt. Make sure you are not overclocking or have other hardware issues, like unstable CPU, memory etc.

[Wulfga]

9 minutes ago, sheson said:

All I ask is this: Install latest driver only without any bloatware. Set RenderSingle=1. In case there is still a problem, upload new log, debug log or realtime log and bugreport.txt. Make sure you are not overclocking or have other hardware issues, like unstable CPU, memory etc.

I've followed all your advice- that's what the couple-day pause was. I reviewed the BIOS line by line, removed all of the overclocking (broke my RAID array at 2am on accident) reinstalled everything fresh, and have consistently had the same issue.

With the rolled back driver to 531.41 and your INI edit, it's (veeerrrrrryyyy slowly) working. I owe you a beer.

For the record, I genuinely think there's something in the new Nvidia drivers that are breaking it. RenderSingle=1 on the current drivers did not work. If it were to ever come up again, RenderSingle=1 on nVidia driver version 531.41 worked fine for me. I do have an absolute mountain of other NVIDIA tools for CUDA, etc, so this might be unique to folks creating animations and doing complex AI work, can't say for sure, but it just finished with all overclocking in place and no changes except the single INI edit and the driver rollback. Cheers.

[20:33] Removing temporary files
[20:33] Waiting for Texconv to convert 2 textures
[20:34] TexGen completed successfully
[20:34] Exit TexGen, zip and exit, check log or restart?

Thanks for putting up with me.

[Holt59]

Hi,

I'm trying to run TexGen and DynDOLOD 3 alpha 128 and right now TexGen is crashing when starting to generate texture. The Window event viewer shows

Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33
Faulting module name: nvoglv64.dll, version: 31.0.15.3640, time stamp: 0x6496035a
Exception code: 0xc0000005
Fault offset: 0x000000000155191a
Faulting process id: 0x0x6D08
Faulting application start time: 0x0x1D9AB821A45779D
Faulting application path: D:\Utilities\DynDOLOD 3\TexGenx64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nvmdsi.inf_amd64_3917166697074d95\nvoglv64.dll
Report Id: 7b4587b6-10c3-4330-a247-78f05062c0ba
Faulting package full name: 
Faulting package-relative application ID: 

Unfortunately I don't have any logs under TexGen... I have latest drivers for everything, in particular NVidia. I'm running TexGen64 through MO2.

Any idea how could I go about investigating this?

[sheson]

11 hours ago, Holt59 said:

Hi,

I'm trying to run TexGen and DynDOLOD 3 alpha 128 and right now TexGen is crashing when starting to generate texture. The Window event viewer shows

Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33
Faulting module name: nvoglv64.dll, version: 31.0.15.3640, time stamp: 0x6496035a
Exception code: 0xc0000005
Fault offset: 0x000000000155191a
Faulting process id: 0x0x6D08
Faulting application start time: 0x0x1D9AB821A45779D
Faulting application path: D:\Utilities\DynDOLOD 3\TexGenx64.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nvmdsi.inf_amd64_3917166697074d95\nvoglv64.dll
Report Id: 7b4587b6-10c3-4330-a247-78f05062c0ba
Faulting package full name: 
Faulting package-relative application ID: 

Unfortunately I don't have any logs under TexGen... I have latest drivers for everything, in particular NVidia. I'm running TexGen64 through MO2.

Any idea how could I go about investigating this?

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to enable the real time log in case the tool is being terminated and can not write its log files.

Use search https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search. https://stepmodifications.org/forum/search/?q=nvoglv64.dll&quick=1&type=forums_topic&nodes=223&updated_after=any&sortby=newest

Add RenderSingle=1 under [TexGen] in D:\Utilities\DynDOLOD 3\Edit Scripts\DynDOLOD\TexGen_SSE.ini and check if it makes a difference. It helped other people in the past that also had an exception in the NVIDIA driver nvoglv64.dll

[Holt59]

1 hour ago, sheson said:

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to enable the real time log in case the tool is being terminated and can not write its log files.

Use search https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search. https://stepmodifications.org/forum/search/?q=nvoglv64.dll&quick=1&type=forums_topic&nodes=223&updated_after=any&sortby=newest

Add RenderSingle=1 under [TexGen] in D:\Utilities\DynDOLOD 3\Edit Scripts\DynDOLOD\TexGen_SSE.ini and check if it makes a difference. It helped other people in the past that also had an exception in the NVIDIA driver nvoglv64.dll

Thanks, using `RenderSingle=1` fixed the issue for me.

[BasicallyLuci]

running DynDOLOD i get a repeating message saying LOD billboard(s) not found, and that i should use texgen to generate lod billboards first, which i did, twice.

Also, on running texgen it automatically closes after a while, i cant see if its finished or if this is crashing.

[z929669]

1 hour ago, BasicallyLuci said:

running DynDOLOD i get a repeating message saying LOD billboard(s) not found, and that i should use texgen to generate lod billboards first, which i did, twice.

 

Also, on running texgen it automatically closes after a while, i cant see if its finished or if this is crashing.

You need to provide the TexGen and DynDOLOD logs as indicated in the forum rules and the DynDOLOD OP. This would tell us why you have this problem. It's just as likely that the LODs you are using have issues as it is a TexGen/DynDOLOD issue. The logs reveal all, so that's why they are always required when posting.

[sheson]

13 hours ago, BasicallyLuci said:

running DynDOLOD i get a repeating message saying LOD billboard(s) not found, and that i should use texgen to generate lod billboards first, which i did, twice.

Also, on running texgen it automatically closes after a while, i cant see if its finished or if this is crashing.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log, debug log and bugreport.txt (if it exists) to upload or how to enable the realtimelog and check the Windows event log in case the normal logs were not saved because the program was terminated.

https://dyndolod.info/Generation-Instructions#1-Generate-The-Required-LOD-Assets-with-TexGen
Click Start and wait for the process to complete without errors. Pay attention to all log messages (especially "file not found textures"). It should end with the log message 'TexGen completed successfully'. Do not use the output if there were errors that stopped the process prematurely.

If TexGen is being terminated prematurely, then it can not generate all required LOD assets.

[ExquisiteLemon]

Having major issues getting TexGen to run.  I have used DynDOLOD 3.0 for multiple playthroughs in the past with no issue, and I currently cannot get TexGen to run without crashing and leaving no log behind after about 1 minute of trying to create lods.

I have all the requirements, and have recently just switched from the scripts and dll to the NG version of the plugin in an attempt to get things working.  I am on Skyrim AE 1.6.40.  I have tried using both 32 and 64 bit versions of TexGen.

I have the resources for DynDOLOD being overwritten by everything that is conflicting with it, and have tried reversing these dependencies to no avail. I have been frequently restarting my PC, as well as clearing the TexGenOutput folder every time the program fails and boots to desktop.  Currently on the newest release of DynDOLOD (Alpha 171).

The only new mod I have added to my modlist is Skurkbro's Part 4 which in includes LODs and clutter,  TexGen still does not run upon removing this.

I am really banging my head against the desk with this one if anyone could point me in the right direction.  I would include logs from the folder but like I mentioned, TexGen is not generating them upon what I think is a crash.

[sheson]

1 hour ago, ExquisiteLemon said:

Having major issues getting TexGen to run.  I have used DynDOLOD 3.0 for multiple playthroughs in the past with no issue, and I currently cannot get TexGen to run without crashing and leaving no log behind after about 1 minute of trying to create lods.

I have all the requirements, and have recently just switched from the scripts and dll to the NG version of the plugin in an attempt to get things working.  I am on Skyrim AE 1.6.40.  I have tried using both 32 and 64 bit versions of TexGen.

I have the resources for DynDOLOD being overwritten by everything that is conflicting with it, and have tried reversing these dependencies to no avail. I have been frequently restarting my PC, as well as clearing the TexGenOutput folder every time the program fails and boots to desktop.  Currently on the newest release of DynDOLOD (Alpha 171).

The only new mod I have added to my modlist is Skurkbro's Part 4 which in includes LODs and clutter,  TexGen still does not run upon removing this.

I am really banging my head against the desk with this one if anyone could point me in the right direction.  I would include logs from the folder but like I mentioned, TexGen is not generating them upon what I think is a crash.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
..\DynDOLOD\bugreport.txt - if it exists
If there are no logs or debug logs because the tool is being terminated prematurely, check the Windows Event log for related messages. Add RealTimeLog=1 under [TexGen] or [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\[TexGen|DynDOLOD]_[GAME MODE].INI respectively. Then execute the tool again to generate the real-time debug log in the Logs folder in real time and upload that.

While the DynDOLOD Resources are irrelevant for TexGen, see https://dyndolod.info/Help/DynDOLOD-Resources
Typically DynDOLOD Resources LOD assets should overwrite everything else unless another mod specifically instructs to overwrite DynDOLOD Resources. Refer to Load/Overwrite Orders for detailed explanations.
Also see https://dyndolod.info/Help/Load-Overwrite-Orders

DynDOLOD DLL NG (or its former alternatives) are irrelevant for TexGen.

https://en.wikipedia.org/wiki/Booting

[ExquisiteLemon]

11 hours ago, sheson said:

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
..\DynDOLOD\bugreport.txt - if it exists
If there are no logs or debug logs because the tool is being terminated prematurely, check the Windows Event log for related messages. Add RealTimeLog=1 under [TexGen] or [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\[TexGen|DynDOLOD]_[GAME MODE].INI respectively. Then execute the tool again to generate the real-time debug log in the Logs folder in real time and upload that.

While the DynDOLOD Resources are irrelevant for TexGen, see https://dyndolod.info/Help/DynDOLOD-Resources
Typically DynDOLOD Resources LOD assets should overwrite everything else unless another mod specifically instructs to overwrite DynDOLOD Resources. Refer to Load/Overwrite Orders for detailed explanations.
Also see https://dyndolod.info/Help/Load-Overwrite-Orders

DynDOLOD DLL NG (or its former alternatives) are irrelevant for TexGen.

https://en.wikipedia.org/wiki/Booting

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