Jump to content
  • 0

Exception in unit process line 87


Question

Posted

Hello there! I'm currently following Lexy's LOTD Mod List and I'm now near the end trying to get DynDOLOD to work.

 

The first 5 times or so I tried running it I kept getting an error that said something like "Exception in unit process line 87: Access violation at address 000000000041580e"

 

I had to delete the logs because there was too much text to fit inside a pastebin. After deleting them I tried running it one more time and now it's coming up with "Exception in unit process line 87: Invalid pointer operation".

 

It always stops working around the 8 minute mark, with Solstheim I believe. The task manager also shows it uses almost 100% of my RAM.

 

Here are the latest logs:

 

DynDOLOD_SSE_log: https://pastebin.com/6y2AKEP9

 

bugreport: https://pastebin.com/6hzu8ETH

 

 

4 answers to this question

Recommended Posts

  • 0
Posted

The bugreport says it is running out of memory.

 

Pay attention to the instructions of the included manual and what it says under the Output folder selection on DynDOLODs Wizard options window. The output path should be outside of the game folders and Mod Organizers virtual file structure. Do not use a path in MO2 mod folders.

 

Close as many programs and background processes as possible to free up memory.

 

Let Windows handle virtual memory/page file.

 

Use lower texture size settings for TexGen/DynDOLOD

 

Generate LOD for Solstheim only to see if it runs through. If successful, install and activate output as usual. Then start DynDOLOD again, with the DynDOLOD plugins. Select the other worldspaces and generate LOD. Then install the new output, overwriting output from the first run.

  • 0
Posted

Looks like letting Windows handle the page file and generating the LOD for select worldspaces at a time did the trick. Thank you for your help!

  • 0
Posted

same issue

Exception in unit process line 87: Can not copy DragonMoundDirtCapSnow [STAT:00068E68] from BetterDynamicSnow_PATCH.esp into DynDOLOD.esp Load order FileID [FE 017] can not be mapped to file FileID for file "DynDOLOD.esp"

 

bugreport.txt

  • 0
Posted
1 hour ago, Dreifels said:

same issue

Exception in unit process line 87: Can not copy DragonMoundDirtCapSnow [STAT:00068E68] from BetterDynamicSnow_PATCH.esp into DynDOLOD.esp Load order FileID [FE 017] can not be mapped to file FileID for file "DynDOLOD.esp"

 

bugreport.txt 45.94 kB · 0 downloads

Op error message:
Exception in unit process line 87: Invalid pointer operation

Your error message:
Exception in unit process line 87: Can not copy DragonMoundDirtCapSnow [STAT:00068E68] from BetterDynamicSnow_PATCH.esp into DynDOLOD.esp Load order FileID [FE 017] can not be mapped to file FileID for file "DynDOLOD.esp"

It is a different issue.

Read all log message and follow their advice.

Checking the docs/DynDOLOD-FAQ.txt
Q: DynDOLOD.exe: Can not copy xxxx from xxxx.esp into xxx.esp
A: Often caused by a broken bashed patch. Use a newer Wrye Bash version to create the patch or do not use the merge patches option.
A: There is a plugin in the load order with errors. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help.

Search the forum for similar error message:
https://stepmodifications.org/forum/topic/15739-can-not-copy-x-from-x-error/#comment-247758

If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.