I get crashes when using the editor every 30sec to 5 mins. No correlation to activity. Then after deleting my intermediates, configs, ect…, restarting, sometimes several times. Often have to start the editor then rollback all the changes it makes in fork. It will resolve itself for 8+ hours. I work till end of day with no issues. Come back in the morning and boom. Crashing until I go through a 1-2 hour process to fix the project again.
One other maybe related behavior. Floor_400x400.uasset from starter content continually checks out as changed. No idea why, again I’ve tried everything.
Any idea what is going on? I’ve tried everything I can find online. I’m completely lost.
Hey there @TheDogtoy! I don’t believe the starter content to be at fault here, but best not to rule anything out. What kind of source control are you using that’s reflecting checked out in editor? Are you using a gitignore file? If not, some data that shouldn’t be synced could be causing issues when pulling.
Agreed, I doubt that is the problem. What’s the full error stack it’s making on crash? I’m guessing a generic memory allocation error as mentioned in the title.
It’s always a slightly different error code. Tends to be something like this. The address will change, sometimes all zeros. Once it’s unstable there are some others too but always engine code.
Fixing up redirectors/restarts/yada yada will sometimes fix it, but not 100% able to fix the correlation. I’ve tried everything I’ve found online from reinstalling drivers to changing my clock speed, to resetting my gpu settings.
This computer is also my gaming PC, so I play a ton of unreal games on it. No crashes. Instability is only in editor.
Editor: 5.4.4
PC: Windows 11, 13900k, 4090, 128 gigs ram.
This error specifically stems from GPU drivers (usually) as nvwgf2umx.dll is an Nvidia driver, so this one might be related but also might be multiple issues at play.
I’ve tried everything in there with no luck. Got this crash today, slightly different.
Assertion failed: RayTracingInstance.GeometryRHI [File:D:\build++UE5\Sync\Engine\Source\Runtime\Renderer\Private\RayTracing\RayTracing.cpp] [Line: 1236] Ray tracing instance must have a valid geometry.
Yes, tried DX11 but no change. Currently switching to a different computer for a few days to see if its related to the project. (this is my personal not work project). The computer that is experiencing the issue has no stability issues with other software or games, but I have found other posts where people that specifically have a I9 13000k and 4090 gpu combo are having issues with Unreal Engine.
Going to see if moving to a computer with a I9/3080 resolves the issue.
There were reported issues with the 13th and 14th generation intel CPUs, and sometimes presented as graphical issues albeit rarely. The fixes from the other thread should have had an affect when it comes to GPU sided issues. Let me know how your testing goes!
Still seems DX12 graphical errors are occurring, but I’m glad they are less frequent. Are these during specific operations, such as working on materials or in a high GPU usage scene?
Seams totally random. Sometimes when hitting play, sometimes when just editing a blueprint, sometimes, when just opening an editor window, sometimes when just scrolling a blueprint/graph, testing the game PIE, looking at the content browser. Never when just idle though.
Very odd that it “goes away” on the problematic PC if I delete everything, reinstall, do random driver resets, yada yada for a day or so.
The laptop crashes are so rare it is not an issue, though this issue is sad because the problem PC was built specifically for Unreal
On the laptop, I probably have had one or two other non gpu related crashes over the past few weeks but they fall into the normal “engine crashed for reasons that are hard to reproduce, like hitting undo at a specific time or something”. All seams in-line with every other unreal project though, so nothing to bring up. It is odd that the GPU crash is consistently popping though
