Crash & Startup / Marvel Rivals / Unreal Engine 5

Marvel Rivals: The UE5 GPU Crash Dump and DX12 Fix Path

A reproducible method for Marvel Rivals GPU crash dumps, DirectX 12 device-removal errors, and VRAM-driven crashes after a seasonal patch.

Official Steam Store header artwork for Marvel Rivals.

Marvel Rivals runs on Unreal Engine 5 and uses DirectX 12. “GPU crash dump” is the game’s way of saying the graphics device stopped responding. Season 6 included mitigations, not a universal cure. A crash that happens in the hero-select screen has a different likely cause than one that happens after twelve minutes of 4K combat with frame generation on.

The right response is a clean baseline and a staged test. Do not reinstall Windows first.

The staged crash response

Baseline before flags
  1. Remove overlays and GPU tuning tools from startup.
  2. Reset the game to 1080p, low preset, DX12 default, no frame generation.
  3. Play one bot match or a short practice session. If it crashes, capture the dump path and driver version.
  4. If it is stable, raise resolution and texture quality one step at a time.
  5. Do not force APIs or “unlock” flags until the baseline is proven.

Where the evidence lives

%LOCALAPPDATA%\MarvelRivals\Saved
Config\WindowsClient\GameUserSettings.ini  # graphics and display settings
Crashes\                                   # Unreal crash reports and dumps
Logs\                                      # engine and renderer logs
Saved\Screenshots\                         # screenshots if enabled
A crash dump is diagnostic data, not a fix. Keep the newest one, note the build and driver, and do not send random dumps to strangers in a support forum.

Open the newest crash report and look for the renderer error near the end. An “out of video memory” line points to VRAM. A “device removed” line can point to driver timeout, an unstable clock, or an overlay. A GPU hang with no allocation warning is more likely driver or clock related.

Rebuild the local settings cleanly

A corrupted GameUserSettings.ini can keep reapplying a bad resolution or HDR mode. Exit the game, make a copy of the file, then rename the original so the game regenerates it. Do not delete the whole Saved folder unless you understand that it also contains local logs and some account-linked state.

%LOCALAPPDATA%\MarvelRivals\Saved\Config\WindowsClient\GameUserSettings.ini
[/Script/MarvelRivals.MarvelRivalsGameUserSettings]
ResolutionSizeX=2560
ResolutionSizeY=1440
FullscreenMode=1
FrameRateLimit=144
bUseVSync=False
; Existing user settings may use different section or key names.
; Rename the whole file to force a clean regeneration instead of
; hand-editing values you do not recognise.
Back up the original. If the game restores the same bad state from the cloud, reset the in-game graphics profile before testing again.
Config builder / Marvel Rivals Unreal Engine 5

Built locally in your browser. Nothing is uploaded.

Game config directory\Engine.ini
; GamePathHub // Marvel Rivals
; Engine: Unreal Engine 5 | GPU class: 12 GB | Target: 144 FPS
; Upscaler: DLSS Quality
; Change one group at a time. Back up the original file first.
[SystemSettings]
r.Streaming.PoolSize=7552
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.MaxTempMemoryAllowed=1359
r.Streaming.HLODStrategy=2
r.Upscale.Quality=2
r.MaxAnisotropy=8
t.MaxFPS=144
r.VSync=0
The streaming pool is intentionally capped below the 12 GB card limit. Remove r.Streaming.PoolSize if the game already manages VRAM cleanly.

What the frame-time bench shows

The chart compares a clean 1080p competitive profile with 1440p high and a 4K high frame-generation profile. The crash was not reproduced on the 16 GB bench; the point is the VRAM and frame-time cost that makes lower-tier cards vulnerable.

Marvel Rivals / resolution and frame-gen pressure
Scale 0–240 FPS
Black: average / Blue: 1% low
1080p / low / no frame gen 219 FPS / 171 low
1440p / high / DLSS Quality 164 FPS / 131 low
1440p / high / DLSS + frame gen 221 FPS / 128 low
4K / high / DLSS Quality + frame gen 151 FPS / 84 low

Bench: RTX 4080 SUPER 16 GB / i9-13900K / 32 GB DDR5. Practice range and a recorded bot match. Frame-gen run uses DLSS Quality plus generated frames.

The frame-generation row is instructive: the average jumps, the native 1% low barely moves. On a card near its VRAM limit, that extra working set can be the difference between stable and a device-removal crash.

GPU stability checks

  • Remove any GPU overclock, undervolt, or fan-curve software profile. Test at stock.
  • Use a clean driver install. A “clean install” checkbox is not a substitute for removing old tuning profiles.
  • Verify both PCIe power connectors are fully seated on cards that use two.
  • Disable hardware-accelerated browser windows and media during a test. They compete for VRAM.
  • Stop RGB and monitoring utilities that inject into the game process while you isolate.

Marvel Rivals GPU crash triage

0 / 8 complete

The anti-cheat boundary

Marvel Rivals uses anti-cheat. Do not install unsigned DirectX wrappers, injected overlays, or “FPS unlock” DLLs to chase a crash fix. If a tool needs to inject into the game process, remove it before you file a support ticket. A stable default build is the only baseline worth defending.

Did this fix work on Patch Season 6 — GPU crash dump mitigations?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against Season 6 — GPU crash dump mitigations. Votes are local-only telemetry.

Marvel Rivals: bench questions

3 answers
What does a GPU crash dump in Marvel Rivals mean?
It means Unreal Engine lost communication with the graphics device or detected a fatal GPU fault. It can be a driver issue, a VRAM overcommit, an unstable overclock, or a corrupted game cache. The dump confirms the symptom, not the cause.
Should I use DX12 or DX11 in Marvel Rivals?
The game's current UE5 build is designed around DirectX 12. Switching to an older API is not a general fix. Test the default path first and remove unstable overlays before forcing launch flags.
Does lowering graphics settings always stop the crash?
No, but it can stop VRAM-driven crashes. If the crash still occurs at 1080p low with every overlay disabled, test a clean driver install and remove any GPU overclock or undervolt.
Filed under

Crash & Startup

Patch tested: Season 6 — GPU crash dump mitigations

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.