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 might test if instead of restarting, you can log out of windows and then back in. That would at least help a litte and speed up the testing process.
ENB builds it's shaders on application startup. These get then handed to the gpu driver for processing. If the crash occurs due to enb shaders and those somehow linger they might be cleared on reboot. To test that you would have to completely disable the enb. However from my understanding the crash should occur instantly if the shaders are to blame.
Does the same still occur when you run the skse launcher manually (not from your modmanager) so it only loads the base game (with/without enb)? This would solidify that mods are not at fault.
You should also exclude the whole skyrim folder from your antivirus, as well as the mod manager folder. Some of the processes might be shown as false positives. Though again, that should manifest immediatly and not after every crash.
I suppose it could be a .net failure. For versions <5.xx (which skyrim uses if present) you can use microsofts .net repair tool to check for (common) errors:
https://www.microsoft.com/en-us/download/details.aspx?id=30135
It doesn't list win10 as supported os, but i can't test if it will work with win10 right now.
edit: test twice please. Once before running skyrim, once after exiting.
Thank you for the very thorough response.
I tested a new game and it ended up doing the same thing. Then I thought what the heck I'll check to see if my .net had any issues so I ran that tool and it fixed some things.
Then I tried an un-modded game with no ENB and had no issues. After this I was starting to sweat that it could be mods after all.
But after testing my fully modded game with ENB again it loaded the saves! I was able to load saves multiple times after exiting. So oddly enough I think .net may have been the issue or at least contributed to it.
I really do appreciate the help. I would have never thought to check that tool.