Metazolid

Don't want to necro this threat, but that's the top result that shows up regarding this issue and I want to add my solution to it as the command mentioned previously wasn't working for me; I moved to a settlement and ordered my follower to exit the armour which she didn't do of course, then proceeded to pick her character up with Place Everywhere - https://www.nexusmods.com/fallout4/mods/9424 and just drop her so that she pounds on the ground. She promptly exited the suit after that. I'm not sure if you can pick the follower (with or without the armour) up when not having the mod installed, so this may not work for you if you haven't installed a mod which allows you to do this.

Just a small update for anyone who might run into the same issue and reads this; I've not modified or tried to fix the bug in any way, though made sure to have a backup of my most recent dozen saves or so, just in case there is corruption that carries over to the others for some odd reason. I kept on playing as usual, avoiding the area, I came back to it some dozen hours later and it seems to be working fine, though I must say I've played on a new PC in the meantime as well where I checked in on it. tl;dr.: Solution 1: If you notice this happening, backup your recent savegames located in Users\(YourUsername)\Documents\My Games\Fallout4 just in case.Avoid running into the general area for the forseeable time, I know it could suck if its a settlement or a place you frequently visit, but that's what it is.Check back if the game has (I guess overwritten) fixed what ever caused the issue on its own after a dozen hours of playtime. Solution 2: (Not sure if that works and I doubt this will be an applicable fix for anybody but whatever) Build a new PC

I'm fine with you two throwing down, but don't do that in my thread. Thanks.

I'll be playing the game as usual now, avoiding this area, or rather the whole island altogether. Maybe some bad code snuck in while saving at some point and hopefully it'll be overwritten/removed on its own at some point.

Thats some good news, that means it's defintely some sort of savefile issue that can be replicated on other computers. I hope that someone who has more experience with this sorts of things than us can help me out, thanks for the suggestions you've given me so far ^^

I've pinned the issue down to two saves between 2nd Dec. and 3rd Dec. 2019. My mods have slightly changed since then, but both are affected by the same way and show the same warning in the main menu, so I don't think it's related. (https://imgur.com/a/ksY7pB4 Live Dismemberment installs all .esp files by default for some reason, but never caused noticeable problems. Reinstalled it with only one .esp yesterday, no change ofc.) REEL reported the VM (?) as freezing & frozen (https://imgur.com/a/RkO1EtA), brushed over it with some googling but Papyrus really doesn't seem to be helpful for this situation, someone please correct me if I'm wrong :laugh: I think I've used ReSaver at one point, but neither cleaning it with version 4.3.2. nor 4.5.0 would change anything, I even removed pretty much everything that was optionally availble after some testing. To my surprise the game still ran, but still crashed at saving like described previously. I will now go back to my most recent save and let the area reset itself like HeyYou suggested it, I have backups from all by saves stored in a separate folder, so I can always go back and mess with copies lateron. II've uploaded upload both savefiles for you and others to try out, the latest one that worked before the bug came up, and the first one after the bug. You don't need the same mod-loadout like I do, both games have been saved after all mods have been disabled. I have not cleaned them afterwards, but from what I've experienced, it wouldn't make a difference. https://drive.google.com/drive/folders/1Ecnn1Vh0o8Sb0QGGJW-QhIMAQSo-Y3Gr?usp=sharing

I don't think so, most of my mods are additions or fixes of/to pre-existing functions like weapons, settlements and UI. The only thing I can think of is that maybe one of the few mods for settlements act up when I try to leave the area around the Daltons Farm. I've previously disabled all mods and tried to nail it down to a specific one like usual, to no avail. Just forgot to list it among the other attempts. Will try it again nonetheless, maybe clean up the savegame from all mods and see is that changes anything. Does it help to use the concole command set timescale and change the value from 20 to like 500 to skip 5 weeks or would that not have an affect on area resets? I only tested out fairly recent ones. I just put some hours into a settlement previous to that issue, I'll try one from that time and hope I won't have to start over, I'd really want to know what caused the issue to avoid it in the future. I'll install REEL and see if that spits out something useful. As said above, there shouldn't have been a mod interfering with that area. The save has 6 Days clocked in, so it's neither old, nor riddled with dozens of dead mod files. :laugh: But I'll double check if a mod is the cause for all of this.

Hope you guys can help me resolve this issue; Whenever I cross the marked line on the bridge between the Daltons Farm and National Park Visitor's Center, the game CTDs when I (quick)save or (quick)load. When I enter and leave the bridge, back to where I have had no issues, it also CTDs when (quick)saving or (quick)loading. Images are down below. Things I've tried out that also helped out other to fix similar problems: Disabled all modsDeployed mod list with VortexApplied mod loadorder via LOOTLoaded & saved savefiles via consoleFixed LOOT warnings with FO4Edit 4.0.3Deleted all .ini files in /mygames/Fallout4Savegames are not exceeding 20mb eachCleaned up savefile after disabeling all mods with ReSaverReduced the amount of savegames in the Saves folder to only a fewKilled myself via console, as well as natural cause (radiation in this case)Started a new game with all mods enabled and saved in the area without issuesChecked that F4SE & all mods are up to date and compatible with my FO4 Version 1.10.163Please let me know what else I can do to fix this, I've been googling around a lot and tried out several things as you can see, I will continue to do so in the meantime. Thanks a lot :laugh: System Specs Plugin Order Images --------------------------------------------------------------------------------------------------------- Stupid solution; Just a small update for anyone who might run into the same issue and reads this; I've not modified or tried to fix the bug in any other way than I've already described above, though made sure to have a backup of my most recent dozen saves or so, just in case there is corruption that carries over to the others for some odd reason. I kept on playing as usual, avoiding the area, I came back to it some dozen hours later and it seems to be working fine, though I must say I've played on a new PC in the meantime as well where I checked in on it. tl;dr.: Solution 1: If you notice this happening, backup your recent savegames located in Users\(YourUsername)\Documents\My Games\Fallout4\Saves just in case.Avoid running into the general area for the forseeable time, I know it could suck if its a settlement or a place you frequently visit, but that's what it is.Check back if the game has (I guess overwritten) fixed what ever caused the issue on its own after a dozen hours of playtime. Solution 2: (Not sure if that works and I doubt this will be an applicable fix for anybody but whatever) Build a new PC