The game crashes on startup

A crash before you reach story mode almost always comes from the last thing you changed. If you know what that was, take it out and try again. If you don't, split the problem in two.

First question

Did the game update? If it ran yesterday and you changed nothing, see The game crashes after a Rockstar update.

Split the problem

Mods load in two separate ways: archives through the mods folder, and scripts through the ASI loader. Switch each off in turn.

1. Rename mods to mods_off and start the game.
   • It starts: the fault is in an archive or an add-on pack. Rename the folder back and go to the section on the mods folder below.
   • It still crashes: rename the folder back and go to step 2.
2. Move dinput8.dll out of the game folder and start the game.
   • It starts: the fault is a script. Put the file back and go to the section on scripts.
   • It still crashes: go to step 3.
3. Verify the game files through your launcher. A game file is damaged, or was changed outside mods.

When the mods folder is the cause

Work through these in order.

1. Check dlclist.xml. Open mods\update\update.rpf\common\data\dlclist.xml in OpenIV. Every line should have its opening and closing Item tags, and every pack named should exist in mods\update\x64\dlcpacks\.
2. Remove the newest add-on. Delete its line, save and test.
3. Check gameconfig.xml. With several add-on packs, a crash during the loading screen points to the game's limits. Install a gameconfig.xml made for your game version. See dlclist.xml and dlcpacks.
4. Refresh update.rpf. If the copy in mods is older than the game's, replace it. See My mods folder stopped working.

When a script is the cause

1. Move every .asi file except OpenIV.asi out of the game folder, and rename the scripts folder to scripts_off.
2. Start the game. If it runs, put the files back a few at a time until it crashes again. The last batch holds the culprit.
3. Open ScriptHookV.log and asiloader.log in the game folder. The last lines before the crash often name the file that failed.

For LSPDFR, start the game without going on duty. If it crashes only when you go on duty, a plugin in plugins\LSPDFR\ is at fault. Move them out and add them back the same way. RagePluginHook.log names the plugin that threw the error.

Common error messages

• A ScriptHookV message about an unknown or unsupported game version. The game is newer than ScriptHookV. See the article on crashes after an update.
• A corrupt game data message that asks you to reinstall. An archive in mods is damaged or out of date. Replace it from the game folder.
• An out of memory error during loading. Too many add-ons for the game's limits, or textures that are too large.

Nothing above helped

Rename both mods and scripts, move every added .asi and .dll out, and verify the game. Once the clean game starts, add your mods back one at a time, starting the game between each.

Also check that BattlEye is off. With it on, the game may refuse to start with added files in its folder.