Checklist: CTD after Bethesda screen

Guide aimed to solve problems related to crashing after Bethesda logo, while attempting to load Skyrim. It is based on the post I made for the main forum. It has gathered enough replies and time to get posted here as tutorial.

Feel free to post questions and suggestions, if more matters arise around this topic.

Index

1. Description

2. Problems

1. Applications potentially interfering with Steam
   
2. Language mismatch
   
3. Wrong version of ENB binaries (Files)
   
4. LOOT: Missing parent data for mods you have installed
   
5. (TES5Edit) Still missing parent data for mods you have installed (Mods)
   
6. Sneaky remnant patch for removed mod that didn't show up with LOOT (Mods)
   
7. Workshop: It's crashing and I don't know why! (Mods)
   
8. Workshop: Auto-update has made some of your mods incompatible with other mods (Mods)
   
9. Broken master files (Files)
   
10. Issue with FISS (FileAccess Interface for Skyrim Script)
    
11. Nothing works! (Files)

3. Tool download links

1. LOOT
   
2. TES5Edit
   
3. Wrye Bash

4. Tutorial changes

1. Description

CTD (Crash To Desktop) after Bethesda logo usually means that one ore more of your mods is lacking the required data from other files: master data from mods and master files (original game files + official DLC files). Crashing game may be using wrong files or lacking dependency files for mods. Some mods may have also been updated to be incompatible with others.

Sometimes a third party tool or file that is not shown in tools we use may be the cause of these crashes.

This post tries to list the most common reasons for CTD after Bethesda logo and suggest solutions for them. It is not an official post, but based on my personal knowledge and experience. Thus, there might be something missing from my list or solutions that I have suggested. I will try to update this post when ever I gain new information that is relevant for this matter.

Original post and discussion can be found from here:
http://steamcommunity.com/app/72850/discussions/0/613939294279340285/

Additional Credits:
- grimus, for linking selective startup mode from Bethesda.
- Nazenn, for Wrye Bash instructions and visual example.

2. Problems

1. Applications potentially interfering with Steam
   Some applications may interfere with Steam and force games like Skyrim crash to desktop after Bethesda screen. Link to Steam support list of these applications:
   
   Programs Which May Interfere with Steam Steam Support
   https://support.steampowered.com/kb_article.php?ref=9828-SFLZ-9289
   
   
2. Language mismatch
   Using different language with Skyrim than with Steam or system may cause the game to CTD after Bethesda screen. This is a less common reason for the crash, but plausible one.
   
   Changing Steam language:
   
   • Steam client > Steam > Settings > Interface > Select the language you wish Steam to use (requires Steam to restart)
   
   Changing Skyrim language:
   
   • Steam client > Library.
     
   • Right click the game.
     
   • Properties > Language > Select the language you wish to play this game in:
   
   
3. Wrong version of ENB binaries
   If you are using ENB, then be sure that you are also using binary pack version that your ENB was designed to use. Effects of wrong binaries vary from minor things to CTD after Bethesda logo.
   
   
4. LOOT: Missing parent data for mods you have installed
   Run LOOT to sort your load order. Pay attention to number of Errors in Summary view and look them up from Details view. Note that missing data might also be missing master file data from DLCs that you have not installed. In this case you are using a mod or patch that relies to DLC content.
   
   Resource priorities and load order exceptions
   There are few files that LOOT does not yet place correctly. I have gathered them to post linked below. Post also makes notes about Resource Priorities, pointing mostly (but not only) to peoples using Mod Organizer mod and manage their games.
   
   Linked post also contains quick instructions how to run LOOT.
   
   Load order and resource priority basics
   http://steamcommunity.com/app/72850/discussions/0/523890681419356033/
   
   
5. (Advanced) Still missing parent data for mods you have installed
   LOOT is very accurate and should be used as primary tool to solve issues with load order items. However, there are few cases where it may not find a problem, especially with certain patches. Running TES5Edit or Wrye Bash can find the troublesome item from your load order.
   
   TES5Edit
   
   • Run TES5Edit. If you are using MO, then you must run TES5Edit trough MO.
     
   • The opening screen will list all your mods. Select “OK”
     
   • Let it run. Screen will stop and tell you it is finished when it is done. Close TES5Edit from clicking the red X in up right corner.
     
   • If TES5Edit finds a problem, then it will stop the process and inform you about what is missing. Close TES5Edit from clicking the red X in up right corner. Download or update the mod that had problems and run TES5Edit again.
     
   • TES5Edit should not ask you to save anything during this process. If it did, then select no or close the tool directly. Do not save or accept any save request (that should not happen) during this process.
   
   TES5Edit is not a mod for NMM or MO. You will need to unpack it for application to become available - as is the case with almost any other pack of files you download from the internet.
   
   Wrye Bash
   Wrye Bash can also be used to detect missing masters.
   When Wrye Bash is opened it will automatically display any missing masters by giving them a red checkbox on the left hand side. If you click on the mod with the red checkbox it will display a list of all masters on the right hand side including marking down the specific master file that may be missing. Visual example: https://i.imgur.com/J70vouy.jpg
   
   
6. Sneaky remnant patch for removed mod that didn't show up with LOOT
   - Workshop and NMM users: Disable your mods. Visit the default Skyrim launcher Data Files view to see what is still lingering there.
   
   - Mod Organizer users: You should not have this problem, if you have properly installed your mods to MO. All mod folders under MO are visible in the left hand panel. Check the Data Files, just to be sure. Then polish your eyes and see what you have left lingering around your Mods list in MO.
   
   
7. Workshop: It's crashing and I don't know why!
   Make sure that files you have unsubscribed from, while meaning to remove them from your game, are actually removed from your game. Check your files in Data Files view against the list of mods you have subscribed to.
   
   Keep in mind that Workshop has been bugged out since early 2015. Refer to this post for more information:
   
   PSA: Current state of the Skyrim Workshop + Modding Resources by Nazenn
   http://steamcommunity.com/workshop/discussions/-1/451850213943051342/?appid=72850
   
   
8. Workshop: Auto-update has made some of your mods incompatible with other mods
   If it is not showing up in LOOT, then there really isn't something we can do about it.
   
   Make a quick glance trough most recently updated files to start troubleshooting. Look the comments below them in Workshop. Check the forum page, in case someone is complaining about the same matter.
   
   Use your favorite technique of disable and enable mods in groups to locate the problem file. Keep in mind that you will have to disable parent file mods for every mod that you disable at the same time, or game will only CTD from that error as well.
   
   
9. Broken master files
   One or more of your master files (Skyrim.esm, Update.esm ect.) is damaged, or otherwise messed up. It needs to be fixed.
   
   • Exit Steam.
     
   • Go to Steam folder and remove folder named appcache
     
   • Close your computer and let it cool off a little, to clean your registry cache. Take a peek outside the window to see how the weather is.
     
   • Start your computer.
     
   • Start Steam. Let it load for a while, when it is inspecting your game files for new appcache folder.
     
   • From Steam client Library view, right click the game with your mouse.
     
   • Select Properties > Local Files > Verify Integrity of Game Cache...
   * 1 file will always fail to validate. It is related to how Steam detects your graphic card configurations and has no effect to your game.
   
   * If you had cleaned your master files with TES5Edit, you will have to repeat the process. Steam will consider them modified and replace them.
   
   
10. Issue with FISS (FileAccess Interface for Skyrim Script)
    Falsely installed FISS, issue with it's functions or file access error can cause game to crash to desktop after Bethesda logo.
    
    • If you see CTD after Bethesda logo, then try to remove FISS to rule this problem out.
      
    • Make sure that FISS can actually read files from your game folder. File access permission issue might cause the problem.
      
    • Check the community that uses FISS for detailed troubleshooting.
      
    • FISS is not safe to remove from ongoing game. If FISS is causing the issue and issue does not get solved, then you will have to start a new game without FISS.
    
    
11. Nothing works!
    
    • Uninstall the game.
      
    • Delete your whole Skyrim folder.
      
    • From Documents > My Games > Skyrim, delete configuration files Skyrim.ini and SkyrimPrefs.ini. You don't have to delete your saves.
      
    • Close your computer.
      
    • Start your computer and install Skyrim again.
      
    • New Skyrim.ini and SkyrimPrefrs.ini files will be created, when you launch the game and set Options.

3. Tool download links

1. LOOT
   https://loot.github.io/
   
   
2. TES5Edit by ElminsterAU
   http://www.nexusmods.com/skyrim/mods/25859/?
   
   
3. Wrye Bash by Wrye Bash Team
   http://www.nexusmods.com/skyrim/mods/1840/?

4. Tutorial changes

• 23.06.2019
  - Added FISS information. Rare issues with LE and SE versions have appeared long enough that I am considering this one of the potential causes for CTD after Bethesda screen. Unfortunately I am not adept enough with the mod to provide detailed information. Only generic information that has been previously provided, which seemed to have fixed the issue. The FISS community is the best help in this matter.
  
• 02.09.2018
  - Removed Selective Startup section, due to link being removed from Bethesda's site, without proper replacement for it.
  
• 11.09.2017
  - Updated the missing tool information and changed section 3 title.
  
• 16.08.2016
  - Added: Link to PSA: Current state of the Skyrim Workshop + Modding Resources
  - Added: Language mismatch and instructions.
  - Changed: Xfire instant messaging -> List of applications that can interfere with Steam.
  - Changed: Cleaned the guide from unnecessary edits and remade the Index form.
  
• 14.02.2016
  - Added: Note about LOOT instructions in Load order and resource priority basics
  
• 10.10.2015
  - Merged: Resource priorities and load order exceptions to chapter 3. Renamed to reflect LOOT.
  
• 5.8.2015
  - Added: Resource priorities and load order exceptions
  
• 26.6.2015
  - Added: Link to Wrye Bash. Reminded by grimus. Thanks.
  - Added: Wrye Bash instructions. Credit: Nazenn.
  
• 16.1 2015
  - Posted, based on the original forum post and discussion.

[Sapko]

Need help for lunching the game !
I lunch the game from Steam and the game menu pops but not the "Continue, Settings etc." How can I solve this ? I just see the logo on the main menu and can't do anything but turn off the game...

[Ilja]

Do you have dedicated thread about the matter? Everything should be here, except that I have forgotten to include issue caused by wrong ENB binary issues. I will do that, when I make a new revision of the guide for SSE and FO4. Right now I am slightly avoiding spending long times on computer, due to health related problems.

[Pvt Awoo]

I'm not having any luck with trying to fix skyrim and as comprehensive as all this is I'm still not sure why I'm having CTD after bethesda logo.
Game was fine two weeks ago and now its fubar

[tlktk]

How "PROXY" has been set in enblocal.ini when using ReShade together with ENB's may also be a root of the problem if Skyrim refuses to start.

[PROXY]
EnableProxyLibrary=true
InitProxyFunctions=true <<-- Then change this to false (guess it delays ReShade a bit).
ProxyLibrary=other_d3d9.dll <-- This name is connected with ReShade and should always have the same name as the original file that's used by ReShade

[Angrypillow]

I'm glad you added the information about FISS, as that was indeed the cause of my problem.