Join the Discord! →

Join hundreds of racers just like you! We love to help answer questions and race together.


Iracing Crashes After Latest Update

iRacing drivers: if iracing crashes after latest update, this guide shows why it happens and gives fast, clear steps to fix it now and get back on track. Today.

If iracing crashes after latest update, the usual causes are a bad graphics cache or settings, an overlay conflict, or a driver mismatch. You’re in the right place. Follow these quick steps to fix it fast and get back on track.

Quick Answer

Most “iracing crashes after latest update” cases come from corrupted graphics cache/settings, outdated GPU drivers, or third‑party overlays hooking the game. Update your graphics driver, run iRacing’s Repair, reset graphics files, and disable overlays. If it still crashes, re-download the problem track/car and check VR/antivirus conflicts.

Why iracing crashes after latest update happens

Updates change how iRacing loads graphics and content. Old shader files or graphics configs can break after a patch. GPU drivers may need a refresh to match new rendering changes. Overlays (Discord, Steam, GeForce Experience, RivaTuner, SimHub, Fanalab) can conflict with the updated executable. Sometimes a single track or car file corrupts during the patch. VR is another common trigger: a change in OpenXR/SteamVR/WMR can crash the sim at launch or when joining a session.

Step-by-Step Fix

  1. Reboot everything
    Restart your PC and power-cycle your wheel base/pedals. It clears driver/device hiccups from the update.

  2. Update GPU drivers (clean install)
    Install the latest NVIDIA/AMD driver. Choose Clean Install if offered. Reboot after.

  3. Repair iRacing install and content
    Open the iRacing UI > Settings/Updates (or Downloads) > click Repair/Force Update to verify and re-download missing or broken files.

  4. Reset graphics settings and cache
    Close iRacing. Go to Documents\iRacing. Delete the “shaders” and “shadercache” folders. Rename app.ini and rendererDX11.ini to .bak (iRacing will rebuild fresh ones). Launch iRacing and run Graphics “Auto Config.”

  5. Disable overlays and background hooks
    Turn off Discord overlay, Steam overlay, GeForce Experience overlay, MSI Afterburner/RivaTuner (set Application Detection Level to None), SimHub game hooks, Fanalab LED plugins. Try launching iRacing again.

  6. Isolate VR (if you use it)
    Launch on the monitor (non‑VR) from the UI. If it works, update your VR runtime (SteamVR/OpenXR/WMR), pick one runtime (don’t mix), and re-enable VR after confirming stability.

Extra Tips / Checklist

  • Re-download any track/car that consistently crashes on load (via the Updates/Content manager).
  • Add the iRacing folder to your antivirus exclusions; some suites quarantine sim64dx11.exe after patches.
  • Install the latest Microsoft Visual C++ 2015–2022 x64 runtime and ensure Windows Updates are current.
  • In iRacing settings, cap FPS and avoid experimental graphics options until stable.
  • Still crashing? Grab logs from Documents\iRacing\logs and open a support ticket; include a DxDiag report.

FAQs

Q: iRacing only crashes when joining a session—menus are fine. Why?
A: That points to graphics cache/content issues. Clear the shaders folders, run Auto Config, and re-download the specific track/car that triggers the crash.

Q: How do I fully reset my iRacing settings?
A: Close iRacing, go to Documents\iRacing, rename app.ini and rendererDX11.ini to .bak, then relaunch and run Graphics Auto Config. This rebuilds clean defaults.

Q: Can overlays really crash iRacing?
A: Yes. After updates, overlays and OSD tools can hook the new executable poorly. Disable Discord/Steam/GeForce overlays and any RivaTuner/SimHub/Fanalab hooks to test.

Q: Should I reinstall iRacing?
A: Usually not. The Repair/Force Update tool fixes most issues. Consider a full reinstall only if repair and cache resets don’t help.

Wrap-Up

Most post-update crashes come down to drivers, overlays, or stale graphics files. Work through the steps above in order; you’ll usually fix it within minutes. Once stable, run a short test session to confirm before your next official race.