Azurahawk Posted September 20, 2018 Posted September 20, 2018 So I've tried googling this issue and come to no result. I have this crash log stating "Game has crashed with exception address 0x68701D!". I found 1 individual that provide an example on google that his issue was around Sound files. I uninstalled Immerse Sounds and reinstall, along with bash patching it with the old bash patch (Unsure if I should delete the patch too) and the issue is still the same. Has anyone encounter that exception before? What does it revolve around? Is there a way to identify this code, so I can trace it and figure what is corrupt? It clearly sounds like a corrupt issue, and knowing how to solve it would be a huge step rather than deleting the save file and starting all over - there has to be a way around this. LoadOrder is attached if need to review. LoadOrder.txt
Frednotbob Posted September 20, 2018 Posted September 20, 2018 You can follow the steps here to clear the issue (run a search for the exception code and it'll pop up). It seems to have something to do with the saved file itself; a broken file or script has probably been baked into the saved game. Also, read through the Dangerous Mods Master List (though it may be somewhat outdated) and check it against your load order to ensure you're not using an unstable or poorly-optimized mod.
Azurawhisperer Posted September 20, 2018 Posted September 20, 2018 Whelp. That Ugrid is a red flag. Hopefully that save isn't already screwed; otherwise, may have to start over with the sub. provided.
Corsayr Posted September 20, 2018 Posted September 20, 2018 I get this every now and then. What works for me is as soon as you log in open the console and type player.kill and hit {enter} You should insta die and it will reload the save, but now you should be able to save the game again.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.