sweetcorncobs Posted November 17, 2017 Share Posted November 17, 2017 Hi guys I've got this new problem I had with Skyrim, I've played this game for more than 300+ hours and although crashes are normal and freezes they rarely occur and it isn't as frequent as it was just recently...for some reason my Skyrim SE keeps crashing at almost always within 30 minutes, it just happens for some reason no matter where I am or what I do it'll just crash, this happened after I ran LOOT to fix the black face bug (which it partially did) and left it there...other things I did was run TES5EDIT, add an animation mod, add two armor mods one for SSE the other I imported from Oldrim. Plus for some reason the moon is gone :/ if there's any advice you can give please let me know :) game is pretty much unplayable at this point. I'll try resorting my load order for now... tl;dr- SSE suddenly keeps crashing within 30 minutes (no matter what i do or where i am) even though this never happened before Link to comment Share on other sites More sharing options...
jones177 Posted November 18, 2017 Share Posted November 18, 2017 Hi Check your GPU & CPU temps. As saves get older they tax your system more. Also CTDs can get into a save. The only way to test is to start a new character. If the CTDs persist it is in the game. If you got the black face bug it may be a resource issue. If faces are dark brown it is a mod issue.If you have trouble telling the difference move close to the inflicted NPC by using the console command "tfc". If you see black polygon shapes(triangles) it is black face bug. Brown face big is mainly caused by mods that change the appearance of NPCs. You can get it with mods like Bijin Warmaidens SE. Moving the mod down in the load list usually fixes it.There are mods that cause brown face bug if they are anywhere on your load list. The Vampire brown face bugs is an example of this. This bug can get into your save so removing the mod causing the bug may not fix it unless you start a new game. In the old game I used mods that changed to look of NPCs to hide the bug that was caused by other mods that changed the look of NPCs. Really complicated. Loot can trash your game, but it is a good second opinion when dealing with mod issues.It is best to save your load list before you use Loot. It is located at \AppData\Local\Skyrim Special Edition. It is called plugins.txt. Those are hidden files so you need to unhide them. This file is the way the game "sees" your load list & load order. WARNING. This file is your modded game. If you trash it, you trash your game. Any time you want to go vanilla for testing(no mod esps) move the plugins.txt file to another location & the game will make a new one without mods on startup. Move the file back after testing. Don't use the test saves after putting the file back unless they were created without mods. This type of testing helps to find if the CTDs are in the save or in the game. There is a difference. I have only had one timed CTD in this game. It was with the mod Beyond Skyrim - Bruma SE. Moving around the esp in the load list only changed the CTD to a freeze. No Beyond Skyrim - Bruma SE for me!In the old game I had one that was caused by a custom follower conflicting with UFO. That was hard to find because it did not start right after I added the follower. It took a lot of reading on this site to find a solution. Later Link to comment Share on other sites More sharing options...
sweetcorncobs Posted November 19, 2017 Author Share Posted November 19, 2017 Hi Check your GPU & CPU temps. As saves get older they tax your system more. Also CTDs can get into a save. The only way to test is to start a new character. If the CTDs persist it is in the game. If you got the black face bug it may be a resource issue. If faces are dark brown it is a mod issue.If you have trouble telling the difference move close to the inflicted NPC by using the console command "tfc". If you see black polygon shapes(triangles) it is black face bug. Brown face big is mainly caused by mods that change the appearance of NPCs. You can get it with mods like Bijin Warmaidens SE. Moving the mod down in the load list usually fixes it.There are mods that cause brown face bug if they are anywhere on your load list. The Vampire brown face bugs is an example of this. This bug can get into your save so removing the mod causing the bug may not fix it unless you start a new game. In the old game I used mods that changed to look of NPCs to hide the bug that was caused by other mods that changed the look of NPCs. Really complicated. Loot can trash your game, but it is a good second opinion when dealing with mod issues.It is best to save your load list before you use Loot. It is located at \AppData\Local\Skyrim Special Edition. It is called plugins.txt. Those are hidden files so you need to unhide them. This file is the way the game "sees" your load list & load order. WARNING. This file is your modded game. If you trash it, you trash your game. Any time you want to go vanilla for testing(no mod esps) move the plugins.txt file to another location & the game will make a new one without mods on startup. Move the file back after testing. Don't use the test saves after putting the file back unless they were created without mods. This type of testing helps to find if the CTDs are in the save or in the game. There is a difference. I have only had one timed CTD in this game. It was with the mod Beyond Skyrim - Bruma SE. Moving around the esp in the load list only changed the CTD to a freeze. No Beyond Skyrim - Bruma SE for me!In the old game I had one that was caused by a custom follower conflicting with UFO. That was hard to find because it did not start right after I added the follower. It took a lot of reading on this site to find a solution. LaterYo thanks for the extra info but funny enough none of the mods caused the crashes it was the "touch keyboard" thing from windows 10 after I disabled it skyrim pretty much went back to normal never thought something like that would cause the crash. Took notes on what you said though, would be nice to know extra things to check through next time a problem like this comes around :) Link to comment Share on other sites More sharing options...
Recommended Posts