Problem: Marvel Rivals on PC keeps crashing/freezing (often tied to shaders, memory spikes, and driver behavior) — and there’s no single reliable fix
Published: 2026-01-12 10:20 (local time)
Quick Summary
- Many PC players report Marvel Rivals crashing on launch, during/after matches, or while compiling shaders—sometimes with full-system freezes or reboots.
- Reports cluster around shader compilation, RAM pressure on 16GB systems, and NVIDIA driver/Windows settings interactions.
- There isn’t one universal solution; the best results come from testing a short list of targeted changes (drivers, shader compilation mode, cache/config resets, and stability settings).
- Some “fixes” have tradeoffs (visual stutter on first render, longer first boot, reduced performance, or losing local settings).
- If you’re seeing hard reboots/BSODs, treat it like a system stability issue (thermals/OC/PSU/driver) and stop stress-testing the game until stable.
What’s happening
Across PC setups, players are describing a repeating pattern: Marvel Rivals will freeze, crash to desktop, or crash the entire PC—often during shader compilation or shortly after several matches. Symptoms vary by machine: some players can launch but crash at end-of-match; others can’t get past early shader compiling; some experience escalating instability (stutters, freezes) that becomes “can’t play at all.” Community threads show this has persisted across multiple updates and hardware combinations, which is why it feels like “few to no clear solutions.”
Based on developer-facing messaging and community reporting, the most common “trigger moments” are: first launch after a game update or graphics driver update (shader rebuild), entering a new match (new material/shader work), alt-tabbing, and long sessions where caches and memory use accumulate.
Likely causes (what research suggests)
Shader compilation + memory pressure: The game has acknowledged heavy RAM usage scenarios and introduced an “experimental” shader compilation mode intended to reduce memory usage and mitigate freezes/crashes on lower-memory PCs. This strongly suggests shader work and memory load are part of the crash pattern for a meaningful subset of players.
NVIDIA driver-level issues (shader cache overflow) and a Windows setting interaction: The game published guidance stating that updating to a specific NVIDIA driver version (and later) can reduce GPU crashes, referencing driver-level shader cache overflow and a crash condition tied to Hardware-accelerated GPU scheduling (HAGS) being disabled on certain NVIDIA driver branches/RTX generations.
Configuration/cached data corruption: Repeated reports of “worked yesterday, broken today” and “fails during compiling shaders” align with stale or corrupted caches/configs. Clearing/rebuilding caches is a common, evidence-backed approach when shader compilation is involved.
System instability under spike loads (especially with overclocks): Community troubleshooting frequently lands on “reduce CPU boost/OC” or similar stability steps. While not proof the game is “at fault,” it indicates the game can produce spike loads that expose marginal CPU/GPU/VRAM/PSU stability.
Solutions & Workarounds
1) Update NVIDIA drivers (or roll forward to a known-stability branch)
Who it helps: PC players on NVIDIA GPUs (especially those seeing “after several matches” crashes or sudden GPU-related crashes).
Steps:
- Open the NVIDIA App (or GeForce Experience equivalent).
- Check for Game Ready Driver updates and install the newest available driver.
- Reboot Windows after installation.
- Launch the game and test for stability for 3–5 matches (not just one).
Risks/tradeoffs: New drivers can introduce issues in other games; if new problems appear, consider trying a different recent driver version.
Stop and contact support when: You still crash repeatedly after driver update + reboot, especially if crashes are reproducible at the same point (e.g., “3% shaders every time”).
2) Check Windows “Hardware-accelerated GPU scheduling” (HAGS) and test both states
Who it helps: Windows 10/11 players on NVIDIA where crash behavior changed after driver updates.
Steps:
- Windows Settings > System > Display > Graphics > Default graphics settings.
- Find “Hardware-accelerated GPU scheduling.”
- If it’s OFF, turn it ON and reboot; if it’s ON, turn it OFF and reboot (test whichever is opposite of your current state).
- Retest Marvel Rivals.
Risks/tradeoffs: HAGS can affect performance/latency in some setups; changes are system-wide, not just for one game.
Stop and contact support when: Changing HAGS makes no difference after two full reboots and you still get full PC resets.
3) Use the game’s “Switch Shader Compilation Mode” (especially on 16GB RAM)
Who it helps: PCs with 16GB RAM (or less) experiencing FPS drops, frozen visuals, or frequent crashes tied to memory load.
Steps:
- Open the Marvel Rivals PC launcher.
- Enable the “Switch Shader Compilation Mode” experimental option (wording may vary slightly by launcher version).
- Launch the game and allow the first post-update/driver-update shader compilation to finish without alt-tabbing.
- Play 2–3 matches to see if freezes/crashes reduce.
Risks/tradeoffs: The game notes possible brief abnormal rendering and first-render stutters per match; on lower-thread CPUs, combining this with certain frame generation features can add stutter.
Stop and contact support when: This mode causes new severe issues (persistent shader crashes, hard resets) or you cannot reach the menu reliably.
4) Clear/rebuild shader caches and reset local config (most effective for “stuck compiling shaders”)
Who it helps: Players crashing during compiling shaders or stuck in a repeatable crash loop on launch.
Steps:
- Fully exit the game and launcher.
- Delete/reset the game’s local settings/config folders (commonly in Windows AppData Local/Roaming for the title). If you’re unsure, back up first by renaming the folder instead of deleting.
- In Steam, run “Verify integrity of game files.”
- Reboot and relaunch; let shaders compile without running other heavy apps.
Risks/tradeoffs: You may lose local settings (graphics, keybinds), and the first launch may take longer while caches rebuild.
Stop and contact support when: Verifying files + config reset still crashes at the same percent consistently.
5) Remove overclocks/undervolts; set “known-stable” CPU/GPU behavior
Who it helps: Anyone experiencing full-system reboots/BSODs, or crashes that began after tuning CPU/GPU settings.
Steps:
- Revert GPU overclocks/undervolts to stock (including “one-click OC” profiles).
- Revert CPU overclocks to stock; if you run aggressive boost settings, temporarily reduce them.
- Ensure thermals are controlled (clean dust filters, verify fan curves).
- Retest the game for at least a few matches.
Risks/tradeoffs: Reduced performance; but this is the safest way to confirm if the crashes are stability-related.
Stop and contact support when: Stock settings still produce hard resets—at that point, treat it as a broader stability/driver issue and gather logs for support.
6) Reduce “spike” scenarios: cap FPS, avoid alt-tabbing, and lower VRAM-heavy settings
Who it helps: Players who can play but crash after several matches, or who notice instability when multitasking.
Steps:
- Cap FPS (e.g., 60/120) in-game or via driver control panel.
- Lower texture/shadow settings one step; disable the most expensive extras first.
- Play in fullscreen/borderless consistently; avoid frequent alt-tab during match loads.
- Close overlays you don’t need (recording, performance overlays) and browser video playback during matches.
Risks/tradeoffs: Visual downgrade and potentially higher input latency depending on your cap/v-sync setup.
Stop and contact support when: You still crash even at conservative settings and minimal background apps.
Prevention (so it doesn’t come back)
- After every major game update or GPU driver update, expect a heavier first launch; don’t alt-tab during shader compilation.
- Keep GPU drivers current, but avoid swapping driver versions repeatedly in a single day (test systematically).
- If you’re on 16GB RAM, minimize background apps while playing and consider enabling the shader compilation mode designed to reduce memory usage.
- Stick to stock or “daily stable” CPU/GPU settings; competitive overclocks can turn a borderline issue into constant crashing.
FAQ
Q: Is this only an NVIDIA problem?
A: No. NVIDIA-specific guidance exists, but community reports show crashes can happen on other hardware too; shader/memory behavior can affect many configurations.
Q: Why do I crash after a few matches instead of immediately?
A: Research and developer notes point to shader cache behavior and memory/caching accumulation that can worsen over multiple matches, not just at launch.
Q: I crash at “compiling shaders” every time. What’s the fastest thing to try?
A: Reset local config/caches and verify files, then let the first launch complete without alt-tabbing. If on NVIDIA, update drivers as well.
Q: Should I enable the experimental shader compilation mode?
A: If you’re on 16GB RAM (or less) and see freezes/crashes, it’s specifically recommended as a mitigation—expect possible minor first-render stutters.
Q: My PC hard reboots. Is the game “killing my hardware”?
A: A hard reboot usually indicates a stability issue under load (power/thermals/driver/OC). Stop stress-testing and run stock settings; if it persists across games, troubleshoot system stability before continuing.
Q: When should I stop troubleshooting and file a ticket?
A: If crashes are perfectly repeatable at a specific step (same shader percentage), or if you get BSODs/hard resets even at stock settings and updated drivers, contact support with logs and system details.