Skip to content
tricknfixGAMING · TECHNOLOGIE · INFORMATIQUE
EN
Create
#GamingGuide

Marvel Rivals crashes on PC at launch, after loading or mid-match: NetEase’s official fixes to try before Season 11 on November 13

Official Marvel Rivals screenshot: a dark armored hero swinging a huge golden blade at other heroes in a sunlit temple arena, with the in-game HUD visible
Crédit : © MARVEL / NetEase Games

Official Marvel Rivals Season 11 trailerVideo: “Doomsday | Marvel Rivals Season 11 Trailer”, official Marvel Rivals YouTube channel (NetEase Games), published November 10, 2026 (5:00 PM Paris time), 1 min 37 s. It is the Season 11 trailer; it does not show any crash or fix. https://www.youtube.com/watch?v=EcKAQ4UNZlI


Marvel Rivals Season 11: Doomsday starts on November 13, 2026 with Nightcrawler and a large balance patch. If the game already crashes at launch, freezes after the loading screen or closes mid-match on your PC, now is the time to sort it out. NetEase does not list a new crash fix in its latest patch notes (Version 20261105), but its official technical FAQ covers the main PC crash cases. Here they are in order, with what each step is for and its limits. Nothing here was tested by TricknFix on our own PCs: these are NetEase’s documented procedures.


Crash at launch, or stuck after the loading screen: check your antivirus and firewall first

  • NetEase’s FAQ links three symptoms to security software wrongly blocking the game process: a crash when launching, failing to enter the match after loading finishes, and failing to reconnect after a disconnection.
  • Add the game folder and the file Marvel\Binaries\Marvel-Win64-Shipping.exe (inside your install folder) to your antivirus or firewall exceptions.
  • Windows Defender (NetEase’s path): Windows Security, Virus & threat protection, Manage settings, then Controlled folder access: allow Marvel-Win64-Shipping.exe.
  • Windows Firewall: Windows Defender Firewall, Allow an app through firewall, then allow Marvel-Win64-Shipping.exe on private and public networks.
  • NetEase also suggests temporarily disabling the antivirus to test. If you do, turn it back on right after the test and keep the exception instead.

Random crashes during matches: repair files, then the graphics driver

  • Verify the game files in the launcher you actually use. Steam: Properties, Installed Files, Verify integrity of game files. Epic Games Store: Library, Marvel Rivals, Manage, Verify. NetEase Loading Bay: options button, Verify File Integrity. Wait until any missing files have downloaded.
  • Reinstall the latest driver for your graphics card (NVIDIA, AMD or Intel) with the clean installation option when available.
  • NVIDIA only: NetEase’s GPU guide describes clearing the shader cache. NVIDIA Control Panel, Manage 3D settings, Shader Cache Size set to Disabled, restart; delete the DXCache folder in %USERPROFILE%\AppData\LocalLow\NVIDIA\PerDriverVersion\; set Shader Cache Size back to Enabled and restart again. Do not apply this NVIDIA path to AMD or Intel graphics.
  • NetEase also recommends enabling “Switch Shader Compilation Mode” in the launcher to reduce crashes. Its FAQ does not describe the exact menu on that page.
  • Start the game with “Start With GPU Debug Mode” from the launcher. It does not fix anything by itself: it collects crash data for NetEase and can reduce performance; you can turn it off at any time.

“Out of Video Memory” on an Intel Core 13th or 14th gen CPU

  • For this exact message, NetEase points to the known stability issue of some Intel 13th and 14th generation processors (low VRAM warnings, crashes during shader compilation), not to your graphics card.
First step: update your motherboard BIOS following Intel’s or your motherboard maker’s instructions. If instability continues, NetEase sends you to your PC maker, Intel support (boxed CPU) or your retailer (tray CPU).
  • NetEase’s workaround: when the game shows the CLICK TO NAVIGATE prompt, install Intel Extreme Tuning Utility (XTU), restart, and lower the Performance Core Ratio by 2 to 3 steps (example given: 55x to 53x), then Apply. This lowers CPU performance and is a CPU tuning change: only do it if you are comfortable with it, and prefer the BIOS update.

Stuttering, or “DirectX 12 is not supported on your system”

  • Stuttering on a PC that meets the requirements: clean-install the latest graphics driver, then in Windows Settings, System, Display, Graphics, add Marvel.exe from the game folder and set it to High performance.
  • “DirectX 12 is not supported”: update Windows (NetEase cites Windows 10 64-bit, version 1909 or later) and your graphics driver, and check your card against the minimum requirements (NVIDIA GTX 1060, AMD RX 580 or Intel Arc A380, 16 GB of RAM, 70 GB of storage).

Still crashing: send NetEase a diagnostic file

  • Close the game. In Steam, right-click Marvel Rivals, Manage, Browse local files, then open client_diagnose.exe and click Analyze.
  • When it finishes, the tool opens the folder containing diagnose_yyyy_mm_dd_xx_xx_xx.zip. NetEase asks for it on the official Discord (discord.gg/marvelrivals); the support e-mail listed on the site is marvel_rivals@global.netease.com.
  • Do not post that ZIP publicly: it describes your PC and system.

What Season 11 changes on November 13

  • Season 11: Doomsday launches on November 13, 2026 according to Marvel Games and NetEase (press release of November 10). Nightcrawler (Strategist) arrives in the first half of the season and Dracula also joins the roster.
  • The balance post for Version 20261113 (Angela, Deadpool and others) is already online; the 18 vs 18 Chrono-Annihilation mode and its Incursion Point map are planned for the November 26 update.
  • The exact patch time and download size for November 13 were not published in the sources we read on November 11 at 3 PM Paris time.

What is not known yet

  • Whether the Season 11 patch adds specific crash fixes: no Season 11 patch notes listing fixes were published at the time of writing.
  • Which PC configurations crash most: NetEase has not published statistics.

Sources

50 views

Conversation (0)