Access violation at address with DynDOLOD 3 alpha 170

[Diogo_HSS]

I did 8 tries, more or less, and in most of then I got this Access violation at address ERROR, not always on the same address.

In the logs it says i'm in windows 10 but I'm on windows 11 and I added the folder C:\Modding to defenders exceptions and even tried to run with it disabled

bugreport.txt https://paste.ee/p/ZgTL4
latest DynDOLOD_SSE_log https://paste.ee/p/kSURl
DynDOLOD_SSE_Debug_log https://ufile.io/fkdch5r1

[sheson]

7 hours ago, Diogo_HSS said:

I did 8 tries, more or less, and in most of then I got this Access violation at address ERROR, not always on the same address.

In the logs it says i'm in windows 10 but I'm on windows 11 and I added the folder C:\Modding to defenders exceptions and even tried to run with it disabled

bugreport.txt https://paste.ee/p/ZgTL4
latest DynDOLOD_SSE_log https://paste.ee/p/kSURl
DynDOLOD_SSE_Debug_log https://ufile.io/fkdch5r1

[12:39] Error while loading images from memory 000000018E141010 (11184976 Bytes) (file format: dds). Exception Message: Access violation at address 0000000000510A6A in module 'DynDOLODx64.exe'. Write of address 0000000000000000 while processing textures\architecture\riften\riftenstonewalledge01.dds

The bugreport.txt and DynDOLOD log only contain one session with one access violation

Is it always reporting the same texture?

Can you do a quick test if it also happens without the crapware from AMD running?
Close or terminate amdfendrsr.exe, amdow.exe, AMDRSServ.exe, AMDRSSrcExt.exe, atieclxx.exe, atiesrxx.exe, AUEPMaster.exe, AUEPDU.exe, cncmd.exe,PresentMon-x64.exe, RadeonSoftware.exe in task manager.

[Diogo_HSS]

I've killed each process on task manager that started with "AMD" even had to kill some multiple times because they were reopening.

I'll try again with the processes you mentioned, since the ones starting with "AMD" seen to not be all of it.

In the mean time, here is the full DynDOLOD_SSE_log from multiple runs ufile.io/pg58l1ia.

[Diogo_HSS]

6 hours ago, sheson said:

[12:39] Error while loading images from memory 000000018E141010 (11184976 Bytes) (file format: dds). Exception Message: Access violation at address 0000000000510A6A in module 'DynDOLODx64.exe'. Write of address 0000000000000000 while processing textures\architecture\riften\riftenstonewalledge01.dds

The bugreport.txt and DynDOLOD log only contain one session with one access violation

Is it always reporting the same texture?

Can you do a quick test if it also happens without the crapware from AMD running?
Close or terminate amdfendrsr.exe, amdow.exe, AMDRSServ.exe, AMDRSSrcExt.exe, atieclxx.exe, atiesrxx.exe, AUEPMaster.exe, AUEPDU.exe, cncmd.exe,PresentMon-x64.exe, RadeonSoftware.exe in task manager.

Happened again

[Window Title]
DynDOLOD

[Main Instruction]
Access violation at address 000000000040F1B0 in module 'DynDOLODx64.exe'.

[Content]
Read of address FFFFFFFFFFFFFFFF while processing textures\architecture\riften\riftenhouseplanks02.dds.

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.

[Exit DynDOLOD]

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

all the logs: https://ufile.io/4ev7qhg5

[Diogo_HSS]

[Window Title]
DynDOLOD

[Main Instruction]
Error while loading images from memory 00000001C1A51010 (11184952 Bytes) (file format: dds).

[Content]
Exception Message: Access violation at address 0000000000510A6A in module 'DynDOLODx64.exe'. Write of address 0000000000000000 while processing textures\architecture\riften\riftenlogsiding01.dds.

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.

[Exit DynDOLOD]

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

Anote one just now after reruning xlodgen, acmos and texgen

[sheson]

The error messages are all over the place, indicating memory issues.

Double check BIOS (memory timings) and other hardware settings, overclocking etc. to make sure the system is stable.
Also check memory usage via task manager while the tool is running if maybe the system runes out of memory. Let Windows handle page file/virtual memory etc.

[Diogo_HSS]

Disabled the custom pagefile i've set to windows from a wabbajack modlist installation guide and it worked.

I also tried running with the memories in stock (2666) instead of the XMP profile (3200), but did not work at first, only after letting windows handle pagefile. Thanks!

[MatsurikoDlight]

i was looking at this as i was having the same problem, in my case i resolved it by changing the "managed by the os virtual memory" thing and setting it up at a random big amount (like 100 gb for testing in an non os disk and disabling the os one) and worked.

The reason why i tried this is because in the event manager there was an error especificaly about dyndolod and virtual memory "Resource-Exhaustion-Detector".

I looked at the task manager while runing with this new limit and every so often, the virtual memory, does a peak of 45 gb for like 3 seconds and i think it may be tryping the os on some way that.

So atleast in my case, if i let windows manage the virtual memory, it maked the os either close some random process on windows (generaly the window manager, making the system not crash but just black screen you cant do anything but it still runing) or make dyndolod trow an access violation in some file during those peaks (in my case i got 2 diferent files). Everything is working now. 

Just in case, i have a Ryzen 1600 with a rx480 16 gb ram, Windows 10

[sheson]

6 hours ago, MatsurikoDlight said:

i was looking at this as i was having the same problem, in my case i resolved it by changing the "managed by the os virtual memory" thing and setting it up at a random big amount (like 100 gb for testing in an non os disk and disabling the os one) and worked.

The reason why i tried this is because in the event manager there was an error especificaly about dyndolod and virtual memory "Resource-Exhaustion-Detector".

I looked at the task manager while runing with this new limit and every so often, the virtual memory, does a peak of 45 gb for like 3 seconds and i think it may be tryping the os on some way that.

So atleast in my case, if i let windows manage the virtual memory, it maked the os either close some random process on windows (generaly the window manager, making the system not crash but just black screen you cant do anything but it still runing) or make dyndolod trow an access violation in some file during those peaks (in my case i got 2 diferent files). Everything is working now. 

Just in case, i have a Ryzen 1600 with a rx480 16 gb ram, Windows 10

See https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory