Join hundreds of racers just like you! We love to help answer questions and race together.
Iracing Crashes When Loading Session
iRacing drivers: Fix ‘iracing crashes when loading session’ fast. Simple steps to update drivers, repair files, and stop overlay conflicts so you can load and race.
If you’re seeing iracing crashes when loading session, the usual causes are a bad graphics cache, a driver or overlay conflict, or a corrupt install. The quick fix is to reset iRacing’s graphics files, update your GPU driver, and verify the game files. You’re in the right place—follow these steps.
Quick Answer: iracing crashes when loading session
Most crashes during the loading screen come from broken shaders/settings, outdated GPU drivers, or conflicts with overlays/monitoring tools. Reset the iRacing graphics cache, clean-install the latest NVIDIA/AMD driver, disable overlays, and run the iRacing updater to repair files. This solves it for most drivers.
What’s Really Going On
When you join a session, iRacing compiles shaders and loads car/track assets. If those cache files are corrupted, the sim can crash mid-load. The same happens if your graphics driver is unstable or third-party overlays hook into iRacing in a bad way.
Less often, a specific car/track file gets corrupted, or a VR runtime mismatch causes a crash. Fixes target those spots first because they’re fast and safe.
Step-by-Step Fix
Reset iRacing’s graphics cache
Close iRacing. Go to Documents\iRacing and delete (or rename) rendererDX11.ini and the shaders folder. iRacing will rebuild them on next launch.Update your GPU driver (clean install)
Download the latest driver from NVIDIA or AMD. Choose a clean install option (or use the vendor tool) to remove old components that can cause crashes.Repair iRacing files
Open the iRacing UI and check Updates (or run the iRacing installer/updater) to re-scan and repair content. This replaces any broken car/track files and runtimes.Disable overlays and background tools
Turn off Discord overlay, GeForce Experience overlay, MSI Afterburner/RivaTuner, Overwolf, SimHub overlays, browser overlays—anything that hooks graphics. Then launch iRacing as administrator.Try safer iRacing settings
In iRacing settings, set Full Screen (or try Windowed/Borderless as a test), limit frame rate, lower Max Cars, and use a lower graphics preset. These iRacing settings reduce load spikes that can trigger crashes.VR check (if applicable)
Make sure your OpenXR/SteamVR runtime matches what you launch. Test launching without VR (monitor mode) to confirm if VR is the cause. Update headset software/firmware.
If it still crashes, unplug non-essential USB devices (extra rims, button boxes) and try again—faulty drivers sometimes trip the load process.
Extra Tips / Checklist
- Test a different track/car. If only one combo crashes, re-download that content via Updates.
- Add iRacing’s folder to your antivirus exclusions; real-time scanning can kill the load.
- Windows Update: install pending updates and reboot.
- Wheelbase firmware: update via your manufacturer’s tool (Fanatec, Simucube, Thrustmaster).
- Logs for support: Documents\iRacing\logs (look for crash.txt and logitech, graphics logs).
FAQs
Why only official races, not Test Drive?
Official sessions load more cars and assets. That extra load exposes driver/overlay issues. The same fixes above apply.Will reinstalling iRacing fix this?
Sometimes, but it’s slower. Resetting shaders, updating GPU drivers, and repairing via the updater usually works. Reinstall only if those fail.Where are crash logs for iRacing support?
Go to Documents\iRacing\logs. Zip the folder and attach it when you open a ticket. Include what you tried and the exact car/track.VR only: it crashes when loading the grid—what now?
Confirm your OpenXR/SteamVR runtime matches your launch method, update VR software, and test without VR. Many VR crashes are overlay or runtime conflicts.
Short version: clear iRacing’s cache, clean-install your GPU driver, repair game files, and run without overlays. These iRacing tips resolve most loading crashes fast.
