Project Motor Racing Keeps Crashing: Fixes for PC, PS5, and Xbox

Project Motor Racing crashes typically stem from startup loading freezes, DirectStorage DLL conflicts, aggressive GPU driver profiles, or unstable third-party overlays. Straight4 Studios and publisher GIANTS Software built the simulation on GIANTS Engine 10, which requires DirectX 12 and strict hardware overhead. Resolving these stability failures requires verifying core files, adjusting render launch parameters, disabling overlay hooks, or tuning platform cache reserves.

Quick Diagnostic Matrix

Before applying advanced operating system changes, match your platform and symptoms against the common causes identified across player logs and system reports:

PC and Steam Crash Solutions

Verify Game Files and Run as Administrator

Corrupted installation files frequently cause Project Motor Racing to close silently without generating an error code.

1. Launch Steam and open your Library.
2. Right-click Project Motor Racing and select Properties.
3. Navigate to the Installed Files tab and click Verify integrity of game files. Wait for Steam to scan and download missing assets.
4. Open the game's local installation directory by selecting Manage and clicking Browse local files.
5. Right-click ProjectMotorRacingGame.exe and select Properties.
6. Under the Compatibility tab, check Run this program as an administrator and Disable full-screen optimizations.
7. Click Apply, then OK.

Force DirectX Launch Commands

If your graphics card struggles with the default DirectX 12 render pipeline, you can force Steam to adjust the rendering protocol.

1. Open your Steam Library.
2. Right-click Project Motor Racing and open Properties.
3. In the General tab, locate the Launch Options input field.
4. Type -dx11 and attempt to boot the game.
5. If the game still fails or performs poorly, replace the text with -dx12 to ensure proper DirectX 12 initialization.

Turn Off Overlays and Background Capture

Overlay hooks from communication and recording utilities are a documented source of crashes in GIANTS Engine 10 titles.

1. In Steam, click Steam in the top menu, open Settings, select In-Game, and uncheck Enable the Steam Overlay while in-game.
2. Open the NVIDIA GeForce Experience application, click the Settings gear icon, navigate to the General tab, and turn off the In-Game Overlay.
3. In Discord, navigate to User Settings, click the Game Overlay tab under Activity Settings, and disable Enable in-game overlay.
4. Close third-party monitoring utilities such as MSI Afterburner and RivaTuner Statistics Server before launching a race.

Reset Triple Screen Configuration in game.xml

Enabling the in-game triple screen setting can cause immediate startup crashes when booting on certain multi-monitor or surround setups.

1. Navigate to your local document directory: Documents/My Games/ProjectMotorRacing/.
2. Open game.xml using a standard text editor.
3. Locate the tripleScreen entry: <tripleScreen ... enabled="true"/>.
4. Change enabled="true" to enabled="false".
5. Save the file and restart the game on a single standard display resolution (such as 2560x1440 or 1920x1080) before re-calibrating.

Graphics Settings and Hardware Tuning

Player reports on the official Steam discussions indicate that Project Motor Racing places heavy demands on both system RAM and graphics card pipelines, particularly on AMD Radeon cards (such as the RX 6800, RX 6800 XT, and RX 6950 XT).

In-Game Graphical Adjustments

• Drop Presets from Ultra to Very High: Several community members confirmed that reducing overall graphics from Ultra to Very High eliminates memory-related race crashes during career sessions.
• Lower Render Resolution: If running at 4K causes driver timeouts within the first few laps, drop the resolution to 1440p (2560x1440) or 1080p (1920x1080) to decrease frame buffer pressure.
• Check Official System Requirements: Minimum specifications require at least an Intel Core i7-8700 or AMD Ryzen 5 with a minimum of 12 threads, 16 GB RAM, and an NVIDIA RTX 2060 or AMD Radeon RX 580 (6 GB VRAM minimum). The recommended spec requires 24 GB of RAM and an NVIDIA RTX 3070 or AMD Radeon RX 6800. Older hardware like the GTX 1080 Ti fails to launch the game reliably.

System Memory and Driver Configuration

• Manage Frame Rate Caps: In the AMD Adrenalin software, activating Radeon Chill and configuring a dynamic cap (such as 60 FPS idle and 100 FPS maximum) has resolved intermittent race CTDs for an RX 6800 user.
• Tone Down Memory Overclocks: If your system uses aggressive XMP or EXPO profiles, dropping memory speeds slightly (for example, from 3600 MHz to 3400 MHz) stabilizes the simulation against random Event ID 1000 application errors.
• Disable CPU Curve Optimizer: Users running AMD Ryzen processors who experience crashes every 10 to 15 minutes have reported full stability after disabling Curve Optimizer or custom CPU overclocks in BIOS.
• Adjust Windows Virtual Memory: Search for "View advanced system settings" in the Windows search bar. Go to the Advanced tab, click Settings under Performance, choose Advanced, and click Change under Virtual Memory. Select your installation drive, choose Custom size, set the Initial size to 1 28 and the Maximum size to 2 4 5 76, click Set, and restart your computer.

PlayStation 5 Troubleshooting

PlayStation 5 players encountering launch freezes, blank loading screens, or sudden quits can resolve local data corruption using console recovery tools.

Clear System Cache and Rebuild Database

1. Turn off your PS5 completely by holding the power button until the console beeps and shuts down.
2. Press and hold the console power button again until you hear a second beep roughly seven seconds later, which boots the system into Safe Mode.
3. Connect your DualSense controller via USB cable and press the PS button.
4. Select Clear Cache and Rebuild Database.
5. Choose Rebuild Database. This process reorganizes drive indexes without deleting your game data.

Restore Game Licenses

1. Go to PS5 Settings from the home menu.
2. Select Users and Accounts, then choose Other.
3. Select Restore Licenses.
4. Highlight Project Motor Racing and confirm Restore.

Toggle HDCP

1. Go to Settings and choose System.
2. Select the HDMI submenu.
3. Toggle Enable HDCP to off, launch the game, and verify stability. If black screen issues continue, switch the setting back on.

Xbox Series X|S Troubleshooting

Xbox users dealing with sudden crashes to the dashboard or loading screen hangs should clear local device storage caches.

Clear Reserved Space

1. Press the Xbox button on your controller, highlight My games & apps, and select See all.
2. Locate Project Motor Racing, press the Menu button, and select Manage game and add-ons.
3. Select Saved data.
4. Highlight Reserved space and select Clear reserved space.

Wipe Blu-ray Persistent Storage

Even for digital copies, clearing persistent disc storage empties hidden temporary cache partitions that cause simulation launch failures.

1. Open Xbox Settings and select Devices & connections.
2. Choose Blu-ray.
3. Select Persistent storage and click Clear persistent storage.

Reset Alternate MAC Address

1. Open Xbox Settings and navigate to General, then Network settings.
2. Select Advanced settings.
3. Choose Alternate MAC address and select Clear.
4. Allow your console to restart automatically.

Frequently Asked Questions

Why does Project Motor Racing crash to the desktop without an error code?

Silent CTDs usually occur when the GIANTS Engine 10 encounters an access violation (such as Windows Event ID 1000 with exception code c0000005), often linked to DStorageCore.dll, outdated GPU drivers, or an unstable RAM overclock. Verifying Steam files and disabling background overlays resolves most silent crashes.

Does Project Motor Racing support older graphics cards like the GTX 1080 Ti?

Players on legacy cards such as the GTX 1080 Ti report that the game will not run.

Where are the Project Motor Racing crash logs stored on PC?

You can check crash and game activity logs by navigating to C:\Users\<YourUsername>\Documents\My Games\ProjectMotorRacing\ and opening the Log.txt file in any text editor. Inspect the bottom lines of the document to identify which asset or system call failed prior to the shutdown.