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
As far as solving the OP's problem, system specs from Steam and load order from LOOT (if you are running any mods) would help quite a bit.
The game also auto saves all the time so you should have a new recent save very soon. Thats why I said to save before. You make a safe save before deleting the old ones.
There are some common characteristics to bethesda coded games (probably because they all use the same frankenstein engine since morrowind... or even before). For example, you can always count on clipping errors... things falling through floors, or floating un supported, or some things extending into or through others. Quest items not being removed. Quests generally bugging out because of logical dependency oversight (like key items falling through the floor). Pathing issues. Scripting errors.
Horrendous optimization (or the lack thereof) and memory leaks, cell based loading problems ... those are common as well =p
And yeah, being smart with which saves you keep is incumbent on the player.... but as a rule, loading befpre a glitch only helps with certain problems (such as scripting). It wont help at all with the host of other issues.