A black window, a picture that freezes on the first frame, or Snes9x closing the instant you load a game usually points at one thing: the video output method Snes9x is trying to use is not getting along with your graphics hardware or drivers. The good news is that the Windows build of Snes9x 1.63 offers four different output methods, and switching between them takes seconds. Start from a clean, official copy — see our download page — and work through the steps below. More fixes live in the troubleshooting hub.
Step 1 — Switch the output method
Snes9x for Windows can render through DirectDraw, Direct3D, OpenGL or Vulkan — those are the four output methods the 1.63 build registers. Open the video/display settings and pick a different one, then load your game again. If Direct3D gives you a black screen, OpenGL or Vulkan will often work, and vice versa. Vulkan is a good test on newer systems because it arrived in Snes9x 1.62 and uses a completely separate code path from the older DirectDraw and Direct3D outputs. If Snes9x crashes before you can even reach the settings menu, skip to the config reset below — the output choice is stored in the config file, so resetting it returns you to the default.
Step 2 — Test without shaders
If the black screen only appears with a shader enabled, the shader and the output method are probably mismatched. Shader formats are tied to the renderer: Cg shaders work in both Direct3D and OpenGL, GLSL shaders are OpenGL-only, and slang shaders work with OpenGL (since 1.59) and Vulkan (since 1.62). Loading, say, a GLSL shader while rendering through Direct3D cannot work. Set the shader to none, confirm the game displays correctly, then re-enable a shader format that matches your chosen output.
Step 3 — Reset the config file
Settings in Snes9x live in a plain config file, snes9x.conf, in the same folder as the executable. The bundled FAQ’s official answer for messed-up options applies here too: you can safely delete snes9x.conf (with Snes9x closed) to reset every option to its defaults. Snes9x recreates a fresh file on the next launch. This clears a bad output method, a broken fullscreen resolution or any other half-remembered tweak in one move. Your ROMs and your Saves folder are untouched — but if saves are your actual problem, read the saves not working guide instead.
Step 4 — Update your graphics drivers
If several output methods fail, suspect the driver underneath them. Install the current graphics driver from your GPU maker’s official site (or your laptop maker’s support page) rather than relying on an old driver Windows installed years ago. This matters most for the OpenGL and Vulkan outputs, which depend directly on driver support; a stale driver is a common reason Vulkan in particular refuses to start. After updating, restart the PC before retesting — graphics drivers often do not fully swap in until then.
Step 5 — Confirm the game itself loads
A black screen after the game starts can also mean the ROM never loaded properly. Try a second game: if every game is black, the problem is video; if only one title is affected, work through our ROM won’t load checklist for that file. Also worth a quick check: if Windows reports a missing DirectX DLL when Snes9x starts, that is a separate, specific failure with its own fix — see the d3dx9_43.dll error guide.
Step 6 — Re-extract a fresh copy
If nothing above helps, eliminate the install itself. Download Snes9x 1.63 again from the official GitHub releases page (our download page links it and publishes the verified SHA-256 checksums), extract it to a fresh folder somewhere writable — not inside Program Files — and launch it before changing a single setting. A clean folder separates “my configuration is broken” from “this system has a deeper problem”, and in practice the fresh copy resolves most stubborn startup crashes. Once it runs, change one setting at a time so you learn exactly which option your system dislikes.
Two more checks: fullscreen and dual-GPU laptops
If the game displays in a window but goes black in fullscreen, the fullscreen resolution or refresh combination is the likely culprit — reset the config file (Step 3) to return fullscreen to its defaults, then re-enable it and note the exact moment it breaks. On laptops with both integrated and dedicated graphics, there is another possibility: Windows may be handing Snes9x to a different GPU than you expect, and the two GPUs’ drivers can behave differently with the same output method. Your graphics settings in Windows (or the GPU vendor’s control panel) let you assign which GPU an application uses; if one output method fails on one GPU, testing Snes9x on the other GPU is a legitimate diagnostic step. As with the output methods themselves, change one variable at a time and keep notes — a black screen that depends on three settings at once is only debuggable if you isolate them.
Quick recap
- Switch the output method among DirectDraw, Direct3D, OpenGL and Vulkan.
- Disable shaders, then re-enable only a format that matches your output method.
- Delete snes9x.conf (with Snes9x closed) to reset all options to defaults.
- Install the current GPU driver from the manufacturer, then restart the PC.
- Test a second game to separate a video problem from a single-ROM problem.
- Re-extract a fresh 1.63 copy into a writable folder and test before changing any setting.