If not and loading a save file actually causes game to inform you about save corruption, then you are actually having a problem. All files should appear and load normally soon. Engine will just need the time to sort out information. Let your character stand still and try to open the menu again.
Game has a really stupid bug, where saves in list may say 'corrupted' when you try to load them from ingame menu. In short: crashing save file can not indicate corrupted file, because Fallout 4 wouldn't let that file to get loaded in the first place. It refuses to load the said save file and attempts to save the situation by creating a tmp file from parsed data in to save folder. Game will 100% inform you on initial load, if your current save file is corrupted. Failing to load a save file due to crashes, or excessive crashing in the game is still not save corruption. This tool can remove these scripts, so you can still use your old save-game file. Only certain way to cause save corruption with mods would be to install files that do not use correct Form version (visible in the file header with tools like 圎dit) - like extremely early mod releases, made with hacky tools before Creation Kit gets released. Unfortunately Fallout 4 store all used scripts in the save-game files, so if you remove a mod that contain scripts, the scripts stay in the save-game and can cause all kinds of errors. Mods are NOT usual reason for save file corruption. Let's make sure that anyone reading this post later understands the difference. I noticed that players spoke about actual warnings, but there are also plenty of misunderstandings.
