Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
My easy fix was just changing DLSS from Quality to Performance. No more crashing.
But that's just me, feel free to see if it works for you, good luck guys.
If you're using DLSS, trying switching to TAAU with render res of like 70. Or vice versa if you are already using TAAU.
Turn V-sync off in game (but turn on in nvidia control panel) and leave reflex on.
Set global illumination to off or low. Just don't use lumin. Screen space reflections off. Set shadows to low. Set post processing to low. Set effects to low. Models and textures can be high or ultra.
If none of that works, try downloading the program i mentioned above. It's called intelligent standby list cleaner. It's free and it's super lightweight. See If that helps and report back.
Your CPU is a bottleneck. And being that this game is apparently a ram hog, 16gb probably isn't helping you either.
There's also another similar access violation that points to not having access to certain .pak files, but I've experimented with permissions a bunch with no luck.
The only puzzling thing is that the crashing only seems to affect a porportionately small amount of the overall playerbase, so if it was an innate code error I'd assume everyone would have the same problems.
We've basically narrowed down the culprit to be memory, but we can rule hardware out there too as I've seen the same errors from people running all RAM sizes and clock speeds. Doesn't matter if you have 16GB 3600MHz DDR4, or 64GB 6000Mhz DDR5 like me, for people who have this issue the memory will leak and fill up before you get one of the UE5 crashes or your system shuts down. Some people say disabling XMP or slightly underclocking their RAM fixed it for them, but I've also seen that reported both by people with 3600Mhz and by people with 6000Mhz, so it's not so much an issue with the speed itself but with the RAM running at full speed regardless of what the top speed "limit" is. For others this does nothing, so I honestly have no idea.
It's probably some weird background software that's the common denominator for all of us that just doesn't play well with the game's calls for file access/memory management somehow.
Edit: I also thought it could be Windows, but it doesn't seem to matter if you're on Win 10/11 or which update you have either.
4090
i7 13700K
32GB DDR5
6TB M.2
I can run Cyberpunk, Control, RDR2, Flight Simulator, you name it, but Marvel Rivals will not run.
At this point I'm just waiting for a patch, but it's pretty disappointing that we haven't gotten a hotfix since release. Either it isn't a priority fix (Which is pretty sad) or they're waiting to patch it in the mid-season, which is also annoying but when a game is released on consoles as well as PC and you want to update all versions at the same time (Which you have to because of crossplay in this case) you have to wait for the console patches to be approved by their parent companies, which can delay an update that would've been out for PC users weeks ago had they not have to check, if you get me. That said, this seems to be a PC-specific problem so pushing a fix back - implying they even have one yet - still doesn't make much sense.
Due to the oddity of how many people it affects and the wild variation of set ups that are affected, I would say it's a game memory leak issue that's either exacerbated or delayed based on combinations of what hardware user is running along with whatever other processes are active at the same time.
In short, Rivals is trying to grab every address it can until it can't anymore. So either you crash because you ran out of true available memory or you crash because the game sees "available" memory which is actually being used by something else.
Really all I can think of as I don't particularly have much running in the background of my PC during gaming. Just Steam, Discord, MSI Afterburner, and MB. Probably explains why I can generally get to double digit matches in a singular session before crashing.
Otherwise I'm running the game at high settings, 1080p, capped 120 FPS no problem on my rig:
3080 (undervolted)
Ryzen 7 7700x (undervolted)
32GB DDR5
2TB M.2
I figured maybe the gpu was resetting or something because I read through one of the discussions that windows intervenes and forces the gpu to reset. I waited about 10 minutes for the screen to come back up, but nothing.
Ive tried dozens of fixes to no avail. Reinstalled/updated drivers. Tried older versions. Tried specific settings on the launcher. Tried installing it through Epic. Tried cleaning the pc out and reseating the GPU and reapplying new thermal paste on the cpu. Last test I haven't tried is trying my GPU on another computer. I can run games like Spacemarine 2, Cyberpunk, Destiny 2, and Tekken 8 with no real issues. Its so weird because it was completely fine during the launch, but something happened after the winter update or something.
Specs
3080 10gb vram
11th gen intel i7-11700kf 3.6ghz
32 GB Ram
game is installed on an SSD
At this point, Im more so interested in what the actual reason is causing these problems for me and so many others. I just want to be able to look through the discussions and confidently say, "Yup, its the game and not my PC or its parts".
hey thank you, this worked! didnt even had to download the intelligent standby list cleaner. But ill keep in mind to download it if the problem comes back
EDIT: actually, it still happens but way less often. I'll try to download the standby list cleaner and post the feedback here
I had this issue starting a day or so ago with the almost the same specs as you. I was able to fix the issue by installing Intels ETU(Extreme Tuning Utility) tool and taking moving the "performace core ratio" number down to 53 (original number was 57) and this completely fixed my game.