AMD And Cyberpunk Ray Tracing Initialization Error | Fix

Guide / By

Most Cyberpunk ray tracing init errors on AMD clear after a clean driver install and a reset of graphics settings.

You hit Play, the screen blinks, and Cyberpunk 2077 closes with a ray tracing initialization message. It’s frustrating because it feels like the game is blaming your GPU, even when everything ran fine yesterday.

In most cases, this crash happens because a driver install got messy, a Windows update changed graphics components, or the game is trying to boot with ray tracing or path tracing settings your current setup can’t start cleanly. The goal is simple: get the game launching first, then turn ray tracing back on in a controlled way. It takes less than 30 minutes.

What The Error Usually Means On AMD

That popup is the game telling you it failed to initialize DXR features at launch. Ray tracing in Cyberpunk relies on DirectX 12, the GPU driver, and saved graphics settings that can force ray tracing on before you reach the menu.

On AMD systems, the trigger is often one of these: a corrupted driver stack after an update, a settings file that keeps ray tracing enabled after a patch, an overlay that hooks into the renderer, or a path tracing toggle that pushes the GPU into a driver timeout during loading.

When It Happens Likely Trigger Best First Move
Instant crash on launch Saved settings forcing ray tracing Reset UserSettings.json
Crash while loading a save Path tracing instability Disable path tracing, load again
Crash after a driver update Driver remnants or bad install Run AMD Cleanup Utility, reinstall

AMD And Cyberpunk Ray Tracing Initialization Error Checks That Work

Before you uninstall anything, run a fast pass that rules out the usual tripwires. These steps take minutes and can save you from a full reinstall.

  • Confirm DirectX 12 mode — Launch Cyberpunk with DX12 (the default) and avoid forcing DX11 through custom launch options.
  • Shut down overlays — Turn off overlays in Discord, Steam, Xbox Game Bar, AMD overlay, and any capture tools that hook into games.
  • Pause tuning tools — Close GPU monitoring apps and disable GPU overclocks or undervolts for this test boot.
  • Remove graphics injectors — Temporarily move out ReShade, frame-gen mods, and DLL swap tools from the game folder.
  • Check Windows version — CD Projekt Red notes that older Windows builds can block launches; Windows 10 1909 or newer is a safer baseline.

If the game still crashes right as it tries to initialize ray tracing, the next step is to clear the driver stack and the game’s saved graphics flags. CD Projekt Red’s “The game is not launching” help article points to a clean AMD driver install and overlay shutdown as top fixes.

Clean Install AMD Drivers The Way CDPR Recommends

A normal driver update can leave leftovers behind, especially if you jumped versions or swapped GPU models. Cyberpunk is picky about ray tracing initialization, so you want a clean baseline. CD Projekt Red’s clean-driver steps for AMD calls out the AMD Cleanup Utility, followed by a fresh driver install from AMD.

  1. Download the driver first — Grab the current AMD Adrenalin package for your GPU, then save it to your desktop so it’s ready after cleanup.
  2. Run AMD Cleanup Utility — Use AMD’s cleanup tool to remove old display driver components, then reboot when it prompts you.
  3. Install the driver fresh — Install the driver you downloaded, reboot again, then open AMD Software once to confirm it loads.
  4. Skip extra toggles for now — Leave Radeon overlay and recording off for your first test launch to cut variables.

If the error started right after a new driver, CD Projekt Red also suggests installing the previous driver version and reporting the behavior. That’s a practical move when a game and driver hit a rough patch on one release.

AMD release notes sometimes list Cyberpunk-specific instability. As one recent example, AMD’s Adrenalin 25.12.1 notes a known issue where a crash or driver timeout may happen while loading a saved game in Cyberpunk 2077 with path tracing enabled.

Reset Ray Tracing Without Opening The Game

This is the move that fixes a lot of “crash on launch” cases. Cyberpunk stores graphics settings in a user config file. If ray tracing is stuck on and the game can’t initialize it, you never reach the menu to turn it off.

On Windows, the settings file is commonly stored at C:\Users\YOURNAME\AppData\Local\CD Projekt Red\Cyberpunk 2077\UserSettings.json. PCGamingWiki and long-running user reports point to this location for Cyberpunk’s user settings file.

  1. Back up the file — Copy UserSettings.json to your desktop so you can roll back if you want.
  2. Force a fresh config — Rename UserSettings.json to UserSettings.json.old.
  3. Launch the game — Start Cyberpunk again. It should rebuild a clean settings file with safe defaults.
  4. Turn ray tracing on later — Once you reach the menu, re-enable ray tracing step by step, testing between changes.

If you prefer editing instead of renaming, search inside the file for RayTracing and set the active value to false. Renaming is safer for most people because you avoid a typo that breaks JSON formatting.

This is also a good moment to search the file for path tracing or overdrive flags. If you can’t remember what you last set, assume the saved config is guilty until proven innocent.

Path Tracing And Overdrive Mode Notes

Cyberpunk uses “ray tracing” as an umbrella label for several features, and “path tracing” as an even heavier rendering mode. It matters because your crash may not be ray tracing in general. It might be path tracing in particular.

Know what you turned on

CD Projekt Red’s Overdrive Mode notes says path tracing is set to off by default and is recommended on high-end NVIDIA GPUs. They also note path-traced screenshots can work on other ray tracing capable cards with at least 8 GB VRAM, with higher resolutions needing more VRAM.

Resolution Minimum VRAM For Path-Traced Screenshots
1080p 8 GB
1440p 10 GB
2160p 12 GB

If you’re on an AMD card with ray tracing hardware, standard ray tracing presets can run fine, yet path tracing can still be unstable or too heavy for your current driver and settings. That mismatch shows up as a crash during initialization or while loading a save.

Work around the AMD path tracing timeout

AMD’s Adrenalin release notes have flagged Cyberpunk path tracing as a known crash or timeout scenario on some driver versions. If you hit the crash right when loading a save, treat path tracing as the first suspect.

  • Disable path tracing — Turn off path tracing or Overdrive Mode, then try loading the same save again.
  • Drop the ray tracing preset — Switch from RT Ultra down to a lighter preset, then add features back one at a time.
  • Lower resolution for testing — Use 1080p for a test boot to reduce VRAM pressure while you confirm stability.
  • Restart after changes — Fully quit the game between tests so the renderer re-initializes cleanly.

Once the game is stable, you can raise settings again. Keep one knob per test. If you flip five switches at once, you’ll never know which one caused the crash.

Verify Game Files And Fix Common PC Triggers

If you cleaned the driver and reset settings and the error still shows up, move to game files and system components. CD Projekt Red calls out several launch fixes that apply cleanly to this scenario.

Verify installation files

A corrupted shader cache or broken file can crash at launch, and it can look like a ray tracing problem when the renderer hits missing data. CD Projekt Red’s file verification steps include Steam, GOG, and Epic.

  • Verify on Steam — Open Properties, go to Installed Files, then run Verify integrity of game files.
  • Verify on GOG — Use Manage installation, then Verify/Repair.
  • Verify on Epic — Use the game menu, pick Manage, then run Verify.

Reinstall Microsoft Visual C++ packages

CD Projekt Red’s launch checklist includes reinstalling Microsoft Visual C++ Redistributable packages (x86 and x64). When these files are damaged or missing, games can fail early in the boot process.

Run the launcher with admin rights

It sounds basic, yet it can help when the launcher can’t write a fresh settings file after you renamed it. Try running Steam, GOG Galaxy, or Epic as an administrator for one test launch.

Disable extra background tools

Some tools hook into graphics calls and can interfere with ray tracing initialization. This includes overlays, capture apps, RGB utilities, hardware monitors, and some antivirus setups.

  • Turn off capture utilities — Close screen recorders and GPU overlays before you launch.
  • Exit monitoring apps — Shut down MSI Afterburner, RTSS, and similar tools for this test.
  • Test a clean boot — Restart Windows and launch Cyberpunk before opening other apps.

If the game launches cleanly with everything closed, add your usual tools back one by one. You’ll find the troublemaker faster than guessing.

Turn Ray Tracing Back On Without Rebreaking Launch

Once you can reach the main menu, don’t jump straight into the heaviest preset. Treat it like a controlled setup, not a dare.

  1. Start with ray tracing off — Load into the game, move around for a minute, then exit normally.
  2. Enable basic ray tracing — Turn on a single ray tracing feature, then load the same save.
  3. Watch for driver timeouts — If the driver resets or the game closes, back off the last change.
  4. Keep path tracing last — Leave path tracing and Overdrive for the final step, after everything else is stable.

If the amd and cyberpunk ray tracing initialization error returns the moment you enable a specific ray tracing option, keep that option off for now and play. A stable game beats a perfect screenshot.

If It Still Crashes, Collect The Right Details

When none of the steps above work, the problem may be deeper than settings and drivers. At this point, you want clean data you can hand to the game’s help form or use for your own debugging.

  • Note the exact moment — Does it crash on launch, on loading a save, or right after the menu appears?
  • Record your driver version — Write down the AMD Software version and Windows build number.
  • Generate a DxDiag — CD Projekt Red links to DxDiag instructions in their PC technical pages, and it helps identify driver and OS details.
  • Test with a new save — Start a new game briefly to see if only one save triggers the crash.

With this order—clean driver install, reset settings, then re-enable ray tracing in steps—you can squash the amd and cyberpunk ray tracing initialization error and get into Night City.