Try to run the engine as an administrator. The crash is related to Unreal Engine or it’s related assets trying to access a restricted memory address.
After a windows update
you should always reinstall your video drivers.
It sometimes helps to check the “clean install” box in the gfx driver install
sometimes you need to reinstall them twice in a month because of win updates.
@EliasWick@christuusgnosis honstly, nothing worked, i am thinking of reinstalling windows and UE, i think i installed design Doll a week ago and it changed things that i don’t know what they are.
BUT, if i work on my laptop screen, or the 2nd screen only, there is no crashs -.-
If you have the possibility to reinstall both Windows and Unreal Engine that would be great. If you still have issues, it’s either hardware or from the Unreal Engine side of things.
Please let us know how it works after the reinstall.
It would be good if you could let us know how to perform some sort of logging or debugging so we can at least discern what is at fault. It seems that Microsoft will always blame the software running on it, and the 3rd party software will always blame the environment.
Save yourself the hassle, and do not re-install your OS. I did on 2 separate systems, and all it did was waste an entire day.
For me, UE5 launches and works, but only for a few minutes and then crashes with no real information. Irrelevant of how clean an install. Even if I launch it, and just move the mouse and click randomly, it fails after a few minutes.
The ONLY thing I can do is revert back to UE4, which is fine for a pleb user, but if I had plans to maybe finance my Epic Games account due to the licensing legislation, why would I when the software is not working and the support is nowhere to be found.
Is there a support portal of any description or do we just moan on these forums until something happens maybe?
Not enough info to pin the exact reason. But here is a similar topic I responded to in which the crash is also in UE5, also references DX12 and also accesses invalid memory:
Quite likely it is just a simple bad line of code in the engine not checking for a nullptr. There really is no reason to modify your own system in an attempt to “fix things” if it’s an engine issue.