DynDOLOD is being terminated prematurely, suddenly closes

[VulKun]

I can use 2.98 but i cant use 3 alphax. Still doesnt work for me. Just closing itself and there is no bugreport or something. I tried everything but nothing change 

[Crim]

2 minutes ago, sheson said:

Check if the Windows Event log shows the same error. If prime95 did not have errors, run OCCT next. 

Even for the real time log this seems incredible slow. Do you have an AMD GPU with crapware installed?
It is still just in the base record building process where it checks base records and scans/matches used meshes and textures.
A real time anti virus check might slow down file access, too.  Adding exceptions might help.
A lot of large textures might add to it, too.

What is the total amount of physical main memory? Is page file / virtual memory set to defaults handled by OS?
You may want to close the browser and other unneeded processes.
Do a memory test.

Unrelated, you should fix the HITMEs in Redwater Castle.esp  

I don't have an AMD GPU, no. Didn't knew the term 'crapware' until now.
There is defitely some large and custom textures here and there, but I was pretty selective to not take more than 2k 95% of the time, except for some armours.
I will test it without any other process active next time.
I excluded the DynDOLOD folder from my antivirus.

I will test it without any other process active next time.
I will test my RAM

Can you expand on "What is the total amount of physical main memory? Is page file / virtual memory set to defaults handled by OS?" ? Im not 100% sure of what you mean by that

[sheson]

1 minute ago, Crim said:

I don't have an AMD GPU, no. Didn't knew the term 'crapware' until now.
There is defitely some large and custom textures here and there, but I was pretty selective to not take more than 2k 95% of the time, except for some armours.
I will test it without any other process active next time.
I excluded the DynDOLOD folder from my antivirus.

I will test it without any other process active next time.
I will test my RAM

Can you expand on "What is the total amount of physical main memory? Is page file / virtual memory set to defaults handled by OS?" ? Im not 100% sure of what you mean by that

I mean how much RAM is installed? 8GB, 16GB?

If you do not know about virtual memory and page file setting, then you probably did not change the default settings.
https://duckduckgo.com/?q=windows+virtual+memory+settings

[Crim]

16GB then, it's less about me not knowing than me being bad at english translation, sorry ^^

Here the results of my last attempt (Windows and crashlog). 

I did everything you asked, but the problem seems to persist

[sheson]

10 hours ago, Crim said:

16GB then, it's less about me not knowing than me being bad at english translation, sorry ^^

Here the results of my last attempt (Windows and crashlog). 

I did everything you asked, but the problem seems to persist

How much free main memory is there available before starting DynDOLOD?
What kind of disk is the drive F:?
Can you test what happens if you change affinity in task manager to only use half the CPU cores?

[Crim]

2 hours ago, sheson said:

How much free main memory is there available before starting DynDOLOD?
What kind of disk is the drive F:?
Can you test what happens if you change affinity in task manager to only use half the CPU cores?

10 to 12+ Go of available memory
Drive F is an SSD Nvme disk
I just tested it, nothing change from my perspective but the logs are here

[sheson]

2 hours ago, Crim said:

10 to 12+ Go of available memory
Drive F is an SSD Nvme disk
I just tested it, nothing change from my perspective but the logs are here

The tool is just being killed while checking if a meshes exist, loading them to see what textures it usess etc.
It really runs about an hour before crashing? If you disable the realtime log, it happens within minutes?

TexGen ran without issues? Can you upload its log and debug log for comparision?

[Crim]

 

54 minutes ago, sheson said:

The tool is just being killed while checking if a meshes exist, loading them to see what textures it usess etc.
It really runs about an hour before crashing? If you disable the realtime log, it happens within minutes?

TexGen ran without issues? Can you upload its log and debug log for comparision?

No, it does not run an hour before crashing most of the time, but that's the thing I don't really understand, it's that sometimes it crash at 2 to 4 minutes, and two times it dit at 50+ minutes now, without me really changing anything between tests, realtime log did not change that, it's just that coincidentally, I activated just before one of the longest run with the tool.
The next runs it ccrashed after a few minutes like most of the times 
 

Texgen seems to run without issue, at least from my perspective, here.

[sheson]

5 hours ago, Crim said:

 

No, it does not run an hour before crashing most of the time, but that's the thing I don't really understand, it's that sometimes it crash at 2 to 4 minutes, and two times it dit at 50+ minutes now, without me really changing anything between tests, realtime log did not change that, it's just that coincidentally, I activated just before one of the longest run with the tool.
The next runs it ccrashed after a few minutes like most of the times 
 

Texgen seems to run without issue, at least from my perspective, here.

Can you load the entire load order into with xEdit 4.1.5m (#xedit-builds channel on the xEdit discord) and do an error check across all non game/DLC plugins?
Upload that xEdit log.

[Crim]

13 hours ago, sheson said:

Can you load the entire load order into with xEdit 4.1.5m (#xedit-builds channel on the xEdit discord) and do an error check across all non game/DLC plugins?
Upload that xEdit log.

I will do that asap

13 hours ago, sheson said:

Can you load the entire load order into with xEdit 4.1.5m (#xedit-builds channel on the xEdit discord) and do an error check across all non game/DLC plugins?
Upload that xEdit log.

Turns out, SSEdit crashed on me while loading the plugins. I can imagine for the same reasons as DynDOLOD

I will try one or two things tomorrow, It might be a strange error due to me changing my CPU (who works fine except for DynDOILOD and SSEdit) but maybe it's the plugins afterall, even though, the modlist work extremly fine ingame (well, except for the LOD oc).

Could you send me a link to the previous Ressources file + Dyndolod 3.0 185 without the blocker ? I did successfully make my LOD with these, and I want to try to see if it's me adding new mods that created this problem or changing my CPU, if not, I will try again a bit but I'm starting to be frustrated lol  

[sheson]

12 hours ago, Crim said:

I will do that asap

Turns out, SSEdit crashed on me while loading the plugins. I can imagine for the same reasons as DynDOLOD

I will try one or two things tomorrow, It might be a strange error due to me changing my CPU (who works fine except for DynDOILOD and SSEdit) but maybe it's the plugins afterall, even though, the modlist work extremly fine ingame (well, except for the LOD oc).

Could you send me a link to the previous Ressources file + Dyndolod 3.0 185 without the blocker ? I did successfully make my LOD with these, and I want to try to see if it's me adding new mods that created this problem or changing my CPU, if not, I will try again a bit but I'm starting to be frustrated lol  

You probably have a plugin that contains a problem or error that causes xEdit to crash.

If the paying attention to the log inclusive. do a binary search  to find out which.
1. Only load about half the plugins.
2. Do the check.
3. If there is no problem load the other half. If there is the problem, repeat from step 1 for these plugins.
4. repat until one plugin remains.

[Crim]

Quote

 

[Window Title]
DynDOLOD

[Main Instruction]
Access violation at address 0000000001603189 in module 'DynDOLODx64.exe' (offset FF3189).

[Content]
Read of address 0000000000000000 while processing Olenveld.esp [REFR:1F3A6E8C] (Places OlenDLC1IcebergLarge_1LayerNOSN [STAT:1F3A7390] in [CELL:1F3A6C19] (in OlenIceWorld "Olenveld Underworld" [WRLD:1F3A6BFE] at 0,1))

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

 

While doing test runs to identify the culprit of my DynDOLOD crash crash, Ive got this error message.

Here the log and bug report 

[Crim]

Alright, I found that the plugin making DynDOLOD AND Xedit crash was 'Orc Strongholds - Largashbur', it was a pain to find.

I suggest to everyone having the same problem as mine in the futur to try to test without this plugin, and see what happen.

[sheson]

1 hour ago, Crim said:

Alright, I found that the plugin making DynDOLOD AND Xedit crash was 'Orc Strongholds - Largashbur', it was a pain to find.

I suggest to everyone having the same problem as mine in the futur to try to test without this plugin, and see what happen.

What version of Orc Strongholds - Largashbur.esp are you using? 

There seems to be no problem with the plugin from 2.1.3. The logs you uploaded reported a different CRC32, so you are using a different version.

[Crim]

3 hours ago, sheson said:

What version of Orc Strongholds - Largashbur.esp are you using? 

There seems to be no problem with the plugin from 2.1.3. The logs you uploaded reported a different CRC32, so you are using a different version.

Nop, i was using the latest, just checked. I used a patch though for EFPS 

[sheson]

6 minutes ago, Crim said:

Nop, i was using the latest, just checked. I used a patch though for EFPS 

In that case please report exactly the entire filename of the plugin that causes the problem and where to acquire it. Or upload it.