Common Crashes

What should I do when Celeste crashes?

DON'T PANIC

Your first questions should be "Is my Everest version up to date?" and "Are my mods up to date?", as sometimes neglecting updates will cause compatibility issues to arise. If updating both Everest and your mods does not fix the issue (or they're already up to date), continue onwards.

---

Read the first line of the error (after the timestamp). It should contain the following:

System.{ERRORNAME}Exception: {Description of the error}:

As a user, first read through the following list of common errors for something matching or similar to the {ERRORNAME} or description of the error displayed in the log, and follow the instructions provided.
If the particular error is not in the list, no fix is provided, or the fix does not work, then proceed to the instructions below to report the issue.

If you get a different error message, skip to the reporting instructions.

---

System.OutOfMemoryException

You've got too many mods (including maps) installed, and your poor PC can't handle them all at once. Try blacklisting or uninstalling some of them.

• To disable a mod while Celeste is running, open the Mod Options menu from the main menu and select the option to Enable or Disable Mods.
• If you are unable to start Celeste, go to the Mods folder next to Celeste.exe, and add the name of the zip/folder in the blacklist.txt file. For example, if you want Everest to skip over CrystalValley.zip and Dadbod.zip, just put those in blacklist.txt:

CrystalValley.zip
Dadbod.zip

• To uninstall a mod, just go to the Mods folder next to Celeste.exe, and delete the mod's zip/folder.

Tip

The mod you are trying to blacklist may already be in blacklist.txt with a # before it. Simply removing the # will cause the mod to be blacklisted.

If you are out of luck or don't have much RAM, you can make Everest only load textures when they are required. Please note this can cause issues. For that, open Saves/modsettings-Everest.celeste in a text editor (f.e. Notepad) and change LazyLoading_Yes_I_Know_This_Can_Cause_Bugs from false to true.

System.NullReferenceException

This error means that something wasn't initialised properly, and has a variety of causes.

When loading a save

Currently, Viv's Helper causes Celeste to crash when you try to load into a save that tries to enter a map that isn't loaded (a state produced by using the Save and Quit from a map, then later disabling it). Either disable Viv's Helper and load the save, or reenable the mod the map is from.

When alt-tabbing to/from Celeste

It seems that Celeste sometimes crashes when its resolution changes while fullscreen, which happens when switching focus. You can try switching to the FNA version 🔗 of the game, which fixes this due to different fullscreen behaviour.

Mentioning at Celeste.Parallax..ctor

This is because a styleground texture is missing; make sure all required mods are installed, and if it's your map that the styleground is attached to, that it points to a valid png image file.

When leaving a room that has a Theo Crystal in it

There is a vanilla crash when leaving a Theo room in directions other than rightwards; using an Extended Variants crystal instead avoids the crash.

IOException: Too Many Open Files

Celeste has too many files open.
When installing mods, it is not necessary to extract them, as Everest will read the .zip files automatically. This is actually preferrable, because it means that your operating system will only see each mod as one file, rather than potentially hundreds.
Make sure downloaded mods are in .zip files, especially as some systems/browsers will automatically try to unzip them.

Ionic.Zip.BadCrcException

Something went wrong while downloading a mod.
Somehow one of your mod zips got corrupted, and will need to be reinstalled.
If you have an idea of which one it may be (if you downloaded one recently, or if you can check your log.txt for the last loaded mod), then delete it from your Mods folder and redownload it.

Exception: FMOD Failed: ERR_EVENT_ALREADY_LOADED

Two FMOD banks define the same event.
If you aren't actively using FMOD, this error is usually caused by having more than one copy of the same mod (and therefore the same audio bank) loaded at the same time.
Check your Mods folder carefully for duplicate mods and remove them.

Exception: FMOD Failed: ERR_OUTPUT_INIT

Something went wrong with the sound engine used by Celeste.
Possible fixes are:

• Unplug/replug your speakers/headphones
• Try a different set of speakers/headphones
• Restart your audio drivers/your PC
• Update your audio drivers

Steam not found!

Ensure that Steam is running, restart it if necessary.

AggregateException: One or more errors occurred

Can be caused by an outdated Everest version.
Update Everest to the latest version through Olympus.

System.ComponentModel.Win32Exception: SELinux execheap probe failed! Please ensure Everest has this permission, then try again

This occurs due to a permission error on Linux systems running SELinux 🔗, such as Fedora. To resolve this, use the following steps to allow Celeste to have the permissions it needs:

1. Open a terminal window on the computer the crash happened on and run sudo cat /var/log/audit/audit.log | grep -a execheap | grep -a Celeste
   • This searches the SELinux logs for entries showing that it denied Celeste execheap, which is a permission that .NET needs to function properly.
2. If you see an output like type=AVC msg=audit(1702580366.688:3126): avc: denied { execheap } for pid=353681 comm="Celeste" ..., then continue with these steps. If you get an error or no output, follow the instructions below to report the issue.
   • This output indicates that such entries exist in the logs, indicating that Celeste was indeed denied this permission.
3. Run sudo cat /var/log/audit/audit.log | grep -a execheap | grep -a Celeste | sudo audit2allow -M everest_core_fix
   • This finds the same entries as before in the SELinux logs, and then creates a rule that tells SELinux to allow Celeste to have this permission.
4. Run sudo semodule -i everest_core_fix.pp
   • This enables the rule that was created in the previous step, allowing Celeste to have the execheap permission. After following these steps, try launching Celeste again. If the issue is not resolved, please report this on Discord.

Reporting Issues

There are two ways of reporting issues:

Discord (preferred)

• Join the Mt Celeste Climbers Association Discord:
  🔗
• Report your issue in the #modding_help channel, following the checklist.
• Wait patiently for someone to help you.

GitHub (only for issues with Everest itself, not with mods)

• Create a New Issue on the main Everest GitHub 🔗.
• Use a descriptive title (not just "Crash plz help").
• Follow the checklist to report your issue.

---

Reporting Checklist

• Describe what you were doing before you encountered the error.
• If it was working previously, list any changes you made to your game since then.
• Include what you have done already to try to fix it.
• Attach the error_log.txt and log.txt (both located in your Celeste folder).
  If you got the Catastrophic Error warning, then only the log.txt is needed.
• If this is an error you believe to be specific to a mod, notify the mod author if possible.

Important

If you have restarted your game since the crash, your log.txt will have been reset.
Everest will automatically store past logs in the LogHistory folder, which is also in your Celeste folder.