Fixing a Black Screen or a Game That Won't Launch in an Emulator
The core loads but the game never appears — just a black screen, or an immediate crash back to the menu. Here's how to isolate whether it's the ROM, the core, or your video configuration.
A black screen after loading content, or a core that crashes immediately back to the frontend, has a handful of common, checkable causes — this works through them in order of how likely and how easy to check each one is.
Step 1: verify the ROM/content file itself is not corrupted
Compare the file's checksum against a known-good database
entry (No-Intro for cartridge-based systems, Redump for
disc-based systems) — see "ROM dumping and preservation"
for why this matters.A corrupted or incomplete file is one of the most common causes of an immediate black screen or crash, and is worth ruling out before assuming anything about the core or configuration is wrong.
Step 2: check the core’s log output for an explicit error
RetroArch: Settings → Logging → Logging Verbosity: enable,
then reproduce the issue and check the logA core that fails to initialize a specific piece of required BIOS or firmware, or that hits an internal error, frequently states this directly in the log even when nothing visible appears on screen.
Step 3: check for a missing required BIOS file
Some cores (PS1, PS2, Sega CD, and several others) require official BIOS files to function at all, and will fail silently to a black screen rather than displaying a clear error if that BIOS is missing or in the wrong location:
Check the core's specific documentation for required
BIOS filenames and their expected directory, and confirm
those exact files are present.Step 4: try a different, known-good piece of content with the same core
If a different game works correctly with the same core, the problem is specific to the original content file (Step 1’s corruption check, or region/version incompatibility) rather than the core or your configuration generally.
Step 5: try a different core for the same system, if one is available
If multiple cores exist for the system in question, trying an alternative isolates whether the problem is specific to one core’s implementation — a black screen with one core but not another points at a core-specific compatibility issue rather than something wrong with your content or setup broadly.
Step 6: check video driver settings for a black-screen-specific configuration issue
RetroArch: Settings → Video → Output → try switching the
video driver (e.g., between "gl" and "vulkan")A specific video driver occasionally has compatibility problems with specific graphics hardware — switching drivers is a quick test to rule this out as the cause.
Step 7: check for a shader causing the black screen specifically
Quick Menu → Shaders → Video Shaders: OFFA misconfigured or incompatible shader can occasionally produce a fully black output while the core itself is actually running correctly underneath — disabling shaders entirely isolates whether this is the case.
Step 8: check for insufficient system resources on a demanding core
For resource-intensive cores (later-generation console emulation in particular), a system genuinely unable to keep up can sometimes manifest as a black screen or crash rather than simply running slowly — see fixing a game that runs too fast or too slow for related performance troubleshooting if this seems likely.
Why checking content integrity first is worth the extra minute
A checksum mismatch on the content file explains a black screen completely and immediately, without needing to investigate cores, drivers, shaders, or BIOS files at all — given how quick this check is relative to working through every other step, confirming it first avoids potentially spending considerable time troubleshooting a core or configuration that was never actually the problem.