The Find The Needle crash on launch fix starts with the Steam checks in order. On an AMD card, apply the launch options or potato mode before anything else, and never delete your save folders as your first troubleshooting step.

Start with the general Steam checks

  1. Let any pending Steam download finish. A half-installed build crashes in ways that look like driver problems.
  2. Restart the machine.
  3. Install the latest GPU driver.
  4. In Steam, open the demo's Properties → Installed Files and choose Verify integrity of game files. Test again after each change rather than making all of them at once.

Crashes are reported in the game's own Steam discussion threads, including one player whose game crashed on the main screen and then kept exiting even after changing settings and the window size. There is no single confirmed cause, so the general checks in order are what actually resolves them.

Two checks belong here regardless:

  • On a dual-GPU laptop, select the dedicated GPU in the Windows graphics settings, because integrated graphics are not supported and may crash.
  • Keep your saves. Back them up before you touch anything — the folder is easy to copy. The specs that decide whether your machine qualifies at all are in the demo PC requirements.

Find The Needle crash on launch fix on an AMD card

There is a documented workaround for a launch crash on AMD cards. The reported failure is an AMD Driver Timeout right after the language screen, with the game minimising and the crash-report window unable to open. One affected machine was an AMD Radeon RX 5600 XT on Adrenalin Edition 26.8.1, and the same timeout was confirmed by a second player reaching the language screen and selecting OK.

Two fixes have been reported to work:

  1. Disable the Steam overlay before launching, then choose potato mode when prompted. You can adjust the graphics settings inside the game afterwards.
  2. Add the launch options --rendering-method gl_compatibility --rendering-driver opengl3. This was credited with fixing the problem on an RX 5700 XT and confirmed by another RX 5700 XT owner.

The proposed root cause is an engine incompatibility with RDNA 1 and RX 5000-series cards. Also check the basics: a dedicated GPU with Vulkan 1.3 support is required, and verifying the game files in Steam repairs damaged installs.

If the game runs but the frame rate is the problem rather than the launch, the performance page covers that separately.

What to include in a bug report

When you report a repeatable crash, include:

  1. Whether it is the demo or the full game.
  2. Your Windows version.
  3. Your CPU.
  4. Your GPU and driver version.
  5. The exact error message.
  6. The reproduction steps.
  7. A screenshot with personal information removed.

The developer takes bug reports on Discord as well as on the Steam hub.