Epsxe | Core Stopped 3.16

Fixing the "epsxe core stopped 3.16" Error in RetroArch: A Complete Guide

If you are a classic PlayStation 1 enthusiast using RetroArch, you may have encountered a frustrating roadblock: the dreaded "epsxe core stopped 3.16" error message. This typically appears when you try to load a PS1 game, and instead of hearing the iconic boot-up sound, you are kicked back to the RetroArch menu.

This error is cryptic, but not insurmountable. It usually points to a mismatch between the core’s expectations and your system’s files or hardware. In this long-form guide, we will break down exactly what this error means, why it appears, and—most importantly—how to fix it permanently. epsxe core stopped 3.16

D. Permissions & Storage Issues

On Android 11+, storage permissions changed (Scoped Storage). If ePSXe cannot read BIOS, games, or config files from external SD cards, it may crash without a proper error message. Fixing the "epsxe core stopped 3

On Nvidia Shield TV / Android TV

Fix #2: Delete or Migrate Save States

If the error happens when loading a game: Ensure your ePSXe app is updated from the

  1. Go to /sdcard/ePSXe/savestates/.
  2. Move all .state files to a backup folder on your computer.
  3. Restart the game normally (using in-game memory card saves, not save states).
  4. Once stable, try converting old states by loading them in an older ePSXe version (3.14), saving a memory card save, then updating to 3.16.

What Does "epsxe core stopped 3.16" Actually Mean?

First, a clarification: RetroArch does not use the standalone ePSXe emulator. Instead, it uses a core called PCSX-ReARMed (or sometimes SwanStation or Beetle PSX) for PlayStation 1 emulation.

The message "epsxe core stopped 3.16" is a misleading wrapper error that appears when the core crashes on startup. The "3.16" typically refers to a version number or an internal state code from a plugin or a compatibility shim. Essentially, it means:

This error is most common on Android, iOS, Raspberry Pi (RetroPie/Recalbox), and low-power ARM devices, though it can occur on Windows/Linux as well.

2. Install Legacy Runtimes