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


Iracing Log File Location for Crashes

Need the iracing log file location for crashes? This guide shows exact paths, how to collect logs, and quick fixes so iRacing drivers can solve issues fast.


If you’re looking for the iracing log file location for crashes, here’s the short answer: check your Documents\iRacing folder for logs and Windows’ CrashDumps for .dmp files. You’re in the right place—below are the exact paths and quick steps to collect logs and fix common crash causes.

Quick Answer: iracing log file location for crashes

  • iRacing logs: C:\Users\YourName\Documents\iRacing\ (often in a “logs” subfolder; sort by Date Modified and look for .log or .txt files)
  • Windows crash dumps: %LOCALAPPDATA%\CrashDumps\ (look for iRacingSim64DX11.exe*.dmp)
  • Windows events: Event Viewer > Windows Logs > Application (faulting module and error details)

Tip: Press Win+R and paste %LOCALAPPDATA%\CrashDumps to jump straight to the dumps folder.

What’s Really Going On

iRacing doesn’t always create a single “crash.log.” When the sim crashes, Windows usually writes a mini-dump (.dmp) in the CrashDumps folder. iRacing also writes general logs (UI, network, renderer) under Documents\iRacing, sometimes in a logs subfolder. Together, these files show what failed—often a graphics driver, overlay, audio device, or a plugin.

Step-by-Step Fix

  1. Collect the sim logs
  • Close iRacing.
  • Go to C:\Users\YourName\Documents\iRacing.
  • If you see a logs folder, open it; otherwise, sort the folder by Date Modified and grab the newest .log/.txt files.
  1. Collect the crash dump
  • Press Win+R, paste %LOCALAPPDATA%\CrashDumps, press Enter.
  • Copy any iRacingSim64DX11.exe*.dmp created at the time of the crash.
  1. Check what actually failed
  • Open “Reliability Monitor” (search “reliability” in Start).
  • Click the red X for the crash, then View technical details. Note the Faulting module (often a GPU driver or overlay).
  1. Quick stability sweep
  • Update your graphics driver (clean install if possible).
  • Disable overlays and recorders (RivaTuner/RTSS, MSI Afterburner, Discord overlay, GeForce Experience overlay, ReShade).
  • Unplug/replug or switch problematic audio devices; set a single default output.
  1. Reset iRacing graphics configs (safe reset)
  • In Documents\iRacing, rename rendererDX11.ini and app.ini to .bak.
  • Launch iRacing; it will rebuild fresh configs.
  1. Verify and test
  • Re-launch the sim in a Test Session first.
  • If stable, re-enable tools one by one to find the culprit.
  • If crashes persist, attach the logs and .dmp to a support ticket.

Extra Tips / Checklist

  • Borderless window or full-screen exclusive? If crashes happen alt-tabbing, try borderless.
  • USB hubs can cause power hiccups—plug your wheel/pedals direct to the motherboard.
  • Don’t overclock the GPU/VRAM while troubleshooting.
  • Keep Windows up to date; many DX11/driver fixes ship via Windows Update.
  • If CrashDumps is empty, Windows may not have generated one—Reliability Monitor and Event Viewer still help.

FAQs

Q: Where exactly is the iRacing log folder?
A: Go to C:\Users\YourName\Documents\iRacing. Many builds create a logs subfolder there. If not, sort the Documents\iRacing folder by date and look for recent .log or .txt files.

Q: Where are iRacing crash dumps stored?
A: Windows writes them to %LOCALAPPDATA%\CrashDumps\ as iRacingSim64DX11.exe… .dmp files.

Q: Which files should I send to iRacing Support?
A: The newest logs from Documents\iRacing (and its logs folder) plus the matching .dmp from %LOCALAPPDATA%\CrashDumps. Adding a DxDiag.txt also helps.

Q: CrashDumps is empty—what now?
A: Use Reliability Monitor and Event Viewer for error details. Some systems don’t generate dumps for every crash.

Short Wrap-Up

You’ll find iRacing’s logs under Documents\iRacing and crash dumps under %LOCALAPPDATA%\CrashDumps. Grab those, run the quick fixes above, and test in a solo session before jumping back into races.