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- Remove overlays and GPU tuning tools from startup.
- Reset the game to 1080p, low preset, DX12 default, no frame generation.
- Play one bot match or a short practice session. If it crashes, capture the dump path and driver version.
- If it is stable, raise resolution and texture quality one step at a time.
- Do not force APIs or “unlock” flags until the baseline is proven.
Where the evidence lives
Config\WindowsClient\GameUserSettings.ini # graphics and display settings
Crashes\ # Unreal crash reports and dumps
Logs\ # engine and renderer logs
Saved\Screenshots\ # screenshots if enabled 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.
[/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. Built locally in your browser. Nothing is uploaded.
; 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
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.
Black: average / Blue: 1% 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 completeThe 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 answersWhat does a GPU crash dump in Marvel Rivals mean?
Should I use DX12 or DX11 in Marvel Rivals?
Does lowering graphics settings always stop the crash?
Crash & Startup
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.
Marvel Rivals: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Marvel Rivals on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on Unreal Engine 5.
Marvel Rivals: Shader Stutter, Frame Pacing & Unreal Engine 5 Config Tuning
A measured stutter-hunting routine for Marvel Rivals: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Unreal Engine 5 settings file to edit.
Marvel Rivals: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Marvel Rivals without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.