DLSS 5 Swapper Crashes: Restore and Isolate

Preserve the failing state

Write down when the crash happens: before a window appears, while loading a scene, when opening a panel, or after a setting change. Save Swapper diagnostics and the game’s relevant crash message. Include application and component versions, GPU, driver, API, bitness, and existing modifications.

Do this before restoring or installing another package. Repeated reinstalls can replace the evidence needed to identify the original problem. See the project’s diagnostic and recovery documentation.

Test one restored game

1. Close the game and any process holding its files.
2. Select Restore originals for that game.
3. Launch it normally with the same renderer and a known scene.
4. Record whether it remains stable without the Swapper installation.

If it still crashes, investigate the original game’s files, settings, driver state, and unrelated mods. Store verification can restore official files but does not necessarily remove added mod files. The complete recovery guide explains why deleting random DLLs is not a reliable cleanup method.

If the baseline works, isolate one installation

Variable	A useful check	What the result means
Executable and API	Install to the rendering EXE using its active renderer	Removes a launcher or API mismatch from the test
Bitness and runtime	Match required x64/x86 components	Helps identify incompatible loaders or missing prerequisites
Consumer	Install one documented route	Avoids simultaneous ordinary and Multipass consumers
Other injectors	Record and isolate an existing ReShade or proxy loader	Tests a specific loading conflict
Monitoring overlays	Compare with the identified overlay closed	Tests that overlay’s involvement, not all overlays universally
Driver	Record it and consult route-specific evidence	Avoids treating any new-driver warning as a proven cause

Do not change every variable in one attempt. If it starts working, a single changed factor makes the result more useful and easier to reproduce.

Known reports have different causes and outcomes

The v2.2.7 release notes discuss newer drivers and monitoring overlays as contextual factors. They do not say every crash is caused by them.

Issue 189 includes an RDR2 Smooth Motion discussion and a suggested profile workaround that did not resolve the original reporter’s problem. Issue 281 involves changes to both application and driver. Neither establishes a universal fix for “every game.” Use the RDR2 checklist for that game’s launcher and renderer details.

Report or stop at a stable configuration

A useful report states the last working configuration, the first failing one, the exact change between them, and whether restoring originals fixes the failure. Attach reviewed logs rather than personal account details. Do not disable all security controls as a default crash remedy.

If one route remains unstable, restore it and retain the working game baseline. Compatibility checks and the diagnostic entry page can identify whether another documented route is appropriate.