Citra crashing immediately when opening any game

Whenever I attempt to open any rom in Citra, it crashes before loading the actual game, a few seconds after the black loading screen appears. Resetting all settings fixes this for one or two opens of a game, sometimes requires resetting all settings multiple times.

System Information

  • Operating System: Windows 10
  • CPU: AMD Ryzen 3 3200G with Radeon Vega Graphics
  • GPU:
  • Citra Version (found in title bar): Canary 2408
  • Game: Any and every game I have
  • Screenshot of Issue (include the full Citra window including titlebar): Screenshot impossible

Diagnostic Log
citra_log.txt (16.0 KB)

citra_log.txt (16.0 KB)

Go to File>Open Citra Folder. Delete the shaders folder found here. Now try again.

The problem persists after trying this.

try to switch with Nightly Build?

Please upload a new log file.

citra_log.txt (16.0 KB)

Hmmm, please try out a portable Citra build to rule out a bunch of things:

Go to Download Citra - Citra and select Manual download. Then under Nightly Build, click on your operating system’s icon to the right of the latest build available to download the build.
Extract it (.7z can be extracted using Winrar or 7zip) and put it wherever you wish. Inside the extracted nightly-mingw folder, create a folder called user. This Citra should now store all of its config, save files and such inside of this user folder.
Check to make sure that this user folder is in the same folder that contains citra-qt(.exe)
Now run the citra-qt executable found inside of the mingw folder.

If the issue persists, upload a log file using this portable build.

This seems to fix the problem.

It turns out that this doesn’t fix the problem, but I have discovered the strange bug that causes it. I have two screens, one of which is a drawing tablet. If I open a game on either version of Citra on the drawing tablet, it crashes, but does not crash if opened on the other screen.

1 Like

I was losing my mind over this bug and this was the only thing that solved it, thank you so much.

Adding to this, my second screen is a common television, so I think the bug may occur on any secondary screen, regardless of what it is. It’s also ocurring in the current Nightly version (1853).