Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
When any game bombs out right from the off, then you should automatically suspect it's antivirus (I know that's not the case here but bear with me). Antiviruses can often identify false positives on steam files or game files. Simply go to the antivirus suite, check the quaantined items page, and if there's anything there from either the game or steam itself, make exceptions for them.
In your case, it could well be that a mod is causing a false positive too, which is why it may be bombing out at load of a save.
But any time you start adding mods - especially to Bethesda games - you increase the risk of things going kaput. It's nature of the beast. All you can do in these cases is to either manually uninstall the last mod or so you added to see if it fixes things.
If it does not, then your only real option is to clear everything out and redownload the game vanilla. Then gradually add one mod at a time, running the game each time until you find which one causes the problem.
https://steamcommunity.com/app/489830/discussions/