Rozen Posted February 1, 2023 Posted February 1, 2023 3 minutes ago, sheson said: Just run it a few more times, see if it happens again. Okay will do.
Rozen Posted February 1, 2023 Posted February 1, 2023 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
Rozen Posted February 1, 2023 Posted February 1, 2023 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
sheson Posted February 1, 2023 Author Posted February 1, 2023 13 minutes ago, Rozen said: 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 Those logs do not help. Add RealTimeLog=1 to DynDOLOD_SSE.ini, then upload the realtime log from the log folder.
Rozen Posted February 1, 2023 Posted February 1, 2023 10 minutes ago, sheson said: Those logs do not help. Add RealTimeLog=1 to DynDOLOD_SSE.ini, then upload the realtime log from the log folder. Doing that now.
LordIceWolf Posted February 2, 2023 Posted February 2, 2023 Good evening I have been a bit of a problem I am hoping you can help me with. My Grass lods are not generating all types of grass. I noticed that my plugins were missing object bounds for many grass types and I resolved that. I reran Texgen and DynDOLOD afterwards and now I see the grass types in the DynDOLOD_Tamriel.dds file but they are still not generating. I have grass lods in the whiterun plains but It seems to be missing everywhere else where the grass is different (like the Reach for exemple). I went through all the steps of the "No Grass Lods check list". The Grass lods are not present in the bto files. Any Ideas? All my logs are here. Let me know if you need anything else https://drive.google.com/drive/folders/13LSsNUuoOHZKBMdbsvJdJi_OpDp8Ok07?usp=sharing
sheson Posted February 2, 2023 Author Posted February 2, 2023 10 hours ago, LordIceWolf said: Good evening I have been a bit of a problem I am hoping you can help me with. My Grass lods are not generating all types of grass. I noticed that my plugins were missing object bounds for many grass types and I resolved that. I reran Texgen and DynDOLOD afterwards and now I see the grass types in the DynDOLOD_Tamriel.dds file but they are still not generating. I have grass lods in the whiterun plains but It seems to be missing everywhere else where the grass is different (like the Reach for exemple). I went through all the steps of the "No Grass Lods check list". The Grass lods are not present in the bto files. Any Ideas? All my logs are here. Let me know if you need anything else https://drive.google.com/drive/folders/13LSsNUuoOHZKBMdbsvJdJi_OpDp8Ok07?usp=sharing Always use the latest alpha version. Do not waste time using older versions or reporting problems with older versions. Go through every step of the No Grass LOD Check List and not only mention the outcome/result of a couple.
Rozen Posted February 2, 2023 Posted February 2, 2023 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.
sheson Posted February 2, 2023 Author Posted February 2, 2023 41 minutes ago, Rozen said: 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. It is that your setup for some reason sometimes fails with the OpenGL command to generate mipmaps, even on textures for which it worked fine earlier in the same process. The heap crash is most likely caused by not properly recovering from that error in order to keep going instead of stopping the process. This test version should do it without heap crash now https://mega.nz/file/ZJ4VWDLb#SGyHh8rgHYORc1WqdwzvrjJWnihDonkJMwL6AuHDKIM Test with default INIs.
Rozen Posted February 2, 2023 Posted February 2, 2023 6 minutes ago, sheson said: It is that your setup for some reason sometimes fails with the OpenGL command to generate mipmaps, even on textures for which it worked fine earlier in the same process. The heap crash is most likely caused by not properly recovering from that error in order to keep going instead of stopping the process. This test version should do it without heap crash now https://mega.nz/file/ZJ4VWDLb#SGyHh8rgHYORc1WqdwzvrjJWnihDonkJMwL6AuHDKIM Test with default INIs. Okay going to test now.
Rozen Posted February 2, 2023 Posted February 2, 2023 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?
sheson Posted February 2, 2023 Author Posted February 2, 2023 6 minutes ago, Rozen said: 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? Yes.
Rozen Posted February 2, 2023 Posted February 2, 2023 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.
sheson Posted February 2, 2023 Author Posted February 2, 2023 7 minutes ago, Rozen said: 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. No. Read/Write functions do not care how long it takes. They either return an error or are successful when they are done.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now