Installed track or vehicle content cannot be read/decompressed
MAS decompression, missing mesh/scene, or affected Installed\Locations / Installed\Vehicles package references near the failure.
Approval requiredView diagnostic →
PitMedic
PitMedic Diagnostic Library
Search known sim-racing errors, launch failures, crashes, configuration problems, and companion-software issues. Each guide explains diagnostic evidence, available repairs, or version-specific manual checks.
65diagnostic, repair and guidance records
Start with your error message
These guides include manual steps, expected results, and when to stop.
65 records shown
Stale/corrupt shader cache or loading failure
Loading failures around track/car initialization without package corruption; repeated shader/cache errors or known 48% load behavior.
Automatic repair availableView diagnostic →
Startup / black-screen / early initialization failure
LMU exits during early configuration or CEF/video initialization before a session begins.
Automatic repair availableView diagnostic →
Third-party plugin conflict
Crash occurs with plugin-related trace evidence or after enabling a known plugin; no stronger hardware/content fault is present.
Automatic repair availableView diagnostic →
Overlay / hook / tuning software conflict
LMU loading crash while MSI Afterburner / RivaTuner or similar hook software is running, especially when no stronger content fault exists.
Automatic repair availableView diagnostic →
Logitech G Hub compatibility/version issue
LMU launch failure with G Hub running and no stronger signature; only suggest when installed version/state is known.
Guided diagnosisView diagnostic →
Virtual memory / page-file allocation failure
Trace contains 'Failed to allocate a section of memory' or Windows commit pressure is exhausted near the failure.
Approval requiredView diagnostic →
Easy Anti-Cheat installation/startup failure
LMU trace or launch state reports Easy Anti-Cheat/EAC missing, failed, or not installed.
Approval requiredView diagnostic →
Unsupported ReShade/custom runtime prevents launch
Early launch failure or 0xc000007b plus ReShade/custom graphics runtime files in the LMU application directory.
Approval requiredView diagnostic →
Unable to join online sessions
RaceControl connection/join failure without local loading crash; compare Windows time settings and EAC launch state.
Guided diagnosisView diagnostic →
iRacing Helper Service stopped / UI cannot launch
iRacing.com Helper Service absent or stopped while UI launch fails or reports Not In Service.
Automatic repair availableView diagnostic →
iRacing UI black/white screen, frozen UI, or stale Electron cache
UI process remains alive but fails to render/respond; logs point to Electron/UI state rather than simulator crash.
Automatic repair availableView diagnostic →
iRacing UI stuck on Welcome to iRacing
UI startup stuck/crashing with the supported UISafe setting present in app.ini.
Automatic repair availableView diagnostic →
Easy Anti-Cheat Error 73 / anti-cheat installation failure
Error 73 or explicit EAC/EOS anti-cheat failure near simulator startup.
Approval requiredView diagnostic →
Update verification failure
A fresh verification failure is reported after the iRacing updater has closed and its 30-second settling period has ended. Transient verification checks during an active update are not repair findings.
Automatic repair availableView diagnostic →
Corrupt/missing vehicle content
Specific car data fails in the UI/3D viewer while other content works.
Automatic repair availableView diagnostic →
Could not find sim
UI reports Could not find sim; correlate VR/OpenXR Toolkit, duplicate installations, OneDrive Documents path, and Windows UTF-8 beta setting.
Guided diagnosisView diagnostic →
Steam Content File Locked during iRacing update
Steam reports Content File Locked while updating iRacing and the Helper Service is running.
Approval requiredView diagnostic →
Steam Missing File Privileges during an iRacing update
Steam reports Missing File Privileges for iRacing while the iRacing Helper Service may still hold installed files open.
Approval requiredView diagnostic →
Loading Error 49 / 61 / 62 / 72 and damaged track content
iRacing reports a numbered track loading error or a track-specific content failure during sim launch.
Automatic repair availableView diagnostic →
Loading Error 22 / 71 and damaged car content
iRacing reports Loading Error 22/71 or car-data corruption while other content remains available.
Automatic repair availableView diagnostic →
Loading Error 3 / damaged user configuration
iRacing reports Loading Error 3 after simpler car/track causes have not produced a more specific signature.
Approval requiredView diagnostic →
iRacing is already running / simulator failed to close
iRacing reports the simulator is already running or a stale simulator process remains after exit.
Approval requiredView diagnostic →
Failed CreateProcessAsUser / incompatible Windows compatibility override
Launch log reports CreateProcessAsUser failure or Windows compatibility mode/admin override is applied to iRacing executables.
Automatic repair availableView diagnostic →
Updater stuck waiting for iRacingService
Updater log/UI reports Waiting for iRacingService while downloaded update files are ready to install.
Automatic repair availableView diagnostic →
Digital Signature Failed during update/startup
iRacing reports Digital Signature Failed while the UI/updater is involved.
Automatic repair availableView diagnostic →
Repeated 0xc0000005 / Windows application access-violation failure
Windows/iRacing records a repeatable application fault or 0xc0000005 without a more specific content, driver, thermal, or service signature.
Approval requiredView diagnostic →
Graphics configuration / renderer settings corruption
Graphics Config crashes or rendererDX11 settings are implicated without stronger GPU driver evidence.
Automatic repair availableView diagnostic →
Broken video settings / graphics startup state
Assetto Corsa EVO exits during startup or logs point to video/graphics initialization. A Video.videosettings file exists in the ACE user-data folder.
Automatic repair availableView diagnostic →
Corrupt ACE user profile / launch state
Repeated early launch crash or black/white startup failure without a stronger hardware/driver signature after a targeted video reset is not enough.
Approval requiredView diagnostic →
Missing or damaged Steam game files
Assetto Corsa EVO logs or Windows evidence indicate missing/corrupt local game files or a failed asset load without a more specific repair signature.
Approval requiredView diagnostic →
Browser cache / Error 503 / UI loading problem
RaceRoom reports Error 503, CEF/browser loading errors, or the browser UI fails while the game process remains otherwise functional.
Automatic repair availableView diagnostic →
Broken graphics / resolution configuration
RaceRoom cannot display correctly, minimizes on launch, shows black output after a GPU/display change, or graphics_options.xml is implicated.
Automatic repair availableView diagnostic →
Shader cache corruption
RaceRoom logs point to shader compilation/cache errors or graphics behavior persists despite normal configuration.
Automatic repair availableView diagnostic →
Damaged RaceRoom user configuration
Repeated startup/loading failure remains after targeted cache/config repairs and evidence points to UserData configuration corruption.
Approval requiredView diagnostic →
Missing or damaged Steam game files
RaceRoom logs or Windows evidence indicate missing/corrupt local content or verification-related failures.
Approval requiredView diagnostic →
Broken display or startup settings
ACC log evidence names GameUserSettings.ini, resolution, or fullscreen configuration near a startup/display failure.
Automatic repair availableView diagnostic →
Unreal Engine or graphics configuration failure
ACC logs identify Engine.ini, DXGI device loss, a rendering-thread exception, or a GPU crash without a stronger content signature.
Automatic repair availableView diagnostic →
Damaged controller or wheel configuration
ACC reports invalid controller, DirectInput, wheel, or controls.json state around a Controls-menu or input failure.
Approval requiredView diagnostic →
Invalid or damaged force-feedback settings
ACC log evidence identifies FFB or ffbUserSettings.json as failed, invalid, or unreadable.
Approval requiredView diagnostic →
Logitech TrueForce or manufacturer-library conflict
ACC reports TrueForce, manufacturer extras, or wheel-library failure near a controller-related crash.
Approval requiredView diagnostic →
Saved control preset crashes the Controls menu
ACC identifies a saved Customs\Controls preset as invalid or failed immediately before a Controls-menu crash.
Approval requiredView diagnostic →
Damaged ACC user configuration
Repeated startup failure remains after targeted repairs and ACC reports corrupt or unparseable configuration state.
Approval requiredView diagnostic →
Missing or damaged ACC game files
ACC explicitly reports a missing, corrupt, or unreadable game package or asset rather than a driver, Windows, or optional plugin file.
Approval requiredView diagnostic →
Broken graphics or display configuration
AMS2 evidence identifies graphicsconfigdx11.xml near a display, startup, or settings failure.
Automatic repair availableView diagnostic →
Broken OpenVR or Oculus configuration
AMS2 evidence names OpenVR, Oculus, or the related graphics/settings XML files near a VR startup failure.
Approval requiredView diagnostic →
Controller input or calibration is lost
AMS2 evidence identifies controller settings or default.controllersettings.v1.03.sav after an update, USB-port change, or driver change.
Approval requiredView diagnostic →
Damaged custom force-feedback configuration
AMS2 evidence names ffb_custom_settings.txt near a force-feedback initialization or parsing problem.
Approval requiredView diagnostic →
Car setups are incompatible after a physics update
AMS2 evidence points to tuning setup or vehiclesetups data while an affected car or setup fails after an update.
Approval requiredView diagnostic →
Corrupted custom championship state
A championship or singlechamps save file changed immediately before a Championship-mode failure and no stronger system fault is present.
Approval requiredView diagnostic →
Damaged default profile settings
AMS2 reports profile corruption involving default.sav rather than the controller-specific profile file.
Approval requiredView diagnostic →
Damaged Automobilista 2 user profile
Repeated startup failure remains after targeted repairs and AMS2 evidence identifies corrupt, invalid, or unparseable profile state.
Approval requiredView diagnostic →
Missing or damaged Automobilista 2 game files
AMS2 evidence explicitly reports a missing, corrupt, or unreadable game file or package.
Approval requiredView diagnostic →
Released crash, team-sync and RaceHub data fixes
Compare the installed LMU build and session context; a generic crash or long join does not establish a vendor-known cause.
Guided diagnosisView diagnostic →
SimPro startup conflicts and RaceHub display data
Check which companion app is running and distinguish an EVO startup failure from incorrect peripheral display data.
Guided diagnosisView diagnostic →
Wheel or paddles stop responding: Steam Input check
Manual check for a wheel/paddle input problem; not a generic crash diagnosis or an automatic setting change.
Guided diagnosisView diagnostic →
Tuner startup GPU use, saving crashes and pedal mapping
Identify Simucube Tuner and its installed version manually. PitMedic's monitored True Drive process set is separate and does not detect or restart Tuner.
Guided diagnosisView diagnostic →
Reference Car Input display and spotter audio fixes
Compare the iRacing build and exact display/audio symptom. These patch notes do not provide a crash signature.
Guided diagnosisView diagnostic →
Recover MOZA Pit House
Confirmed crash or stale-process clean recovery
Approval requiredView diagnostic →
Recover Simucube True Drive
Confirmed crash or stale-process clean recovery
Approval requiredView diagnostic →
Recover Fanatec software
Confirmed app fault and process-set recovery
Approval requiredView diagnostic →
Recover Logitech G HUB
Loading-loop, agent-fault, and updater-service recovery
Approval requiredView diagnostic →
Recover SIMAGIC SimPro Manager
SimPro 2/3 conflict, daemon, crash, and stale-process recovery
Approval requiredView diagnostic →
Recover Asetek RaceHub
RaceHub app and elevated-helper clean recovery
Approval requiredView diagnostic →
Recover VRS DirectForce
Confirmed configuration-app crash or stale-process recovery
Approval requiredView diagnostic →
No matching diagnostic records. Try a broader search or clear a filter.