Rozen
-
Posts
78 -
Joined
-
Last visited
-
Days Won
1
Everything posted by Rozen
-
I rather not touch my bios setting sense I have only been in there a few times and the few times I was in my bios was to turn on safe boot and a setting I needed on to update to windows 11 and on my video card I am using the gaming profile that it has. I will keep testing when I can and report if I get a bug report log again.
-
Run 1: crashed and no logs besides the one in windows. Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63dfe565 Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6 Exception code: 0xc0000374 Fault offset: 0x000000000010c249 Faulting process id: 0x0x3238 Faulting application start time: 0x0x1D9398ACD3C7CE3 Faulting application path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: c650c480-37df-4000-9de6-c304a8bb562e Faulting package full name: Faulting package-relative application ID: Run 2: Got through, logs> https://ufile.io/f/e41vo Seems like it is getting better.
-
Got a bug report log and the debug log> https://ufile.io/f/7059l
-
grabbing that and going to test now, I will send the debug log too if it makes it.
-
To be on the safe side again I ran texgen again sense i redid my video drivers, texgen is now also moving faster, Got the please wait message again and it made a bug report log. here is the log> https://ufile.io/a8xnb02o
-
ah okay I just seen windows 10 and I was like wait what, but I am on 11 lol and I uninstalled the software and drivers that AMD uses to control their GPU and got the drivers and software from the AMD website here> AMD Drivers and Support | AMD Going to go test that new version now.
-
New Run: Right off the bat it's moving through files so much faster than before, got the OpenGL error again but this time I got a please wait message and it made a bug report log but not the other 2 logs. Here is the bug report log for this run> https://ufile.io/b7wish01 Edit: also looking at your bug report log I see it says I am on windows 10 but I am not I am on windows 11.
-
there was not, and it might be due to like I said about my driver just crashing trying to load up a game. Love AMD's hardware but their software is really tweaky at times lol.
-
Okay so this time it might have been my drivers, I went to load up a game and got a driver crash, going back to do a few runs and hope and pray it was just a driver slowly failing this time. Did a full driver clean re-install and told it to reset its settings on install.
-
Run 2: got an OpenGL Error and it made logs> https://ufile.io/f/oqxhp
-
Run 1: Crashed and made none of the logs. Edit: adding the windows crash report from run 1. Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63deaedc Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6 Exception code: 0xc0000374 Fault offset: 0x000000000010c249 Faulting process id: 0x0x48A8 Faulting application start time: 0x0x1D938D1662D4CD6 Faulting application path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: bd918364-0a2e-4c01-b06b-12c2c98b187e Faulting package full name:
-
It does not, I didn't get any update notice for alpha 3 at all, when I found out there was an update it was by going to your link to it in the Large Reference Bugs Workarounds area and seeing it was a newer version.
-
Run 1: It toke a long time to get past DynDOLOD_Tamriel.dds 16384 x 8192 then got stuck at DynDOLOD_Tamriel_Glow.dds 1024 x 1024 CPU usage stayed around 20% and longer I waited the memory usage went down all the way to only 111.1 MB. After telling it to close it went to the background processes and stayed around 20% CPU usage but the memory jumped up to 890.6 MB, waited a little to see if it would go away but never did so had to end task on it. Logs> https://ufile.io/f/1rfci Run 2: went faster to get past DynDOLOD_Tamriel.dds 16384 x 8192 and got past DynDOLOD_Tamriel_Glow.dds 1024 x 1024 but did not lock up or crash, Logs> https://ufile.io/f/p9z2c
-
ah okay so i just got lucky again lol, testing it now and I will stop with the video then, just thought it would be helpfully to you sense you can see what it is doing and that last video you can see what file it was at before crashing, showing it was around the dds file types.
-
just a heads up I just noticed that you updated the DynDOLOD DLL NG and Scripts 3.00 from alpha 2 to alpha 3 so I am updating that now and doing a few new runs to see what happens. Run 1: Seemed to go faster now making the files on a lot of parts, did not make the logs you been getting me to send again until it was done, Logs> https://ufile.io/f/3clrk Run 2: Same as run 1, Logs for run 2> https://ufile.io/f/e1wta I don't know if I just got lucky runs again but seems like updating the DynDOLOD DLL NG and Scripts 3.00 from alpha 2 to alpha 3 did the trick, I will do a few more test runs when I wake up and let you know what happens and test any new version you need tested if you need me too.
-
Here is the video from run 3, crashes at 9:37 in the video.
-
Did a 3rd run, made a video of this run and uploading it to youtube, i will post the link when the video is done uploading, it did not do what it did last with the sub processes and this time it did not make the logs again, but in windows event viewer I got a crash log. Faulting application name: DynDOLODx64.exe, version: 3.0.0.112, time stamp: 0x63dd1986 Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6 Exception code: 0xc0000374 Fault offset: 0x000000000010c249 Faulting process id: 0x0x24E4 Faulting application start time: 0x0x1D938277974CBBA Faulting application path: C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLODx64.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: c417aa56-1e63-467d-8f9a-a8ac44d4ac79 Faulting package full name: Faulting package-relative application ID: Fault bucket 1804213948848729828, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DynDOLODx64.exe P2: 3.0.0.112 P3: 63dd1986 P4: StackHash_d3f8 P5: 10.0.22621.900 P6: a97a9ed6 P7: c0000374 P8: PCH_6B_FROM_ntdll+0x000000000009F957 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a8b2ca69-337d-4478-a7a5-659ffd65293d.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a9e9642b-98ee-447a-94a3-ef8206ce9b3e.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ce918e57-6074-4a76-980c-a49d1408169d.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.fcd4933c-c558-4d64-afc1-d0e58c7c17af.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.58c0948a-6e07-400c-841c-82e2238439f6.tmp.xml These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DynDOLODx64.exe_11eda9e46b74a64dd9c765c1165be24c312a23_209c72da_debb94ce-78bc-4f27-98d6-f47527ba8b8d Analysis symbol: Rechecking for solution: 0 Report Id: c417aa56-1e63-467d-8f9a-a8ac44d4ac79 Report Status: 268435456 Hashed bucket: c57391a73b2bb2bea909db06ffeeeee4 Cab Guid: 0
-
Just adding this, ran it again with task manager up and it is doing this, and brings a lot of those sub processes up and closes them fast more than one time then goes on without doing it again, on this run it got stuck on [19:50] [DLC01FalmerValley] Creating texture atlas C:\DynDOLOD 3.00-68518-Alpha-111-1673607327\DynDOLOD\DynDOLOD_Output\Textures\DynDOLOD\LOD\DynDOLOD_DLC01FalmerValley.dds 4096 x 4096 and went to 0% COU usage. Also did not make the logs you been getting me to send. https://i.gyazo.com/db40b4056769fb7a8f57bbc8098e16a1.mp4 Ops update it did make the logs this time but only after fully crashing it did they show up. Logs> https://ufile.io/f/cnhhu
-
Okay test run 1 got a crash, it also did not make any of the logs you been getting me to send.
-
I am now on my new video card and will be running tests again here soon, doing a windows update that showed up right before i was going do a new full run with a newly made texgen file. Tested on call of duty already and the new video card is working great.
-
Rub 2 no getting stuck or crash, here is the logs> https://ufile.io/f/eypgr
-
I will run again sense i am still waiting on my video card.
-
No getting stuck or locking up on run 1, here is the logs> https://ufile.io/f/xdm39 Also just letting you know, i do not have my new video card in yet, so still on the same one.
-
it is still crashing randomly but it also started getting stuck again like that and it might be related but don't know. Here are the logs from that run from the video> https://ufile.io/f/wa1hn
-
Here you go I did one more run for the night and made a video showing it with no ini change, it did not crash but got stuck.
