Rozen

just got done with the new run and no crash, i will test more tomorrow after I get my new video card installed.

Okay that run got done with no crash, i will do one more but it takes almost 2 hrs each time with real time logging on.

I am still doing the run but i was thinking, would it be that your program is on a SSD and my Skyrim is on one of my HDD? maybe the program is trying to go faster than my HDD can go making it error, just asking sense it seems to work fine with no crash every time I turn on real time logging making it go slower.

Will do.

Run 1 got a crash again Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63dbb506 Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6 Exception code: 0xc0000374 Fault offset: 0x000000000010c249 Faulting process id: 0x0xF4E0 Faulting application start time: 0x0x1D93709074E78FA Faulting application path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 4322bd91-7999-4200-9a0c-8a1fbafd6b49 Faulting package full name: Faulting package-relative application ID: Want to put the real time logging back on?

Okay going to test now.

I am still testing with the setting in the ini but it has not crashed yet so still doing runs when I can it just takes a long time with the real time log on. It like your program is got a mind of its own lol. Also, tomorrow I am getting a new video card in, going from a RX 580 to a RX 6650 XT sense i have had this 580 for years now.

Doing that now.

did a new run and got a crash again at the same spot as the last run. Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63da83ed Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6 Exception code: 0xc0000374 Fault offset: 0x000000000010c249 Faulting process id: 0x0x1883C Faulting application start time: 0x0x1D9368140BA9C96 Faulting application path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 415e9fd3-d510-4b05-905d-e854754446d5 Faulting package full name: Faulting package-relative application ID: Also seen this stuff in the event viewer Log Name: Application Source: Windows Error Reporting Date: 2/1/2023 4:14:51 PM Event ID: 1001 Task Category: None Level: Information Keywords: User: SYSTEM Computer: DESKTOP-K3NF99T Description: Fault bucket 2065828522773481299, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DynDOLODx64.exe P2: 3.0.0.112 P3: 63da83ed P4: StackHash_6a2a P5: 10.0.22621.900 P6: a97a9ed6 P7: c0000374 P8: PCH_D2_FROM_ntdll+0x000000000009F957 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c30454a5-b873-43ca-822f-2db66aceb807.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.466ee0df-9fac-4e88-b902-33f42840f9fa.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ef876ecd-1235-4913-8550-48a20c6cf3d2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.af69eb16-f35e-402e-bad4-e502bcd6add0.tmp.txt \\?\C:\Users\funny\AppData\Local\Temp\WER.e302ad19-1391-44da-add7-92bfd2fdfafc.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f64ea648-4974-4040-8d50-e932a242a930.tmp.xml These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DynDOLODx64.exe_40d8d3a0e74f7cedaeec20f980ae9efa2cec1c6_86e3828f_b9706448-cd7a-4ac3-863a-018ad58b1c0b Analysis symbol: Rechecking for solution: 0 Report Id: 415e9fd3-d510-4b05-905d-e854754446d5 Report Status: 268435456 Hashed bucket: 6c265e6444821ad60cab4c18a2c88753 Cab Guid: 0 and Log Name: Application Source: Windows Error Reporting Date: 2/1/2023 4:14:49 PM Event ID: 1001 Task Category: None Level: Information Keywords: User: DESKTOP-K3NF99T\funny Computer: DESKTOP-K3NF99T Description: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DynDOLODx64.exe P2: 3.0.0.112 P3: 63da83ed P4: StackHash_6a2a P5: 10.0.22621.900 P6: a97a9ed6 P7: c0000374 P8: PCH_D2_FROM_ntdll+0x000000000009F957 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c30454a5-b873-43ca-822f-2db66aceb807.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.466ee0df-9fac-4e88-b902-33f42840f9fa.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ef876ecd-1235-4913-8550-48a20c6cf3d2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.af69eb16-f35e-402e-bad4-e502bcd6add0.tmp.txt \\?\C:\Users\funny\AppData\Local\Temp\WER.e302ad19-1391-44da-add7-92bfd2fdfafc.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f64ea648-4974-4040-8d50-e932a242a930.tmp.xml These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_DynDOLODx64.exe_40d8d3a0e74f7cedaeec20f980ae9efa2cec1c6_86e3828f_cab_b9706448-cd7a-4ac3-863a-018ad58b1c0b Analysis symbol: Rechecking for solution: 0 Report Id: 415e9fd3-d510-4b05-905d-e854754446d5 Report Status: 4 Hashed bucket: Cab Guid: 0

It happened again on the first try. Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63da83ed Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6 Exception code: 0xc0000374 The last thing i seen show up was stuff for the main world map and in the last 2 logs it made was the one for LODGen_SSE_Tamriel_log.txt sense that was running when it happened and DynDOLOD_SSE_TexturesUsed_Tamriel, inside the logs LODGen_SSE_Tamriel_log.txt got to ,textures\wizkid pole\wiz_pole_05a.dds,textures\wizkid pole\wiz_pole_02_n.dds: 16 -> 73 | 32, 0 Log ended at 3:55:01 PM (00:03:43) Code: 0 and DynDOLOD_SSE_TexturesUsed_Tamriel got to textures\wizkid pole\wiz_pole_06.dds,8,textures\wizkid pole\wiz_pole_06_n.dds, textures\wizkid pole\wiz_pole_06_rock.dds,8,textures\wizkid pole\wiz_pole_06_rock_n.dds, Here are the logs just encase they help> https://ufile.io/f/nvbqg

Okay will do.

I would not know how sense the times it has hang up and/or crashed has always been around the glow.dds files being made, and it was never the same one it would do it on. Edit: So like sometimes it was after a glow.dds file or before but that's as far as I can tell what it was doing when it would just crash, and the hang ups was always at a glow.dds file but not the same one every time.

Everything on my pc is working fine and there are no other errors I am seeing in the event viewer, i just got done playing the new call of duty yesterday so I would think if it was something in my hardware it would make issues in a game like that easily sense that runs my CPU and GPU harder for longer than your program dose. Edit: Also, I don't know what it was doing when it happened for that one sense it would crash at random times.

Also looking at the logs I found this where it would just get stuck. The program DynDOLODx64.exe version 3.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. When going there this is the info I see for the program Description Faulting Application Path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe Problem signature Problem Event Name: APPCRASH Application Name: DynDOLODx64.exe Application Version: 3.0.0.112 Application Timestamp: 63da6bdd Fault Module Name: StackHash_d3f8 Fault Module Version: 10.0.22621.900 Fault Module Timestamp: a97a9ed6 Exception Code: c0000374 Exception Offset: PCH_D2_FROM_ntdll+0x000000000009F957 OS Version: 10.0.22621.2.0.0.768.101 Locale ID: 1033 Additional Information 1: d3f8 Additional Information 2: d3f8511deccc73d94b0e55f0a35c4ccf Additional Information 3: 748a Additional Information 4: 748acf82d1efe0f9c372d6eeb532c8cc Extra information about the problem Bucket ID: d87834348914bff9173a4064cc03ebe1 (1673721013185276897) Edit: it has other logs too if you need them for the times, it outright crashed. Last Edited: wanted to add this sense it says hang in it. Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe Problem signature Problem Event Name: AppHangB1 Application Name: DynDOLODx64.exe Application Version: 3.0.0.0 Application Timestamp: 63c135b8 Hang Signature: 686e Hang Type: 134217728 OS Version: 10.0.22621.2.0.0.768.101 Locale ID: 1033 Additional Hang Signature 1: 686eadb77f72d14db40101f61d1eaed9 Additional Hang Signature 2: aca4 Additional Hang Signature 3: aca4fa2adc763a561d8a1904720aad12 Additional Hang Signature 4: 686e Additional Hang Signature 5: 686eadb77f72d14db40101f61d1eaed9 Additional Hang Signature 6: aca4 Additional Hang Signature 7: aca4fa2adc763a561d8a1904720aad12

what would i be looking for in event viewer? Edit: Found it XD Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63da6bdd Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6 Exception code: 0xc0000374

Run 3 got through. logs> https://ufile.io/f/bz8so

Run 2 got a random crash with no bug report file made and it did not make the 2 logs that I have been sending.

Okay, will do and just want to say thank you for making this great program/mod. Run 1 got through logs> https://ufile.io/f/4vc31 I will do the next run now after sending this message.

It got through, here is the logs> https://ufile.io/f/ux2yn

Sorry it toke so long, I found out that ZUPA does not work with AE and had to change it out with Animated Potions, so I ended up having to run loot again, ran texgen to be on the safe side and run nemesis. It crashed with no bug report this time, deleted the logs it did make and tried again sense it didn't even make the logs that I have been sending. On run 2 I looked at what logs it is making first and it seems to be making the Dynamic LOD log and Object LOD log first, do you want them? Also, on run 2 it Crashed with the please wait message then gave me an error message Error: OpenGL: invalid operation while processing A07FAA33 (4) while processing textures\lod\rubblepilelod.dds. Here is the logs> https://ufile.io/f/hfmk4

Got an OpenGL error. Here is the Logs> https://ufile.io/f/4gowf

Strange i dragged and dropped all of them into the site. Here you go> https://ufile.io/f/iokog

Got a new crash report, i am still using the same version you gave me to test with, this time it was the same file type and it pop up a please wait message and did nothing after that i can tell, CPU usage went to 0% after and it made a bug report file. Here is the logs> https://ufile.io/dstkwq2x

it got through but took longer, here is the logs> https://ufile.io/f/uycmw

Okay thank you for letting me know, want me to move to the .ini change or do one more without the .ini change to see what happens?