Schlongs of Skyrim throwing EXCEPTION_ACCESS_VIOLATION and CTD.

[Sabre013]

When loading a save I get a CTD and attached is the crash log. I ma not great at reading them, so any assistance on what I can do to fix this would be greatly appreciated. Thank you. 

crash-2023-07-05-13-55-55.log

[Sabre013]

Found a solution and putting it here for anyone in future having the issue. Originally from u/Gazibaldi on reddit. 

 

"The issue is with Schlongs of Skyrim. It says so in the error log.

>Unhandled native exception occurred at 0x7FFFBC7BF1F9 (SchlongsOfSkyrim.dll+F1F9) on thread 14820!

The DLL can be very temperamental with load order changes.

To fix it do the following:

-Arrange your load order how you want it.

-Disable the schlongs of Skyrim dll within data\skse\plugins (rename it or hide it in mo2 is fine). Just the DLL not the mod.

-Load your save. It will moan about schlongs version mismatch. This is to be expected.

-Save your game. New save file to be safe

-Close game

-Re-enable the schlongs DLL

-Reload your save and wait for schlongs to re-register.

-From schlongs MCM choose Restart Schlongs of Skyrim

-Wait till that is done.

-Save game and reload game

-Wait for schlongs first time initialisation message.

-In schlongs MCM reimport your settings. This has to be done after the save/reload or it doesn't import properly

-Save your game

-Done

You might find this happens whenever you add something at a lower priority than the schlongs esp or adding a bunch of new esps. Just follow the above each time it blows up."

This does not work on older saves, you would have to repeat the process for them. However, once fixed you should be good to go going forward. 

[SarahKawaii2]

On 7/5/2023 at 6:37 PM, Sabre013 said:

Found a solution and putting it here for anyone in future having the issue. Originally from u/Gazibaldi on reddit. 

 

"The issue is with Schlongs of Skyrim. It says so in the error log.

>Unhandled native exception occurred at 0x7FFFBC7BF1F9 (SchlongsOfSkyrim.dll+F1F9) on thread 14820!

The DLL can be very temperamental with load order changes.

To fix it do the following:

-Arrange your load order how you want it.

-Disable the schlongs of Skyrim dll within data\skse\plugins (rename it or hide it in mo2 is fine). Just the DLL not the mod.

-Load your save. It will moan about schlongs version mismatch. This is to be expected.

-Save your game. New save file to be safe

-Close game

-Re-enable the schlongs DLL

-Reload your save and wait for schlongs to re-register.

-From schlongs MCM choose Restart Schlongs of Skyrim

-Wait till that is done.

-Save game and reload game

-Wait for schlongs first time initialisation message.

-In schlongs MCM reimport your settings. This has to be done after the save/reload or it doesn't import properly

-Save your game

-Done

You might find this happens whenever you add something at a lower priority than the schlongs esp or adding a bunch of new esps. Just follow the above each time it blows up."

This does not work on older saves, you would have to repeat the process for them. However, once fixed you should be good to go going forward. 

Thank you So much!!!

[grechanka]

Thanks a lot. That helped. I installed trueblood Serena and it broke but with that I managed to fix the thing.

[Nohrin]

On 7/5/2023 at 11:37 AM, Sabre013 said:

Found a solution and putting it here for anyone in future having the issue. Originally from u/Gazibaldi on reddit. 

 

"The issue is with Schlongs of Skyrim. It says so in the error log.

>Unhandled native exception occurred at 0x7FFFBC7BF1F9 (SchlongsOfSkyrim.dll+F1F9) on thread 14820!

The DLL can be very temperamental with load order changes.

To fix it do the following:

-Arrange your load order how you want it.

-Disable the schlongs of Skyrim dll within data\skse\plugins (rename it or hide it in mo2 is fine). Just the DLL not the mod.

-Load your save. It will moan about schlongs version mismatch. This is to be expected.

-Save your game. New save file to be safe

-Close game

-Re-enable the schlongs DLL

-Reload your save and wait for schlongs to re-register.

-From schlongs MCM choose Restart Schlongs of Skyrim

-Wait till that is done.

-Save game and reload game

-Wait for schlongs first time initialisation message.

-In schlongs MCM reimport your settings. This has to be done after the save/reload or it doesn't import properly

-Save your game

-Done

You might find this happens whenever you add something at a lower priority than the schlongs esp or adding a bunch of new esps. Just follow the above each time it blows up."

This does not work on older saves, you would have to repeat the process for them. However, once fixed you should be good to go going forward. 

Thank you so much for saving my playthrough! 

[dozing_off22]

On 7/5/2023 at 9:07 PM, Sabre013 said:

Found a solution and putting it here for anyone in future having the issue. Originally from u/Gazibaldi on reddit. 

 

"The issue is with Schlongs of Skyrim. It says so in the error log.

>Unhandled native exception occurred at 0x7FFFBC7BF1F9 (SchlongsOfSkyrim.dll+F1F9) on thread 14820!

The DLL can be very temperamental with load order changes.

To fix it do the following:

-Arrange your load order how you want it.

-Disable the schlongs of Skyrim dll within data\skse\plugins (rename it or hide it in mo2 is fine). Just the DLL not the mod.

-Load your save. It will moan about schlongs version mismatch. This is to be expected.

-Save your game. New save file to be safe

-Close game

-Re-enable the schlongs DLL

-Reload your save and wait for schlongs to re-register.

-From schlongs MCM choose Restart Schlongs of Skyrim

-Wait till that is done.

-Save game and reload game

-Wait for schlongs first time initialisation message.

-In schlongs MCM reimport your settings. This has to be done after the save/reload or it doesn't import properly

-Save your game

-Done

You might find this happens whenever you add something at a lower priority than the schlongs esp or adding a bunch of new esps. Just follow the above each time it blows up."

This does not work on older saves, you would have to repeat the process for them. However, once fixed you should be good to go going forward. 

Dec 29 2025 still working 

[erzomegadang]

Another thanks!