Support

Try this first.

Most “PCSX2 won’t run” threads boil down to a short list: missing runtimes, outdated GPU drivers, wrong BIOS region, or a bad rip. Work top-to-bottom here before reinstalling Windows or chasing obscure registry hacks.

If you open a forum thread or GitHub issue, include OS version, CPU/GPU, PCSX2 build (stable vs nightly + exact version string), renderer, and whether software renderer reproduces the bug—that package gets answers fastest.

VC++ runtime (Windows)

Install VC++ 2019–2022 x64, reboot, then launch PCSX2 again.If the window flashes and dies with no message, Event Viewer → Application logs sometimes names the missing DLL—still fixable with the same redistributable.

Graphics settings crash

Update GPU drivers from AMD, Intel, or NVIDIA—not only Windows Update. Remove experimental “Vulkan compatibility” layers if you installed them for other games.If opening the graphics panel crashes instantly, start with software renderer from a safe config backup or reset graphics.ini per upstream docs.

Audio crackle

Confirm stable full speed with an on-screen FPS readout before touching SPU2-X latency sliders—crackle is often “CPU can’t keep up” in disguise.Close Bluetooth-heavy apps; try wired headphones to remove wireless jitter from the equation.

Black screen

Verify the rip with another tool; try software renderer once to see if it’s GPU-specific.Confirm BIOS region matches the game; some failures look like graphics bugs but are actually boot-level mismatches.

Low FPS

Use Vulkan or D3D12 on Windows when available; drop internal resolution to native; disable aggressive texture filtering experiments.Check laptop power mode and plugged-in status—silent profiles cap CPU hard enough to tank PS2 titles.

ISO won’t mount / invalid disc

Re-dump with a known-good tool; confirm the file size isn’t truncated or zero-padded.BIN/CUE vs ISO can matter for some discs—follow per-game wiki guidance for that serial.

Stuttering or hitching every few seconds

First runs compile shaders and build caches—retest after a few minutes of play.Disable Discord/GeForce/Steam overlays temporarily; some hook DXGI in ways that add frame pacing noise.

Controller not detected / wrong mapping

Disconnect Steam Input or reWASD remappers for a test; map in PCSX2 directly.On Windows, try both XInput and raw HID modes if your pad offers both; on Linux check udev permissions.

Fullscreen issues (wrong resolution, blank)

Toggle between exclusive, borderless, and windowed; disable HDR temporarily on some displays.If only fullscreen fails, file a report with monitor model, cable type (HDMI/DP), and GPU driver string.

macOS-specific

Use a build matched to your chip generation; Metal backends evolve quickly across macOS releases.Grant input permissions if the OS prompts; some security tools block low-level pad access.

Linux-specific

Confirm 64-bit userspace, Mesa or proprietary Vulkan stacks, and a working vulkaninfo.Wayland vs X11 changes fullscreen behavior—test borderless windowed to narrow the bug.

Before you post “nothing works”

  • Update to the latest stable (or the nightly mentioned in a fix you’re chasing).
  • Reset graphics settings to defaults, then change one option at a time.
  • Search the wiki for your exact game serial; many issues are documented with a patch or workaround.
  • Attach the emulog snippet the forums ask for—without it, replies are guesswork.

Bug report template (copy mentally)

  • OS + version (e.g. Windows 11 24H2)
  • CPU model, RAM, GPU model + driver string
  • PCSX2 version (paste from title bar / about)
  • Renderer + internal resolution
  • Repro steps from cold boot → failure
  • Does software renderer reproduce it?

When not to open a GitHub issue

Support chats and forums are better for “how do I click BIOS” questions. Issues should be reproducible bugs or clear regressions with logs—noise buries the patches contributors need to write.

If you’re unsure, ask once with logs attached; someone will redirect you if it belongs elsewhere.

Performance triage order

  1. Power plan / thermals / background CPU hogs
  2. Native internal resolution, default renderer
  3. GPU driver update (clean install if you’ve stacked betas)
  4. Game-specific wiki notes and recommended hacks
  5. Try the other mainstream hardware renderer

Issue tracker · Setup · FAQ · Compatibility