Hi all,
This crash has been a persistent thorn in my side. I can’t figure out how to properly debug what may be causing it. How can I debug this issue to figure out what’s causing it?
0xffffffffffffffff looks like the end of the heap/stack. Are you running low on resources?
ive been getting this on and off and i think its to do with blueprints and redirectors, i get an ubergraph error alongside it sometimes. Updating redirectors, and sometimes rebuilding the cpp files sometimes fixes it sometimes doesn’t. other posts said that its a currupt file, but i wasn’t sure on that but my current branch doesn’t seem to have the issue. If you don’t use version control make sure to or else you wont be able to even cook your project with this error it seems
Nothing that would really indicate so. Framerate is stable and everything, the crash is quite random. It could happen 30 seconds into a session or 30 minutes.
f is the last digit in hex so it seems it’s at the ‘end’ of something; it’s all f’s… seems odd
maybe some kind of internal buffer?
download the debug symbols for your engine and provide the proper crash call stack next time you recevie the crash again. WIthout it it’s only guessing.
Well, or just attach debugger and look where the things goes wrong (engine’s symbols are still required)
Ok so I think that was the issue. I recalled consistently crashing whenever I tried to “Fix up Redirectors” on the whole project. I instead went through each folder and clicked “Fix up Redirectors” for each one, including the main content folder at the end. I tried a prolonged session with a friend and there was zero crashing, so I think it did have to do with redirectors.
I’ve seen these types of errors pop up in quite a few DX12 games(not just UE based games) lately and from what I’ve seen, a lot of people have troubles reproducing the crashes.
Are you using a 13th or 14th gen Intel CPU by chance? There have been a lot of instability issues with them and they have had to do all kinds of emergency BIOS and microcode updates this year over some bug with voltage limit regulation causing permanent physical damage to the CPU that can get progressively worse and worse. I think it mostly affects the 13/14700 and 13/14900 variants. The Intel 0x129 microcode is supposed to fix the voltage regulation. It won’t undo any damage done if the CPU has been damaged, but it can prevent it from getting worse.
I don’t have an intel CPU, I have an AMD Ryzen 7 5800x. It was also a consistent issue across different testers with different setups, but it went away after fixing up redirectors anyways. I’ll report back to this thread if it returns.