PSA to those who are crashing (GPU dump, unhandled exception, etc)

[Skygaze]

Typed this up as a response in another thread here but it got big enough that I thought I might as well make one myself.

There's a thread in the Discord with a few thousand responses, but the short of it is that none of us can find a fix. If you can think of it, it's probably been tried.

Personally, I have:

    
• Reinstalled the game multiple times, once using files from the Epic launcher.
  
• Wiped extra folders after uninstalling. (Some left over in directory + appdata.
  
• Verified files multiple times.
  
• Tried 4 older driver releases then cleanly reinstalled the latest ones with DDU.
  
• Cleared shader cache, which can stop crashing but only until it fills up again.
  
• Checked for CPU instability as I'm using a 14700k. (No issues, stress tested twice)
  
• Checked for overheating (Nope) and repasted my CPU to be safe. (No issues)
  
• Checked for RAM instability. (No issues)
  
• Tried every mix of in-game settings, with frame caps at 30/60/90 and 144.
  
• Tried multiple different power settings.
  
• Tried running the game as admin/in compatibility mode for Windows 8.
  
• Tried making exceptions in my firewall for the game and launcher.
  
• Tried turning off all overlays and recording software/closing browser and Discord.
  
• Made sure my BIOS/chipset drivers are up-to-date.
  
• Messed around with different settings in Nvidia Control Panel.

GPU: 3080 ti
CPU: I7 14700k
RAM: 64GB 6000MHz DDR5

Game is installed on an SSD with plenty of free space.

Most frequent errors are a "GPU" crash that I've noticed only triggers when the game's memory leak reaches critical mass, which seems to be about 50/64GB of my RAM, an "unhandled exception" crash which triggers when the game can't access certain .pak files correctly, and another generic UE5 crash that I can't remember.

This is happening to a bunch of us with varying specs, doesn't matter if you're using AMD/Nvidia GPUs or AMD/Intel CPUs, doesn't matter how much RAM you have.

A few people have reported that disabling XMP or slightly underclocking (6000MHz > 5600MHz) their RAM has fixed it for them, but this game's memory management in general is atrocious. I'll probably underclock my RAM to test it out eventually but I'm pretty fed up at this point, and even if that was a surefire fix, it's still an issue with UE5 being a trash engine and not people's systems.

If anyone has a hunch about the common denominator or you've found a "fix" that works for you, drop it below so other people can give it a crack. Just know that if you're unlucky like me and many others, you could be troubleshooting for hours with no results.

[Oxolane]

Thanks for the info, I thought it was just me. I have a 7800XT and while I do like to do an underlock/overclock it, it also happens when in default. It's actually crashed my computer multiple times and forces a reboot.

[Dovah]

Removing my underwolt/overclock for my GPU fixed it for me. I still have MSI Afterburner and Riviatuner on in the background btw.

The only time I ever crash is at the title screen, right after you left-click to start the game and the cinematic starts. Haven't crashed any other way apart from that. And ONLY after the recent update did the crashes start, before that none of this ever happened, even WITH my GPU undervolt/overclock on.

[SolutionS]

Originally posted by Dovah:

Removing my underwolt/overclock for my GPU fixed it for me. I still have MSI Afterburner and Riviatuner on in the background btw.

Yea its a problem with the 13th and 14th gen intel chips, OP is likely experiencing the same thing. You are both eligible for RMA but intel is extremely laggin on any rma since 99% of their chips released faulty. Its best to set all the power targets manually in the bios and turn off any mother board boosting like Multicore enchancement for asus.

[kaisha]

Originally posted by Skygaze:

Typed this up as a response in another thread here but it got big enough that I thought I might as well make one myself.

There's a thread in the Discord with a few thousand responses, but the short of it is that none of us can find a fix. If you can think of it, it's probably been tried.

Personally, I have:

    
• Reinstalled the game multiple times, once using files from the Epic launcher.
  
• Wiped extra folders after uninstalling. (Some left over in directory + appdata.
  
• Verified files multiple times.
  
• Tried 4 older driver releases then cleanly reinstalled the latest ones with DDU.
  
• Cleared shader cache, which can stop crashing but only until it fills up again.
  
• Checked for CPU instability as I'm using a 14700k. (No issues, stress tested twice)
  
• Checked for overheating (Nope) and repasted my CPU to be safe. (No issues)
  
• Checked for RAM instability. (No issues)
  
• Tried every mix of in-game settings, with frame caps at 30/60/90 and 144.
  
• Tried multiple different power settings.
  
• Tried running the game as admin/in compatibility mode for Windows 8.
  
• Tried making exceptions in my firewall for the game and launcher.
  
• Tried turning off all overlays and recording software/closing browser and Discord.
  
• Made sure my BIOS/chipset drivers are up-to-date.
  
• Messed around with different settings in Nvidia Control Panel.

GPU: 3080 ti
CPU: I7 14700k
RAM: 64GB 6000MHz DDR5

Game is installed on an SSD with plenty of free space.

Most frequent errors are a "GPU" crash that I've noticed only triggers when the game's memory leak reaches critical mass, which seems to be about 50/64GB of my RAM, an "unhandled exception" crash which triggers when the game can't access certain .pak files correctly, and another generic UE5 crash that I can't remember.

This is happening to a bunch of us with varying specs, doesn't matter if you're using AMD/Nvidia GPUs or AMD/Intel CPUs, doesn't matter how much RAM you have.

A few people have reported that disabling XMP or slightly underclocking (6000MHz > 5600MHz) their RAM has fixed it for them, but this game's memory management in general is atrocious. I'll probably underclock my RAM to test it out eventually but I'm pretty fed up at this point, and even if that was a surefire fix, it's still an issue with UE5 being a trash engine and not people's systems.

If anyone has a hunch about the common denominator or you've found a "fix" that works for you, drop it below so other people can give it a crack. Just know that if you're unlucky like me and many others, you could be troubleshooting for hours with no results.

I kept getting the "unhandled exception" crash error when I was overclocking my ram to 6400 mt/s. never happened in any other game besides this one, but downclocking it back to 6000 fixed it for me.

[Dovah]

Originally posted by SolutionS:

Originally posted by Dovah:

Removing my underwolt/overclock for my GPU fixed it for me. I still have MSI Afterburner and Riviatuner on in the background btw.

Yea its a problem with the 13th and 14th gen intel chips, OP is likely experiencing the same thing. You are both eligible for RMA but intel is extremely laggin on any rma since 99% of their chips released faulty. Its best to set all the power targets manually in the bios and turn off any mother board boosting like Multicore enchancement for asus.

I don't see how my CPU would be the issue. As removing the undervolt on my GPU fixed the problem. Again this only happened after the most recent update. Shader compilation works fine.

[YourFreeUseHairbrush]

the solution is to unplug the pc and replug the pc.

[gob]

This is indeed the engine causing this from the devs coding for the game. Just like how they developed the framerate being tied to your range & damage output.

[Skygaze]

Originally posted by SolutionS:

Originally posted by Dovah:

Removing my underwolt/overclock for my GPU fixed it for me. I still have MSI Afterburner and Riviatuner on in the background btw.

Yea its a problem with the 13th and 14th gen intel chips, OP is likely experiencing the same thing. You are both eligible for RMA but intel is extremely laggin on any rma since 99% of their chips released faulty. Its best to set all the power targets manually in the bios and turn off any mother board boosting like Multicore enchancement for asus.

I've ran a stability test on it and it came up all clear, I've also underclocked it and haven't had issues in other UE5 games. Funnily enough, I was able to play for about 3h without crashing after I toggled some settings in the launcher so that it doesn't close when you open the game, and made it minimise to the system tray.
Edit: Also AMD users are having the same issues, as I mentioned. 13-14 series instability was my first guess but it's not the case here.

[BingusDingus]

The only fix that has worked for me consistently is that whenever the game finally crashes I verify the files, after that the game doesn't crash for quite some time.
My problem seems to be the files corrupting on exiting the game, and it does so infrequently.

[Dovah]

Originally posted by BingusDingus:

The only fix that has worked for me consistently is that whenever the game finally crashes I verify the files, after that the game doesn't crash for quite some time.
My problem seems to be the files corrupting on exiting the game, and it does so infrequently.

Just tried that, turned my undervolt back on and worked fine after verify the files. What's weird is all the files were there,but it still helped for some reason. They really broke this game with the update...

Edit: It's worth noting that Frame gen can mess up your game due to sudden intense areas, ie Doctor Strange dropping a portal in the middle of the main objective, it does some weird stuff so try turning frame gen off , if you have it on.

[Zhohan]

Using AMD CPU and frame-gen is disabled. Think the game is just buggy and they're taking their sweet time fixing it.

[Spoonmoose]

I’m not well versed in coding but after another GPU crash dump I put the report into windbg. One exception code that kept appearing was Code 8000 suggests invalid memory access: The RaiseException function in KernelBase was involved, the application attempted to raise an exception that wasn’t properly handled leading to the crash.

Does this mean anything at all to anyone?

[Gluten Disc]

I've had two black screen crashes with this game recently. Bluescreen viewer showed a fault at ntoskrnl. One had a blank bug check, the other with Memory Management. The former happened mid match. Latter, interestingly enough, occurred while closing Marvel Rivals. Did the checks OP mentioned. Memtest86, SMART scans, sfc, dism, etc. Meet the hardware requirements, yadda yadda.

Prior to these crashes, very rarely had problems with the game. One thing of note, both these crashes occurred after a multi-hour play session with more matches occurring on Midtown than I was usually getting since the start of Season 1. I have heard rumors about Midtown being particularly finicky in performance and I believe that just recently, the Midtown only playlist was removed in favor of putting the map more into the regularly rotation. I could be wrong, but quite possibly something to lookout for. It was the only real change I could come up with that was involved in both crashes.

Been doing tests today to see my stability with the game. I did a full uninstall of the game including the leftover files that aren't removed. Reinstalled and used the Launcher's Clear Local Config files. Then I played a few matches, closed the game, restarted, played a few, etc. So far hadn't crashed while the PC has remained on the entire time.

I'm led to believe and agree that it is a memory leak issue but how it crashes seems to be dependent on what ends up being the straw that breaks the camel's back at a given moment. This game has quite a few things running under the hood to which I am led to believe also adds to the memory leak issue. My crash during the game's shutdown leads me to believe that something, such as the Anti-cheat, or some other background process may also chew up more memory than it should. Leading back to my Midtown map theory, that may also have more of a mem issue, but I'd rather find methods to keep my system from crashing rather than test to make it crash.

[jo.G O.g]

Try installing ISLC (intelligent standby list cleaner). Set your list to purge when size is at least 1024mb and free memory is lower than 1024mb. Then click start.

See if it helps.

My specs are somewhat similar to yours. 3080ti, i7 processor, 32gb ram. I haven't had any crashing at all.

Worth a shot.

[Kadu]

FPS Drops to 1

Im experiencing mass fps drops that lasts for 20 to 40 seconds. Every now and then but in the first game always happens. Tried a bunch of stuff listed here, pretty much everything that im able to, nothing solves.
Also, changing in-game graphics settings doesnt change a thing, just makes the game slightly uglier.

Besides that the game runs smoothly on High.

I dont know if anyone is running on 2560x1080, but most people complaining is not.

My config:
4070 super, 12gb vram
r5 3600
16gb ram
game running on a m2 nvme