Heyo, I have been having alot of issues the past few days with crashing in UE5.6.1, I set myself a challenge to build a game in a month and since the 1st I have had to make 6 different projects because they all end up becoming ‘‘Bricked’’ so if i try to launch the project it just instantly crashes. Obvioulsy I never got too far into development in every project but its now averaging out to more than 1 project a day becoming unsalvagable. All the crashes have happened at different times while I was doing different things but most of them seem to be when im altering AnimGraphs and/or BPs so pretty standard things. Has anyone else had these issues? I will also post my hardware here incase there are issues that I do not know about with my specific hardware.
I can crash from the editor, viewports, honestly they have been from anything, the main error is something like ACCESS_VIOLATION? Nothing on windows, no OC and its set to performance. Im thinking about trying slightly older versions rather than 5.6.1 and see if its still crashing? I have also heard rumors that AMD GPUs can struggle compared to NVIDIA in UE but I would have thought with the 7900XTX and its power it wouldnt have any issues
You mention ACCESS_VIOLATION as the main problem. Is you project c++ based? If so are you doing nullptr checks before accessing data that may not be initialized correctly yet?
Actor initialization order is not guaranteed. Perhaps your game initializes actors in random order. Things like memory cache misses and disk speed can change the loading outcome. Are you accessing actors without checking if they are ready?
Editor and published game loading works slightly different so this can also cause crashes if not tested extensively.
If you are using blueprints only then don’t forget to use the isValid node to check if an uncertain node you are accessing is ok and ready.
Have you done any bios updates lately? Maybe you have the same problem as the op of this thread regarding XMP/DOCP in the bios settings?
Edit:
You can also try running HWMonitor in parallel with the engine and observe the cards temperatures (hotspot mostly). And see if the instability may come from the card hitting a thermal limit causing instability. If so then you could try setting the fan curve to be more aggressive so that it cools the card faster. If temps are a problem then a thermal repaste could also help the problem if it’s hardware related.
I’ve also noticed that a lot of people are getting 7900xtx crashes when discord is on. It seems to use hardware acceleration that causes problems.
Other people mention to install the display drivers in “drivers only” mode (in adv options)
There are posts where people had RAM problems that were caught with memtest. It’s grasping at straws but you could do a memory test just in case. Maybe the card is getting bad data along the way from a bad part of one of your Ram sticks.
Power fluctuations could also be a thing if it’s random. If you have access to a UPS that might clear up any power dips or spikes that could cause instabilities (sometimes even changing a wall outlet can help)
I am using BP not c++, but after restarting a project on UE5.4 I have not crashed yet but again I have not done the AnimGraph yet, still just setting up inputs like jumping/sprinting etc so we will see today as I get further into it if anything happens, I have discord closed today too so we will see if that helps!
I would suggest looking into the latest KB5063878 windows update (and removing it). If your project is on an SSD then it could be effected. There have been some instances where windows would slowly corrupt data over time on the drive even when large files aren’t being copied. (JayzTwoCents had his pc crash just by playing F1)
It seems to cause problems mostly with SSD’s that have Phison controllers.
You could try removing it from the windows update history and pause updates for now.
I have been looking into this, one of my friends has also had this issue on a very big project so we are currently trying to troubleshoot and find a solution but we do suspect it could be the update, will confirm soon if that seems to be ther problem