Access Violation Error on Generating LODS

[pohtatoe]

Receiving the following error on running DynDOLOD x64:
Exception in unit userscript line 337: Access violation at address 00000000015A60EF in module 'DynDOLODx64.exe'. Read of address 0000000000000000

I'm running as Administrator, and my DynDOLOD is located in its own directory in the Skyrim folder.

Here are the bug report and log:

bugreport.txt

DynDOLOD_TES5_log.txt

Any and all help is appreciated. Thanks

[z929669]

5 hours ago, pohtatoe said:

Receiving the following error on running DynDOLOD x64:
Exception in unit userscript line 337: Access violation at address 00000000015A60EF in module 'DynDOLODx64.exe'. Read of address 0000000000000000

I'm running as Administrator, and my DynDOLOD is located in its own directory in the Skyrim folder.

Here are the bug report and log:

bugreport.txt

DynDOLOD_TES5_log.txt

Any and all help is appreciated. Thanks

Look at the pinned topic in this very forum or use search. This sounds like the same issue with Windows Security 'features'

[pohtatoe]

The only suggestions I'm seeing are regarding adding exceptions to Windows Security... I've added the processes DynDOLODx64.exe and TexGenx64.exe as well as the entire DynDOLOD directory to the exclusion list, as well as turning off Real-Time Protection altogether and I still see the same error. Not sure what else to try.

Last time I tried using dyndolod was last November and it worked, so it's either a messed up mod (but i've cleaned everything indicated in LOOT) or a Windows update that's broken something. Not sure what exactly it could be but I'm out of ideas to fix it...

[z929669]

1 hour ago, pohtatoe said:

The only suggestions I'm seeing are regarding adding exceptions to Windows Security... I've added the processes DynDOLODx64.exe and TexGenx64.exe as well as the entire DynDOLOD directory to the exclusion list, as well as turning off Real-Time Protection altogether and I still see the same error. Not sure what else to try.

Last time I tried using dyndolod was last November and it worked, so it's either a messed up mod (but i've cleaned everything indicated in LOOT) or a Windows update that's broken something. Not sure what exactly it could be but I'm out of ideas to fix it...

Sheson can help more, but while he is away, I would try loading up a vanilla instance to see if DynDOLOD runs correctly with that. This will rule out a mod-specific issue.

[sheson]

Replace ..\DynDOLOD\Edit Scripts\DynDOLOD Worlds.pas with the version attached and try again. 

DynDOLOD Worlds.pas

[win92]

Having the same problem.

" Exception in unit userscript line 350: Access violation at address 00000000015A623F in module 'DynDOLODx64.exe'. Read of address 0000000000000000 "

Same as Pohtatoe, running as Admin, Anti-virus exclusion done, not sure what is wrong here.. last time i used Dyndolod was like 3 months ago and it was working fine.

 I really need help with this, sorry for the bother.

DynDOLOD_SSE_log.txtbugreport.txt

[sheson]

On 7/17/2022 at 8:58 PM, win92 said:

Having the same problem.

" Exception in unit userscript line 350: Access violation at address 00000000015A623F in module 'DynDOLODx64.exe'. Read of address 0000000000000000 "

Same as Pohtatoe, running as Admin, Anti-virus exclusion done, not sure what is wrong here.. last time i used Dyndolod was like 3 months ago and it was working fine.

 I really need help with this, sorry for the bother.

DynDOLOD_SSE_log.txt 990.63 kB · 4 downloads bugreport.txt 54.25 kB · 4 downloads

Comparing the messages shows it is not the same problem. You are using Skyrim Special Edition, while pohtatoe uses Skyrim Legendary Edition.

Do not install DynDOLOD into any mod manager folders.
Check the load order for errors with xEdit error check and especially correct unresolved form id errors.

Consider using DynDOLOD 3 Alpha for better problem detection/handling.

[win92]

On 7/19/2022 at 5:34 AM, sheson said:

Comparing the messages shows it is not the same problem. You are using Skyrim Special Edition, while pohtatoe uses Skyrim Legendary Edition.

Do not install DynDOLOD into any mod manager folders.
Check the load order for errors with xEdit error check and especially correct unresolved form id errors.

Consider using DynDOLOD 3 Alpha for better problem detection/handling.

Thanks for the answer! I did as you said, moved Dyndolod to a different folder, and switched to 3. At first that did not fix the issue, but after doing some cleaning and fixing some errors in SSEEdit, Dyndolod was able to finish the process without problems!

 Thanks for the help!