Out of memory error every run.

[Pawelekdabek]

Hi, 

 

For several days I have been trying to deal with the out of memory error when generating LOD using DynDOLODx64.

I was using S.T.E.P guide to mod my Skyrim and I was able to generate LOD files only once. I noticed that all the mods take up too much space on my system disk and decided to change the paths to another disk. I coppied files, played skyrim for a while and then started modifying skyrimprefs.ini. and I found this tutorial on the internet: 'tutorial' and in this tutorial this is mentioned: "If you set uLargeRefLODGridSize = 11 do this: in DynDOLOD_SSE.ini in line IgnoreLargeReferences = change from a 0 to a 1 then just save the file."

I thought that i have to regenerate LOD files and i did this but faced out of memory error. I reverted this setting and tried to generate LODs again but from now on I get this error every time. (i disabled DynDOLOD Output on my modlist before regenerating and deleted files from that mod folder).

 

I thought maybe the files were copied wrong and hence such an error appears but I downloaded all the mods again, cleaned the game folder and checked them using Steam, then I did everything step by step as in the S.T.E.P guide and the same error still appears.

 

But I noticed a few things.

1. If DynDOLOD is on the same disc as the game and mods then this error pops up soonest(Log attached).
2. If DynDOLOD is on the HDD then the error pops up a little later.
3. However, if DynDOLOD is on the SSD disk and the mods folder on the C drive in appdata then the error pops up when generating DLC2SolstheimWorld (so further than other two options).

[(A: Games(sdd), B: Data(hdd) C: System(ssd)]

 

I have all exes from DynDOLOD added to exceptions in Windwows Defender

I have pagefile for every disc set to min: 1,5*RAM max: 2*RAM

i checked all plugins with SSEdit and they do not have any errors.

All files are up to date.

 

Pastebin:

Bugreport: https://pastebin.com/j3seafSy

Log: https://pastebin.com/GyKFC3ub

 

Hope you will help me cause it starts to drive me crazy.

[sheson]

Ignore third party instructions and read manual included in the download archive.

It makes no sense to tell DynDOLOD to ignore large references if they are enabled in the game.

 

Leave Windows page file settings default.

 

Close other programs and background processes.

 

The bug report shows there is only 1052/8127 MB (free/total)

 

Do large worldspace one at a time. Install output with plugins after each generation and enable the plugins so they are loaded/updated for later runs. Overwrite older output with newer output.

Edited March 17, 2020 by sheson

[Pawelekdabek]

This was clean installation and as i mentioned, i followed S.T.E.P guide. I set page file setting to default,  restarted windows and output is almost the same. This time Acces Violation while generating Solstheim because mods files are on system disc.

 

Log: https://pastebin.com/iWuTLgBB

System menager before LOD generation: https://imgur.com/ZTwTJFU

 

While generating LOD files memory usage is floating around 90% with spikes to 95%.

 

i will try generating it world after world.

 

EDIT:

 

I tried running only Tamriel and still out of memory.

https://imgur.com/5B6iazS

 

LOD generation CMD is still running in the background but DynDOLOD is stuck and will not show message to close and save files.

Edited March 17, 2020 by Pawelekdabek

[sheson]

This time Acces Violation while generating Solstheim because mods files are on system disc.

 

It should not matter on what disc mods are.

 

If DynDOLOD stops with an error, you can close the LODGen command prompt window it spawned. The generated LOD/plugins are not usable.

 

No point in posting screenshots of logs that exist in text form.

 

It is possible it is trying to update a base record added or overwritten by a plugin that has issues.

 

Set Debug=1 in DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini so it prints messages which base record is working on. Then check the last one mentioned before the error.

 

Otherwise, if the system runs out of memory there is nothing the program can do about it. You could try running the x86 version.

[Pawelekdabek]

I ran generation on Windows in safe mode and it finished without any errors. Do you have any idea why it is not working in normal mode?

[Pawelekdabek]

Could you also tell me if changing my Skyrim.ini and Skyrimprefs.ini affects LOD generation? Like if i change uLargeRefLODGridSize = 11 to 7 or 21 do I have to generate LOD files once more?

 

Sorry about another post, i could not edit previous one.

Edited March 17, 2020 by Pawelekdabek

[sheson]

I ran generation on Windows in safe mode and it finished without any errors. Do you have any idea why it is not working in normal mode?

Could be hardware/drivers or service/background things which are now not used or running.

 

INI settings do not change LOD generation.

 

The only result using such insane INI settings will be performance and probably stability issues. 

[Pawelekdabek]

It is really weird, I did clean install not long ago, drivers are up to date. Could you tell me what can I do to check what is wrong with my PC? I do not have any problems while gaming so I do not think it is hardware issue.

 

I will stick to uLargeRefLODGridSize = 11

Edited March 17, 2020 by Pawelekdabek

[sheson]

That's outside the scope of the free DynDOLOD/xLODGen support.

 

I would try to take a close look at what isn't loaded/active when in save mode.

[Pawelekdabek]

Okay, thank you for your time and help ;)

[Pawelekdabek]

Update. 

 

I tried driver booster and i had 7 or 8 intel drivers to update. I think they were discs related.

 

After update i was able to succesfully generate LOD files on normal mode.

Edited March 17, 2020 by Pawelekdabek