Troubleshooting
Marvel Rivals crashing with mods? Find the mod that did it
When Marvel Rivals crashes with mods installed, the hard part is knowing which mod did it, because the game's own crash window doesn't say. RIVALSFPS.GG 5.5.0 does: when the game crashes, it names the mod the game was loading and turns it off in one click, and after every launch each mod in the Mod Manager says whether the game loaded it.
Why mods crash the game
A mod replaces some of the game's own files, such as a hero's model, effects or textures. When a game update changes those files, a mod made for the old version can crash the game the moment it loads, which is why crashes often come on a hero pick, in the lobby or when one ability plays. A mod can also be broken on its own, whatever the game version.
What the crash popup tells you
Keep RIVALSFPS.GG running while you play; minimized or in the tray is fine. When the game crashes, the app comes to the front with Marvel Rivals crashed. What it says depends on what it could find:
| The popup says | What to do |
|---|---|
| One of your mods replaces the file it crashed on | Press Turn it off and launch again |
| Several of your mods replace it | Press Open Mod Manager and turn them off one at a time |
| It came from one of your RIVALSFPS graphic packs | Press Rebuild it if the game has updated since the pack was built, otherwise Turn it off and tell us in Discord |
| None of your mods replace that file | It looks like the game itself. See when no mod is named |
A named mod is a suspect, not a verdict. The game can crash on a file for its own reasons, and the popup says so. Turning the mod off and playing the same hero or map again is the quickest way to find out: if the crash is gone, that mod was it.
The Crashed badge
When a crash names exactly one mod, that mod gets a red Crashed badge on its row in the Mod Manager, so you can find it again after the popup is gone. Hover it for when the crash happened. The badge stays if you turn the mod off, because the mod would crash the same way once it is back on. It clears by itself when:
- the mod's files change, for example when you install an update of it;
- you remove the mod;
- a later crash takes its place, on whichever mod that crash names;
- a launch loads the mod and the game closes normally.
Did the mod load at all?
After every launch, each mod that was on says Loaded or Not loaded in the Mod Manager, based on what Marvel Rivals itself reports. A note beside Import sums it up, such as "Last launch: 7 of 8 mods loaded."
A mod marked Not loaded is unlikely to be the one crashing the game, since the game didn't load it. If it's also marked Outdated, press Fix. If you turned the mod on after the game started, it loads next time. Mods that are switched off show neither badge. For everything else that stops a mod loading, see Marvel Rivals mods not working.
When no mod is named
Sometimes the game crashes on a file none of your mods replace, or the crash doesn't say what it was loading. Then find the mod by halves:
- Save the mods you have on now with Profiles > Save current as…, so you can put them all back in one click. See mod profiles.
- Open Tools and pick Disable All Mods, which turns off your mods, your skins and the app's graphic packs so the game runs stock. If it still crashes, mods aren't the cause: use Verify Game Files in Settings, on the Diagnostics tab.
- Turn half your mods back on, launch and play until the crash would happen. Keep halving whichever side crashes until one mod is left.
- When you're done, open Profiles and click the profile you saved to put your mods back. Profiles don't cover the app's graphic packs, so turn those back on in the Graphic Packs tab.
Crash Reports, also on the Diagnostics tab, lists your recent crashes in words, with the mod each one matched. Those matches use the mods you have installed now, so an older crash may have happened with a different set. Open Crash Reports opens the game's crash folder; zip the newest folder in it when you make a ticket in our Discord.
Common questions
Why does Marvel Rivals crash with mods installed?
A common cause is a mod made for an older version of the game. Game updates change the files mods replace, and a mod built against the old ones can crash the game when it loads, often on a hero pick, in the lobby or when an ability plays.
How do I find out which mod is crashing Marvel Rivals?
Use RIVALSFPS.GG 5.5.0 or later. When the game crashes, the app shows Marvel Rivals crashed and, when it can tell, names the file the game was loading and the mod of yours that replaces it. Turn it off switches that mod off. If no mod is named, switch half your mods off at a time until the crash stops.
Is the mod in the crash popup always the cause?
No. It is the mod the game was loading when it crashed, and the game can crash on a file for its own reasons. Turning that mod off and launching again is the quickest way to find out.
What does the Crashed badge mean?
Marvel Rivals crashed while loading that mod. The badge stays if you turn the mod off. It clears when the mod's files change, when you remove the mod, when a later crash takes its place, or after a launch that loads the mod and closes normally.
How can I tell whether my mods loaded?
Launch the game once. Each mod that was on then says Loaded or Not loaded in the Mod Manager, based on what Marvel Rivals itself reports, and a note beside Import says how many loaded.
Marvel Rivals still crashes with every mod off. What now?
Then a mod is not the cause. Verify Game Files, in Settings on the Diagnostics tab, asks your game store to check and repair Marvel Rivals. If it still crashes, make a ticket in the RIVALSFPS.GG Discord.
