Exception in unit userscript line 331: Access violation at address 004B4A55

[sb187]

   This is more a follow up post then a unsolved bug report. I tried running DynDOLOD last night and keep getting a recurring error:

 

"Exception in unit userscript line 331: Access violation at address 004B4A55 in module 'DynDOLOD.exe'. Write of address 00000000"

 

   I'm on LE, MO1, Bashed Patched disabled and Archive Management Disabled as well. I tried restarting pc but error still occurred. Googling and seaching the forums here, I found a few posts mentioning antivirus issues, so I double checked and added exceptions to all the exe's in the dyndolod folder and edit scripts folder. Error still occurred. My Skyrim is installed outside the C drive x86 folders, on a seperate SSD, using the latest DynDOLOD exe, Resources and DynDOLOD Patch 2.45 for Beyond Reach. I run ~1400 active mods with ~700 esps, merged down to around ~235, give or take. I tested this with a few of the larger land mods I had installed removed and still had the error. The only variation I had in the program failure was sometimes the error would only be: "Exception in unit userscript line 331", without the rest of the access violation part.

 

   I finally came on a post made by you that mentions possible out of memory issues, and to try running the x64 bit version. So I downloaded the latest version of MO2 from SE nexus, and installed it to the same place as my MO1, which is the Skyrim Folder itself along with all my other tools/programs. I followed your instructions about modifying the file directories of MO2 to point to the same ones in MO1, worked just fine. I then ran the x64 bit version of TexGen and DynDOLOD and it worked just fine, no program failure. I'll post the BugReport.txt along with my DynDOLOD_TES5_log.txt, which has the logs starting form last night with all the errors. Roughly 6-10 attempts, ending with the x64 bit successful generation. If you have any questions or would like to see anything else, please let me know, and if you prefer some faster responses, I'm in the Xedit discord.  

 

 

bugreport.txt

Edited April 10, 2019 by sb187

[sb187]

Seems my DynDOLOD_TES5_log is too long for both pastebin and attaching here, 2.55mb. so I'll trim out the older failures and just leave the last one before the successful x64 generation. I'll have a copy with the rest of them saved in case you are interested. DynDOLOD_TES5_Log: https://pastebin.com/JDsmGYaB

Edited April 10, 2019 by sb187

[sheson]

I am not even sure how there is anyone still left with MO1 / x86 version anyways :)

 

Did you increase the texture sizes in TexGen or the Max Tile Sizei in DynDOLOD?  

 

I suppose the error message could be more descriptive.

Edited April 10, 2019 by sheson

[sb187]

Yes, lol. I'll be switching to MO2 soon enough. BSA conflict detection and management keeps me using it for now. Texture size in TexGen was the default 512, and Tile size of DynDOLOD was 512 as well. I've been using the same settings for a long time now, across numerous DynDOLOD updates. I'll attach a screenshot of the settings. Only thing I change from time to time is the LOD brightness setting.

Edited April 10, 2019 by sb187