Jump to content

Rozen

Citizen
  • Posts

    78
  • Joined

  • Last visited

  • Days Won

    1

Rozen last won the day on August 14 2021

Rozen had the most liked content!

Contact Methods

  • Discord
    Rozen Sabra Maiden#0209
  • Nexus Mods
    RozenJuliteMaiden

Profile Information

  • Favorite Mod(s)
    Legacy of the Dragonborn

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Rozen's Achievements

Noble

Noble (3/12)

2

Reputation

  1. 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.
  2. 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.
  3. Got a bug report log and the debug log> https://ufile.io/f/7059l
  4. grabbing that and going to test now, I will send the debug log too if it makes it.
  5. 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
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. Run 2: got an OpenGL Error and it made logs> https://ufile.io/f/oqxhp
  11. 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:
  12. 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.
  13. 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
  14. 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.
  15. 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.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.