Access violation at address ... in module DynDOLOD.exe

[moose]

Hopefully this is the right forum and I'm doing this correctly.

I have gone through and resolved as many of the DynDOLOD summary issues as I can, shuffled around mods, disabled mods, re-generated the textures using the other program, cleaned up mods using xEdit, and so on and so forth.  Ultimately, I keep getting the same two lines in the resulting error window after it attempts to generate an "atlas" or whatever the final message is.

One or more errors occurred Access violation at address 0040A9B4 in module 'DynDOLOD.exe'.
Read of address 00000000

These two lines often get repeated several additional times in the error message window. From what I understand, "0040A9B4" should be the form ID of an asset of some sort in Skyrim's base module, but I cannot find it with xEdit nor can I find anyone else on the internet having an issue with this specific form ID. Likewise, I have no idea if it's actually the culprit behind these errors. Assistance would be appreciated, as would be patience: I am not very good at the technical side of modding games.

https://ufile.io/ys2y5z4s

These should be the bug report file, the debug log, and the truncated log, as requested.

[sheson]

On 4/8/2023 at 4:34 AM, moose said:

Hopefully this is the right forum and I'm doing this correctly.

I have gone through and resolved as many of the DynDOLOD summary issues as I can, shuffled around mods, disabled mods, re-generated the textures using the other program, cleaned up mods using xEdit, and so on and so forth. Ultimately, I keep getting the same two lines in the resulting error window after it attempts to generate an "atlas" or whatever the final message is.

One or more errors occurred Access violation at address 0040A9B4 in module 'DynDOLOD.exe'.
Read of address 00000000

These two lines often get repeated several additional times in the error message window. From what I understand, "0040A9B4" should be the form ID of an asset of some sort in Skyrim's base module, but I cannot find it with xEdit nor can I find anyone else on the internet having an issue with this specific form ID. Likewise, I have no idea if it's actually the culprit behind these errors. Assistance would be appreciated, as would be patience: I am not very good at the technical side of modding games.

https://ufile.io/ys2y5z4s

These should be the bug report file, the debug log, and the truncated log, as requested.

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen. The x86 versions may run into memory errors especially with large texture resolution settings and are included in case a x86 OS is used. They are functionally identical, the only difference is the supported CPU architecture.

https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory
Use the x64 versions of the tools. Let the OS handle virtual memory/page file settings. Close other programs and background processes.

A memory address is not a form id in a plugin.

[z929669]

1 hour ago, moose said:

Hopefully this is the right forum and I'm doing this correctly.

I have gone through and resolved as many of the DynDOLOD summary issues as I can, shuffled around mods, disabled mods, re-generated the textures using the other program, cleaned up mods using xEdit, and so on and so forth.  Ultimately, I keep getting the same two lines in the resulting error window after it attempts to generate an "atlas" or whatever the final message is.

One or more errors occurred Access violation at address 0040A9B4 in module 'DynDOLOD.exe'.
Read of address 00000000

These two lines often get repeated several additional times in the error message window. From what I understand, "0040A9B4" should be the form ID of an asset of some sort in Skyrim's base module, but I cannot find it with xEdit nor can I find anyone else on the internet having an issue with this specific form ID. Likewise, I have no idea if it's actually the culprit behind these errors. Assistance would be appreciated, as would be patience: I am not very good at the technical side of modding games.

https://ufile.io/ys2y5z4s

These should be the bug report file, the debug log, and the truncated log, as requested.

This looks like a general error cause by Windows Security or antivirus. It can also result if you have your modding assets located in UAC-controlled paths like %USERPROFILE% and %APPDATA%. See this post for a method to resolve.

Also see the OP for exactly what logs to provide and upload those as well.

[moose]

Quote

This looks like a general error cause by Windows Security or antivirus. It can also result if you have your modding assets located in UAC-controlled paths like %USERPROFILE% and %APPDATA%. See this post for a method to resolve.

Also see the OP for exactly what logs to provide and upload those as well.

Thank you for your swift response; just tried the abovementioned fix. DynDOLOD made it past "Creating Texture Atlas" and seems to have gotten a little further, but it has once again barfed out the same errors with the same messages again. 

As far as I'm aware, I don't think I have any of the modding assets in %APPDATA% or %USERPROFILE%. There seems to be a few folders and text documents for the Vortex mod manager in there, but they seem specific to the program itself and have nothing to do with the assets being worked with.

https://ufile.io/f/cjtie
Logs, including the extra ones regarding LODGen upload/paste. (I think that's right? Can't find any other requested logs in the OP)

Edited April 8, 2023 by moose
accidentally didn't quote

[moose]

On 4/8/2023 at 6:58 AM, sheson said:

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen. The x86 versions may run into memory errors especially with large texture resolution settings and are included in case a x86 OS is used. They are functionally identical, the only difference is the supported CPU architecture.

https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory
Use the x64 versions of the tools. Let the OS handle virtual memory/page file settings. Close other programs and background processes.

A memory address is not a form id in a plugin.

This seems to have worked! I still get a summary of messages from errors, but the primary issue of DynDOLOD not generating LODs at all has been remedied. I wasn't aware of the difference between a memory address and a form ID; that probably explains why I couldn't find that asset...

Thank you for your assistance, your swiftness in helping me resolve this, and - most of all - for your patience!

[Legaciii]

Whenever I activate dynlod it ends with this error Access violation at address 0040A9B4 in module 'DynDOLOD.exe'. Read of address 00000000

I can post the full log if needed but changing setting I still get this 

[sheson]

On 10/28/2023 at 9:20 PM, Legaciii said:

Whenever I activate dynlod it ends with this error Access violation at address 0040A9B4 in module 'DynDOLOD.exe'. Read of address 00000000

I can post the full log if needed but changing setting I still get this 

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log, debug log and bugreport.txt (if it exits) to upload when making posts.

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen. The x86 versions may run into memory errors especially with large texture resolution settings and are included in case a x86 OS is used. They are functionally identical, the only difference is the supported CPU architecture.

[Marina]

Quote

Whenever I activate dynlod it ends with this error Access violation at address 0040A9B4 in module 'DynDOLOD.exe'. Read of address 00000000

I can post the full log if needed but changing setting I still get this 

I'm getting a similar error message, unfortunately.

Hopefully this is the right bugreport.

Edited November 1, 2023 by Marina

[Marina]

Sheson, I think you overlooked my comment.

[sheson]

On 11/1/2023 at 4:16 PM, Marina said:

Sheson, I think you overlooked my comment.

From the first post at https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-155/:
"Useless "me too" posts without logs are going to be ignored or deleted."

Since you claim you have the same error like the post you are quoting, the same reply/solution applies.

 

[Marina]

8 hours ago, sheson said:

From the first post: "Useless "me too" posts without logs are going to be ignored or deleted."
Since you claim you have the same error like the post you are quoting, the same reply/solution applies.

I'm sorry, looks like I was the one overlooking something (though I didn't have the exact same error). Thank you for your patience!

Well, I uninstalled the 86x versions, as you suggested, which might have helped?! Now I'm getting a new error message to which I couldn't find a thread: "OpenGL: 674C7174 framebuffer incomplete attachment".

Edit: Oh, sorry - the bugreport is the wrong one. I'll try to make a new one.

Edit 2: Geez, I'm so stupid! I need to install the newest grahics drivers... I'll give it a shot and come back later. *sighs*

Edit 3: I'm getting the feeling I will never be able to generate the new LODs.  Now it's "access violation at address 0040A9B4 (...)". I've added the new text documents just in case you can help me one more time. I can (almost) rule out the points mentioned under the error, the only thing I don't know is if my CPU is unstable, but I doubt it. The bugreport said I was running out of memory. I just googled thrat phrase and I'm a little bit confused. Does it mean the hard disc containing my OS has too less capacity? Sorry, as you probably noticed, English is not my native language.

Logs.rar

Edited November 2, 2023 by Marina

[sheson]

On 11/1/2023 at 11:52 PM, Marina said:

I'm sorry, looks like I was the one overlooking something (though I didn't have the exact same error). Thank you for your patience!

Well, I uninstalled the 86x versions, as you suggested, which might have helped?! Now I'm getting a new error message to which I couldn't find a thread: "OpenGL: 674C7174 framebuffer incomplete attachment".

Edit: Oh, sorry - the bugreport is the wrong one. I'll try to make a new one.

Edit 2: Geez, I'm so stupid! I need to install the newest grahics drivers... I'll give it a shot and come back later. *sighs*

Edit 3: I'm getting the feeling I will never be able to generate the new LODs.  Now it's "access violation at address 0040A9B4 (...)". I've added the new text documents just in case you can help me one more time. I can (almost) rule out the points mentioned under the error, the only thing I don't know is if my CPU is unstable, but I doubt it. The bugreport said I was running out of memory. I just googled thrat phrase and I'm a little bit confused. Does it mean the hard disc containing my OS has too less capacity? Sorry, as you probably noticed, English is not my native language.

Logs.rar 334.15 kB · 0 downloads

The last generation in the uploaded TexGen log and debug log shows that it was successful (2 trees are missing textures, though) and the TexGen_Output.zip has been created.

You did not upload a DynDOLOD log or debug log. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

The bugreport.txt shows that DynDOLOD.exe is running out of memory.

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen. The x86 versions may run into memory errors especially with large texture resolution settings and are included in case a x86 OS is used. They are functionally identical, the only difference is the supported CPU architecture.

https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory
Use the x64 versions of the tools. Let the OS handle virtual memory/page file settings. Close other programs and background processes.

DynDOLODx64.exe is the x64 version of the tool.

[Marina]

18 hours ago, sheson said:

The last generation in the uploaded TexGen log and debug log shows that it was successful (2 trees are missing textures, though) and the TexGen_Output.zip has been created.

You did not upload a DynDOLOD log or debug log. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

The bugerport.txt shows that DynDOLOD.exe is running out of memory.

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen. The x86 versions may run into memory errors especially with large texture resolution settings and are included in case a x86 OS is used. They are functionally identical, the only difference is the supported CPU architecture.

https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory
Use the x64 versions of the tools. Let the OS handle virtual memory/page file settings. Close other programs and background processes.

DynDOLODx64.exe is the x64 version of the tool.

As I said, I'm already using the x64 versions of the tools.

I closed all unnecessary programs (my internal memory runs with 30 % - less is not possible) and got a new bugreport.

Logs 2

Edited November 3, 2023 by Marina

[sheson]

5 hours ago, Marina said:

As I said, I'm already using the x64 versions of the tools.

I closed all unnecessary programs (my internal memory runs with 30 % - less is not possible) and got a new bugreport.

Logs 2

The log, debug log and bugreport.txt show that DynDOLOD.exe is being used and running out of memory.

https://dyndolod.info/Installation-Instructions
Use the x64 versions of DynDOLOD/TexGen.

https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory
Use the x64 versions of the tools.

DynDOLODx64.exe is the x64 version of the tool.

[Legaciii]

[Window Title]
DynDOLOD

[Main Instruction]
One or more errors occurred Access violation at address 0040A9B4 in module 'DynDOLOD.exe'.

[Content]
Read of address 00000000 Access violation at address 0040A9B4 in module 'DynDOLOD.exe'. Read of address 00000000 Access violation at address 0040A9B4 in module 'DynDOLOD.exe'. Read of address 00000000.

Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.

[OK] [Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

 

I have done all of the recommended fixes. It is in its own folder in the root directory, I added all of the recommendations in the file as well.

DynDOLOD_SSE_ChildworldCopies_Tamriel.txt

[sheson]

6 hours ago, Legaciii said:

[Window Title]
DynDOLOD

[Main Instruction]
One or more errors occurred Access violation at address 0040A9B4 in module 'DynDOLOD.exe'.

[Content]
Read of address 00000000 Access violation at address 0040A9B4 in module 'DynDOLOD.exe'. Read of address 00000000 Access violation at address 0040A9B4 in module 'DynDOLOD.exe'. Read of address 00000000.

Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.

[OK] [Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

 

I have done all of the recommended fixes. It is in its own folder in the root directory, I added all of the recommendations in the file as well.

DynDOLOD_SSE_ChildworldCopies_Tamriel.txt 49.61 kB · 1 download

The already given answers above still apply.

Nobody knows what "all of the recommended fixes" means. You are still not using the x64 version.

There seems to be no purpose in posting the child world copy log instead of the DynDOLOD log, debug log and bugreport.txt