LODGenx64.exe failed to generate object LOD for one or more worlds

[nolbear]

Hello again, I'm trying to use DynDOLOD 3.00 (Alpha 14) to generate LOD for my game and I keep running into this error: "LODGenx64.exe failed to generate object LOD for one or more worlds." It seems to run into the error when trying to generate object LOD for the Tamriel worldspace. I've searched all over but can't find anyone else who has encountered this error. Any ideas what might be causing the problem? Here's a picture of the error message. Please let me know if you have any ideas. Thanks!

[m1sf1t711]

Hi again Sheson

I needed to rerun DynDOLOD and I am suddenly running into this error and can't see any error messages in the logs. 

 

Error: LODGenx64Win.exe failed to generate object LOD for one or more worlds. Check for error messages in the listed LODGen log(s)
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel AUT. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_AUT_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel SUM. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_SUM_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel WIN. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_WIN_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_log.txt

Here's a link to my logs:

https://drive.google.com/file/d/1ik1O1lEBecszryMQXyIP14PTeShoPdGK/view?usp=sharing

I suspect it will be something on my PC causing a problem. I've tried reinstalling .NET Desktop Runtime 6 just in case and tried generating LOD in expert mode for just the affected world spaces but had the same problem. I've attached logs of my latest attempt to run DynDOLOD for all world spaces. I always run in expert mode so I can put in the rules for A Clear World Map, ERM and Happy Little Trees.

[sheson]

22 minutes ago, m1sf1t711 said:

Hi again Sheson

I needed to rerun DynDOLOD and I am suddenly running into this error and can't see any error messages in the logs. 

 

Error: LODGenx64Win.exe failed to generate object LOD for one or more worlds. Check for error messages in the listed LODGen log(s)
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel AUT. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_AUT_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel SUM. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_SUM_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel WIN. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_WIN_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_log.txt

Here's a link to my logs:

https://drive.google.com/file/d/1ik1O1lEBecszryMQXyIP14PTeShoPdGK/view?usp=sharing

I suspect it will be something on my PC causing a problem. I've tried reinstalling .NET Desktop Runtime 6 just in case and tried generating LOD in expert mode for just the affected world spaces but had the same problem. I've attached logs of my latest attempt to run DynDOLOD for all world spaces. I always run in expert mode so I can put in the rules for A Clear World Map, ERM and Happy Little Trees.

See https://dyndolod.info/Help/LODGen:
C0000005/80131506 - If happening randomly can be a sign of hardware issues like CPU or memory being unstable.
Reduce memory requirements. See Out of Memory below. See FAQ High Memory Usage / Out of Memory.

Expert mode does not change being able to add or change rules in advanced mode already. See https://dyndolod.info/Help/Expert-Mode

[m1sf1t711]

8 hours ago, sheson said:

See https://dyndolod.info/Help/LODGen:
C0000005/80131506 - If happening randomly can be a sign of hardware issues like CPU or memory being unstable.
Reduce memory requirements. See Out of Memory below. See FAQ High Memory Usage / Out of Memory.

Expert mode does not change being able to add or change rules in advanced mode already. See https://dyndolod.info/Help/Expert-Mode

Hi

I've had a go at following all the advice given but I'm still having the same problem and noticed this error message as well so I tried the ini change for occlusion not generating:

<Error: Occlusion generation aborted due to LODGen error>
 

Here's a link to my latest logs: https://drive.google.com/file/d/1gLyHh4cYNPubAtV7dvXJSQAfSXJF6HCi/view?usp=sharing

 

And also a link to a copy of my DynDOLOD_SSE.ini so you can see what changes I tried: https://drive.google.com/file/d/1nnSqISDbBIw8oKkyjU-8b0ddmqqHZ0es/view?usp=sharing

 

I previously ran DynDOLOD successfully using all the same settings within the start up window as I am using now. 

I have also regenerated xLODGen using the latest 127 version in case that had any impact.

 

I'm very out of my depth knowing the best values to try in the ini so any advice would be appreciated. I've also done a health check on my cpu and memory and they don't appear to be a problem. I only purchased this pc in the summer and I have an AMD Ryzen 7 7800X3D 8-Core processor and 21.9GB available RAM

 

Thank you so much for your help and for DynDOLOD itself.

[sheson]

58 minutes ago, m1sf1t711 said:

Hi

I've had a go at following all the advice given but I'm still having the same problem and noticed this error message as well so I tried the ini change for occlusion not generating:

<Error: Occlusion generation aborted due to LODGen error>
 

Here's a link to my latest logs: https://drive.google.com/file/d/1gLyHh4cYNPubAtV7dvXJSQAfSXJF6HCi/view?usp=sharing

 

And also a link to a copy of my DynDOLOD_SSE.ini so you can see what changes I tried: https://drive.google.com/file/d/1nnSqISDbBIw8oKkyjU-8b0ddmqqHZ0es/view?usp=sharing

 

I previously ran DynDOLOD successfully using all the same settings within the start up window as I am using now. 

I have also regenerated xLODGen using the latest 127 version in case that had any impact.

 

I'm very out of my depth knowing the best values to try in the ini so any advice would be appreciated. I've also done a health check on my cpu and memory and they don't appear to be a problem. I only purchased this pc in the summer and I have an AMD Ryzen 7 7800X3D 8-Core processor and 21.9GB available RAM

 

Thank you so much for your help and for DynDOLOD itself.

Since occlusion can not be generated when object LOD meshes generation fails, there are no out of memory message while generating occlusion and changing the OcclusionMaxThreadsObjectLOD setting is irrelevant. It does not change anything about LODGen.

The INI setting are already documented in the DynDOLOD_SSE_debug_log.txt, there is not need to upload DynDOLOD_SSE.ini.

Sounds like high memory usage is not the cause. Check the Windows Event log for related messages.
Stress testing the system with tools overlockers use, like xorecycler using prime95, ycruncher or occt etc. could be useful.
21.9GB is an odd number for main memory. It should be closer to a power of 2 number, since you typically have 2 or 4 memory modules a 8GB, 16GB etc.

Test if using the Framework version LODGenx64.exe works better by hiding the ..\DynDOLOD\Edit Scripts\LODGenx64Win.exe.
Just use expert mode and Execute LODGen for the worldspaces and seasons that failed.

[m1sf1t711]

52 minutes ago, sheson said:

Since occlusion can not be generated when object LOD meshes generation fails, there are no out of memory message while generating occlusion and changing the OcclusionMaxThreadsObjectLOD setting is irrelevant. It does not change anything about LODGen.

The INI setting are already documented in the DynDOLOD_SSE_debug_log.txt, there is not need to upload DynDOLOD_SSE.ini.

Sounds like high memory usage is not the cause. Check the Windows Event log for related messages.
Stress testing the system with tools overlockers use, like xorecycler using prime95, ycruncher or occt etc. could be useful.
21.9GB is an odd number for main memory. It should be closer to a power of 2 number, since you typically have 2 or 4 memory modules a 8GB, 16GB etc.

Test if using the Framework version LODGenx64.exe works better by hiding the ..\DynDOLOD\Edit Scripts\LODGenx64Win.exe.
Just use expert mode and Execute LODGen for the worldspaces and seasons that failed.

 

Thank you

 

I tried generating just Tamriel Seasons and it failed again:

Error: LODGenx64Win.exe failed to generate object LOD for one or more worlds. Check for error messages in the listed LODGen log(s)
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel AUT. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_AUT_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel SPR. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_SPR_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel SUM. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_SUM_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel WIN. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_WIN_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_log.txt

 

I've had a look in the Windows Event Log and these are the reports for this attempt:

 

https://docs.google.com/document/d/1dvUqsUPrqXy7oEcPL8ju1w90fCUPuE_SHlc0KomJKqo/edit?usp=sharing

 

Does that help at all? I'm not technical enough to really know what they are telling me, sorry :/

 

Sorry I also wasn't sure how to hide  ..\DynDOLOD\Edit Scripts\LODGenx64Win.exe. so I haven't tried that yet. Do I just tick hidden in properties?

Edited October 21, 2024 by m1sf1t711

[sheson]

2 hours ago, m1sf1t711 said:

 

Thank you

 

I tried generating just Tamriel Seasons and it failed again:

Error: LODGenx64Win.exe failed to generate object LOD for one or more worlds. Check for error messages in the listed LODGen log(s)
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel AUT. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_AUT_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel SPR. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_SPR_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel SUM. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_SUM_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel WIN. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_WIN_log.txt
Error: LODGenx64Win.exe failed to generate object LOD for Tamriel. LODGenx64Win.exe returned C0000005. Check C:\DynDOLOD\Logs\LODGen_SSE_Tamriel_log.txt

 

I've had a look in the Windows Event Log and these are the reports for this attempt:

 

https://docs.google.com/document/d/1dvUqsUPrqXy7oEcPL8ju1w90fCUPuE_SHlc0KomJKqo/edit?usp=sharing

 

Does that help at all? I'm not technical enough to really know what they are telling me, sorry :/

 

Sorry I also wasn't sure how to hide  ..\DynDOLOD\Edit Scripts\LODGenx64Win.exe. so I haven't tried that yet. Do I just tick hidden in properties?

By hiding I mean something like moving it out of the folder or renaming it to LODGenx64Win.bak for example.

Make sure antivir is not interfering by temporality disabling or adding exceptions.
Reinstall or repair .NET6

If neither works, upload the files mentioned from the last event log entry, e.g.
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b742fef1-151c-4b46-8353-6e3f9a08266a.tmp.dmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0820b4dd-3d78-4c5a-b818-0e6721cbf5f0.tmp.WERInternalMetadata.xml
etc.

[m1sf1t711]

21 hours ago, sheson said:

By hiding I mean something like moving it out of the folder or renaming it to LODGenx64Win.bak for example.

Make sure antivir is not interfering by temporality disabling or adding exceptions.
Reinstall or repair .NET6

If neither works, upload the files mentioned from the last event log entry, e.g.
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b742fef1-151c-4b46-8353-6e3f9a08266a.tmp.dmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0820b4dd-3d78-4c5a-b818-0e6721cbf5f0.tmp.WERInternalMetadata.xml
etc.

Hi

Apologies for the slow retest but sleep and work rudely interrupted my modding endeavours lol

 

The attached zip includes a copy/paste of the error logs for my attempt this evening, having followed all the instructions above first. I've also attached the two Windows Report logs which I think was what you wanted. Let me know if I've misunderstood that part and you need anything else.

 

And again thank you so much for your help. Your generosity with your time is really appreciated.

 

Logs.7z

[sheson]

26 minutes ago, m1sf1t711 said:

Hi

Apologies for the slow retest but sleep and work rudely interrupted my modding endeavours lol

 

The attached zip includes a copy/paste of the error logs for my attempt this evening, having followed all the instructions above first. I've also attached the two Windows Report logs which I think was what you wanted. Let me know if I've misunderstood that part and you need anything else.

 

And again thank you so much for your help. Your generosity with your time is really appreciated.

 

Logs.7z 37.49 kB · 1 download

Can you check/upload whatever files you have in C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LODGenx64.exe_3e45a4a6ec721ab9b0cf8eeec45b859ad46d875f_dccf8104_1e33ab8d-94fe-4a05-ba29-d611e7a20939
or here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LODGenx64.exe_3e45a4a6ec721ab9b0cf8eeec45b859ad46d875f_dccf8104_d2f3d1fc-8356-4a4a-9082-6fc9c1dd1b74

Especially files ending in *.dmp
Might be here: 
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f8f9708a-1428-4aa2-b32e-e61c619ff101.tmp.dmp
or here:
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b6d9ab25-2747-482b-8c01-2bd34348a1a1.tmp.dmp

Did you do change any settings about virtual memory/page file?

[m1sf1t711]

3 minutes ago, sheson said:

Can you check/upload whatever files you have in C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LODGenx64.exe_3e45a4a6ec721ab9b0cf8eeec45b859ad46d875f_dccf8104_1e33ab8d-94fe-4a05-ba29-d611e7a20939
or here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LODGenx64.exe_3e45a4a6ec721ab9b0cf8eeec45b859ad46d875f_dccf8104_d2f3d1fc-8356-4a4a-9082-6fc9c1dd1b74

Especially files ending in *.dmp
Might be here: 
 C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f8f9708a-1428-4aa2-b32e-e61c619ff101.tmp.dmp
or here:
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b6d9ab25-2747-482b-8c01-2bd34348a1a1.tmp.dmp

Hi

 

In the first two locations I only have the .wer files which I sent.

I can't find the other files at all. In the Temp folder I only have the two files attached.

files.7z

[sheson]

1 hour ago, m1sf1t711 said:

Hi

 

In the first two locations I only have the .wer files which I sent.

I can't find the other files at all. In the Temp folder I only have the two files attached.

files.7z 207 B · 1 download

Did you do change any settings about virtual memory/page file?

Create a new registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps to enable minidumps.
https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps

No need to add any of the settings, the defaults should suffice. Then reproduce the crash and hopefully find the file to upload in %LOCALAPPDATA%\CrashDumps

[m1sf1t711]

1 hour ago, sheson said:

Did you do change any settings about virtual memory/page file?

Create a new registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps to enable minidumps.
https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps

No need to add any of the settings, the defaults should suffice. Then reproduce the crash and hopefully find the file to upload in %LOCALAPPDATA%\CrashDumps

 

Hi

 

"Did you do change any settings about virtual memory/page file?" - No I wouldn't know how to lol

So I think I set up the registry keys correctly (never done that before) and here's a link to the logs that I found in %LOCALAPPDATA%\CrashDumps after reproducing the crash.

https://drive.google.com/file/d/1v_Y69za19KwIXW73kyiVPURB3BXHGAYC/view?usp=sharing

[sheson]

8 hours ago, m1sf1t711 said:

Hi

"Did you do change any settings about virtual memory/page file?" - No I wouldn't know how to lol

So I think I set up the registry keys correctly (never done that before) and here's a link to the logs that I found in %LOCALAPPDATA%\CrashDumps after reproducing the crash.

https://drive.google.com/file/d/1v_Y69za19KwIXW73kyiVPURB3BXHGAYC/view?usp=sharing

So far so good. Delete all old dmp.
Replace LODGenx64.exe in Edit Scripts with this version https://mega.nz/file/wMhQkbYK#txe4unb3FlDtjlAaaIoVuOUohMoGqUNNA6oH4AABulY
Start DynDOLOD in expert mode and Execute LODGen for whatever worldspace and season with the problem.
Upload new dmp file(s). 

[m1sf1t711]

CrashDump2.7z

1 hour ago, sheson said:

So far so good. Delete all old dmp.
Replace LODGenx64.exe in Edit Scripts with this version https://mega.nz/file/wMhQkbYK#txe4unb3FlDtjlAaaIoVuOUohMoGqUNNA6oH4AABulY
Start DynDOLOD in expert mode and Execute LODGen for whatever worldspace and season with the problem.
Upload new dmp file(s). 

Thanks

Just tried that but DynDOLOD wouldn't start and I got error code E0434352

 

I still have LODGENx64Win hidden. Should I have put that back?

I have run the repair tool again for .NET Desktop Runtime 6 but a second attempt had the same result. I've attached the CrashDump files

CrashDump2.7z

[sheson]

35 minutes ago, m1sf1t711 said:

CrashDump2.7z 1.78 MB · 1 download

Thanks

Just tried that but DynDOLOD wouldn't start and I got error code E0434352

 

I still have LODGENx64Win hidden. Should I have put that back?

I have run the repair tool again for .NET Desktop Runtime 6 but a second attempt had the same result. I've attached the CrashDump files

CrashDump2.7z 1.78 MB · 1 download

Leave LODGenx64Win.exe hidden. We will continue with the Framework 4.8 version.

If you like you can try updating/uninstalling/reinstalling/repairing the latest Framework version.

On a windows command prompt you can try running
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update /force

You can also try a sfc /scannow https://support.microsoft.com/en-us/windows/using-system-file-checker-in-windows-365e0031-36b1-6031-f804-8fd86e0ef4ca

Reboot after each.
I doubt though that this is going to make a difference, since both Framework and .NET have the crash that is typically cause by CPU/memory issues.

 

I have another test version. Replace the LODGenx64.exe with the one in this archive https://mega.nz/file/4RIzHSQZ#aTjH9RtZRcigS_RxmE3ZNbkglSvj6dIVmE1bhJRILPs
Also put the same LODGenx64.pdb next to it.
Delete old dmp files, and Execute LODGen in expert mode for a single worldspace and season so it only starts one processes. Upload dmp file(s).

[m1sf1t711]

15 minutes ago, sheson said:

Leave LODGenx64Win.exe hidden. We will continue with the Framework 4.8 version.

If you like you can try updating/uninstalling/reinstalling/repairing the latest Framework version.

On a windows command prompt you can try running
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update /force

You can also try a sfc /scannow https://support.microsoft.com/en-us/windows/using-system-file-checker-in-windows-365e0031-36b1-6031-f804-8fd86e0ef4ca

Reboot after each.
I doubt though that this is going to make a difference, since both Framework and .NET have the crash that is typically cause by CPU/memory issues.

 

I have another test version. Replace the LODGenx64.exe with the one in this archive https://mega.nz/file/4RIzHSQZ#aTjH9RtZRcigS_RxmE3ZNbkglSvj6dIVmE1bhJRILPs
Also put the same LODGenx64.pdb next to it.
Delete old dmp files, and Execute LODGen in expert mode for a single worldspace and season so it only starts one processes. Upload dmp file(s).

Windows Defender is blocking the download saying a virus has been detected?