Rozen Posted February 1, 2023 Posted February 1, 2023 36 minutes ago, sheson said: Let me know what happens with this test version. https://mega.nz/file/wAJAlaRC#CZ3lzXWBMlpHwd1Eg2xodOJo1tvcXjF0sQ2bXDhHsSI 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
sheson Posted February 1, 2023 Author Posted February 1, 2023 50 minutes ago, Rozen said: 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 Test what happens with this test version https://mega.nz/file/YJgXSJLA#9YpgdccTNnjRu5YwqPWrhwwN8mbwJoxfOrmXcDmMha0 If this happen to run through upload log and debug log anyway. No other logs are needed.
Rozen Posted February 1, 2023 Posted February 1, 2023 5 minutes ago, sheson said: Test what happens with this test version https://mega.nz/file/YJgXSJLA#9YpgdccTNnjRu5YwqPWrhwwN8mbwJoxfOrmXcDmMha0 If this happen to run through upload log and debug log anyway. No other logs are needed. It got through, here is the logs> https://ufile.io/f/ux2yn
sheson Posted February 1, 2023 Author Posted February 1, 2023 19 minutes ago, Rozen said: It got through, here is the logs> https://ufile.io/f/ux2yn So far so good. If you find the time, do a couple more runs to be sure and upload the log/debug log even if they always run through.
Rozen Posted February 1, 2023 Posted February 1, 2023 47 minutes ago, sheson said: So far so good. If you find the time, do a couple more runs to be sure and upload the log/debug log even if they always run through. 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.
Rozen Posted February 1, 2023 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
Rozen Posted February 1, 2023 Posted February 1, 2023 Run 3 got through. logs> https://ufile.io/f/bz8so
sheson Posted February 1, 2023 Author 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.
Rozen Posted February 1, 2023 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
Rozen Posted February 1, 2023 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
sheson Posted February 1, 2023 Author 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.
Rozen Posted February 1, 2023 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
sheson Posted February 1, 2023 Author 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?
Rozen Posted February 1, 2023 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
sheson Posted February 1, 2023 Author 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.
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