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
You can try making a save, waiting in a town or interior cell for 30 days straight, then try traveling there again. A 30 day wait refreshes the world map and all of its associated cells, so whatever is causing the crash may no longer be there. This is the usual vanilla solution to solve such crashes.
In my current playthrough, I don't crash, but the game recently has starting freezing and the game becomes unresponsive when the cell next to Nilheim tower (where a bandit tries to lure you to escort him back to his camp is, only for it to be a bandit ambush) is loaded -- but it only freezes when I approach from the north to the south via the road. It doesn't freeze and the game runs fine if I come from any other direction or if I directly fast travel there. It's extremely weird.
Conflicts like that can definitely cause a crash issue when a broken cell is loaded. Though, if it's two mods conflicting, unless you're not using a mod loader, they should be warning you that there is indeed a conflict.
If you're not using one, I very strongly recommend getting one. Bethesda's in-house one in-game is extremely bad and mod loaders are much better to use. "Vortex" is more simple for simple modding in a "plug-in-play" style and allows you to do things like creating profiles and stuff.
"Mod Organizer 2" is slightly more complicated but allows for more options with customizing one's mod load order which is useful if you're using lots of mods or mods which may conflict with one another.
The most common way to troubleshoot problematic mods is to disable half of your mods, and enable the other half to see if the problem persists or not. You should be starting a new game when you are doing this each troubleshooting attempt.
For example, if I have 100 mods, make 50 mods be group a and 50 mods be group b.
Disable group b's mods, and run group a's mods. If the problem doesn't happen in group a's mods, then disable group a's mods, and enable group b's mods.
If the problem persists in group b's mods, then you split group b in half, so you have 25 mods in group c, and 25 mods in group d.
Then repeat again. Cutting the list of potential mods in half each time, until you can single out the problematic mod(s).
In the case of a broken cell, you should also probably load into the cell directly (open up the console and type in "coc falkreath" and it should drop you nearby. "coc" means "center on cell", teleporting you to the center of that cell). It will save you a lot of walking.