Marvel Rivals

Marvel Rivals

View Stats:
unreal engine crash, constantly
so my system is older, that said i can easily get 120 fps consistent on this title. but randomly, for seemingly no reason, the game will lock up, and moments later unreal engine crash handler comes up and says there was a GPU crash...

i've done a verify on anything and everything, a clean install of the latest GPU drivers for my card, tried to read the generated log but in notepad++ it comes up in machine language.

as for it being an actual "GPU crash" my hardware statistics indicate no power loss or performance loss. this is the only title crashing on my PC at the moment. everything else i've run made in unreal engine runs fine.

anyone got any ideas?

11900k i9
2080ti
64gb RAM
all installed on a m.2 ssd

thermals are all fine, better than the more intensive games honestly.

tried turning off lumen but no effect, figured it was newer to the gaming scene that it might be the cause but no dice.
< >
Showing 1-15 of 21 comments
Essedus Feb 16 @ 2:40pm 
Anecdotal, but I find I crash most often when I'm doing particularly well in a match.
I got a 3080 card and it does the same thing, with lowest settings, normal settings and max settings all crash after an hour and half of playing. I turned off overlays and everything. searched online and was told use old graphic drivers I did that fixed it for awhile but no its crashing again...so i stalled current gpu drivers and still does it.
Originally posted by Essedus:
Anecdotal, but I find I crash most often when I'm doing particularly well in a match.
heh aint that the truth.

i've had it happen at many different moments, start of a match, mid match, practice range, everywhere except the lobby. it makes a crash log but i dont have anything that can properly decode and read it so i couldn't pinpoint the exact cause.
Always crashing high end pc smh just crashed reinstalled game, drivers, windows no fix.
There is a popular hack on a certain website that can crash people. So look there first.
Originally posted by Xilo The Odd:
i've had it happen at many different moments, start of a match, mid match, practice range, everywhere except the lobby. it makes a crash log but i dont have anything that can properly decode and read it so i couldn't pinpoint the exact cause.

You could go to folder

%localappdata%\Marvel\Saved\Crashes\

then subfolder with most recent date.

UECC-Windows-(some_number_here)

In the CrashContext.runtime-xml file, there are some details.
For me it is always RHIInterruptThread crashing.

<Thread> <CallStack>KERNELBASE 0x00007ffc9a2b0000 + 3b699 Marvel-Win64-Shipping 0x00007ff709360000 + e85f05 Marvel-Win64-Shipping 0x00007ff709360000 + 263276b Marvel-Win64-Shipping 0x00007ff709360000 + 26337c5 Marvel-Win64-Shipping 0x00007ff709360000 + 25fdf23 Marvel-Win64-Shipping 0x00007ff709360000 + 260d2d9 Marvel-Win64-Shipping 0x00007ff709360000 + 2611500 Marvel-Win64-Shipping 0x00007ff709360000 + 261998f Marvel-Win64-Shipping 0x00007ff709360000 + e86677 Marvel-Win64-Shipping 0x00007ff709360000 + e7d8c1 KERNEL32 0x00007ffc9ae50000 + 17374 ntdll 0x00007ffc9c930000 + 4cc91</CallStack> <IsCrashed>true</IsCrashed> <Registers /> <ThreadID>2688</ThreadID> <ThreadName>RHIInterruptThread</ThreadName> </Thread>

I just search in notepad a phrase <IsCrashed>true</IsCrashed>. And it always points to this <ThreadName>RHIInterruptThread</ThreadName>

Rest of the logs are encrypted or something, probably to hide game mechanics from people making cheats.

And ironic message from Devs in logs, they haven't done anything about it.

<ErrorMessage>GPU Crash dump Triggered</ErrorMessage>
<CrashReporterMessage>We are very sorry that this crash occurred. Our goal is to prevent crashes like this from occurring in the future. Please help us track down and fix this crash by providing detailed information about what you were doing so that we may reproduce the crash and fix it quickly. Thanks for your help in improving Marvel Rivals.</CrashReporterMessage>
Last edited by IndianaJones; Feb 18 @ 3:44pm
Ok so its not only me. I'm not relived but I atleast know that my computer isn't being ♥♥♥♥♥♥.
Essedus Feb 18 @ 3:53pm 
Originally posted by Charlemagne:
There is a popular hack on a certain website that can crash people. So look there first.
I have suspected this for some time. It wouldn't be the first, or the last time something like this has been done in an online competitive game.
I’ve literally been crashing every game my game was working just fine a few days ago now I get a gpu crash. I played paladins for 1 hour no crashes or anything. I have an MSI claw and it works perfectly and for some reason marvels just keeps crashing and crashing it sucks I really like this game
Originally posted by edgarrodriguez91:
I’ve literally been crashing every game my game was working just fine a few days ago now I get a gpu crash. I played paladins for 1 hour no crashes or anything. I have an MSI claw and it works perfectly and for some reason marvels just keeps crashing and crashing it sucks I really like this game
yeah i dug around some other crash threads to see what people did / suggested, havn't had a crash yet but we'll see. but as far as i can tell its only Marvel Rivals doing this.

or a bethesda game. but thats different. for way different reasons.
And it still crasher after the update maaan....
i realy like the game but these crashes are enoying
so i disabled some overlays and a few things other threads have suggested and havn't had any issues. will update when i'm sure my crash issue is gone.
so after a few long play sessions, this is what i did that seemed to have an effect:

added command line to launch the game -dx12

disabled steam overlay and apparently i had a discord overlay, which i didn't want or need so both those disabled. this has stopped the random crashing for me.
if you haven't already. make sure Nvidia Reflex is disabled. Having that on increases the frequency
Originally posted by Roland's 2nd:
if you haven't already. make sure Nvidia Reflex is disabled. Having that on increases the frequency
yeah i never had it on so it wasnt the cause itself, good to know it makes it happen more often...

hmm...

if i solved the main cause, then theoretically turning it on should cause no issue or make any existing issue worse then? i dunno i'll dink with it tomorrow after work. wouldn't mind getting the exact causes nailed down and laid out in a thread in here.
< >
Showing 1-15 of 21 comments
Per page: 1530 50

Date Posted: Feb 16 @ 2:20pm
Posts: 21