Rozen Posted February 1, 2023 Share Posted February 1, 2023 (edited) 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. Edited February 1, 2023 by Rozen Link to comment Share on other sites More sharing options...
Rozen Posted February 1, 2023 Share Posted February 1, 2023 Run 3 got through. logs> https://ufile.io/f/bz8so Link to comment Share on other sites More sharing options...
sheson Posted February 1, 2023 Author Share Posted February 1, 2023 51 minutes ago, Rozen said: 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. Check the Windows Event log for related entries. The others indeed went through without any failures. Link to comment Share on other sites More sharing options...
Rozen Posted February 1, 2023 Share Posted February 1, 2023 (edited) 20 minutes ago, sheson said: Check the Windows Event log for related entries. The others indeed went through without any failures. 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 Edited February 1, 2023 by Rozen Link to comment Share on other sites More sharing options...
Rozen Posted February 1, 2023 Share Posted February 1, 2023 (edited) 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 Edited February 1, 2023 by Rozen Link to comment Share on other sites More sharing options...
sheson Posted February 1, 2023 Author Share Posted February 1, 2023 46 minutes ago, Rozen said: 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 Do you know what it was doing when the exception c0000374 happened? If we assume that the AMD driver is stable, how certain are you about the hardware (memory, power supply), related BIOS settings. The issue(s) just seems very random/all over the place. Link to comment Share on other sites More sharing options...
Rozen Posted February 1, 2023 Share Posted February 1, 2023 (edited) 20 minutes ago, sheson said: Do you know what it was doing when the exception c0000374 happened? If we assume that the AMD driver is stable, how certain are you about the hardware (memory, power supply), related BIOS settings. The issue(s) just seems very random/all over the place. 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. Edited February 1, 2023 by Rozen Link to comment Share on other sites More sharing options...
sheson Posted February 1, 2023 Author Share Posted February 1, 2023 5 minutes ago, Rozen said: 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. So you don't know what it was doing when the exception c0000374 happened? Can you reproduce it? Link to comment Share on other sites More sharing options...
Rozen Posted February 1, 2023 Share Posted February 1, 2023 (edited) 9 minutes ago, sheson said: So you don't know what it was doing when the exception c0000374 happened? Can you reproduce it? 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. Edited February 1, 2023 by Rozen Link to comment Share on other sites More sharing options...
sheson Posted February 1, 2023 Author Share Posted February 1, 2023 6 minutes ago, Rozen said: I would not know how sense the times it has hang up and /or crashed as always been around the glow.dds files being made, and it was never the same one it would do it on. Just run it a few more times, see if it happens again. Link to comment Share on other sites More sharing options...
Rozen Posted February 1, 2023 Share Posted February 1, 2023 3 minutes ago, sheson said: Just run it a few more times, see if it happens again. Okay will do. Link to comment Share on other sites More sharing options...
Rozen Posted February 1, 2023 Share 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 Link to comment Share on other sites More sharing options...
Rozen Posted February 1, 2023 Share 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 Link to comment Share on other sites More sharing options...
sheson Posted February 1, 2023 Author Share 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. Link to comment Share on other sites More sharing options...
Rozen Posted February 1, 2023 Share 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. Link to comment Share on other sites More sharing options...
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