How to I stop my UE5 project from crashing on startup?

My project started crashing every time I started it up and I never added or removed any plugins or anything, the project started crashing out of the blue and I can’t find any solution to the error anywhere.

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000550

UnrealEditor_Foliage
UnrealEditor_Foliage
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_CoreUObject
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
kernel32
ntdll

If anyone has any solution to this error, I’d really appreciate the help

1 Like

Hi Jackzinger,

One thing to try would be deleting your ‘saved’ and ‘intermediate’ folders of your project. These contain cached info and will be regenerated upon launch.

To clear you engine settings delete yourproject/Config/DefaultEngine.ini

Optional, but if you wanted to get more info about the crash you could install Debugging Symbols (Dropdown next to ‘Launch’ on your engine version → Options → Editor symbols for debugging)

Another thing to try would be to copy the ‘content’ folder into a new project and see if you can open the new project.

Let us know if any of those solve it, welcome to the forums.

7 Likes

Hey there, try removing high poly assets from content folder before launching the project. Also try opening clean UE project and then open your project right after (having both opened), remove heavy assets, set texture resolution to lower settings and enable virtual texturing. I assume you work with large project, if not, above mentioned will probably not going to help. Good luck! )

I removed the ‘Saved’ and ‘Intermediate’ files, and I was still getting the same crash report, but when I removed the ‘defaultengine.ini’ I was able to open the project, but it wasn’t the project I was working on, it was a terrain made up of tiles with mountains in the distance in all directions. Also, all of my actors were gone, and they were not in a different level, they were just gone. I also tried moving the ‘content’ folder to a new project and I still got the same crash report. Here is the more detailed crash report

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000550

UnrealEditor_Foliage!ResolveObjectHandle() [D:\build++UE5\Sync\Engine\Source\Runtime\CoreUObject\Public\UObject\ObjectHandle.h:321]
UnrealEditor_Foliage!AInstancedFoliageActor::PostLoad() [D:\build++UE5\Sync\Engine\Source\Runtime\Foliage\Private\InstancedFoliage.cpp:4512]
UnrealEditor_CoreUObject!UObject::ConditionalPostLoad() [D:\build++UE5\Sync\Engine\Source\Runtime\CoreUObject\Private\UObject\Obj.cpp:1103]
UnrealEditor_CoreUObject!UObject::PostLoadSubobjects() [D:\build++UE5\Sync\Engine\Source\Runtime\CoreUObject\Private\UObject\Obj.cpp:1137]
UnrealEditor_CoreUObject!UObject::ConditionalPostLoad() [D:\build++UE5\Sync\Engine\Source\Runtime\CoreUObject\Private\UObject\Obj.cpp:1086]
UnrealEditor_CoreUObject!EndLoad() [D:\build++UE5\Sync\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:1701]
UnrealEditor_CoreUObject!<lambda_c8710bcd35c9e247c18bb173ed0f9483>::operator()() [D:\build++UE5\Sync\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:1264]
UnrealEditor_CoreUObject!LoadPackageInternal() [D:\build++UE5\Sync\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:1366]
UnrealEditor_CoreUObject!LoadPackage() [D:\build++UE5\Sync\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:1520]
UnrealEditor_CoreUObject!LoadPackage() [D:\build++UE5\Sync\Engine\Source\Runtime\CoreUObject\Private\UObject\UObjectGlobals.cpp:1500]
UnrealEditor_UnrealEd!UEditorEngine::Map_Load() [D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\EditorServer.cpp:2694]
UnrealEditor_UnrealEd!UEditorEngine::HandleMapCommand() [D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\EditorServer.cpp:6232]
UnrealEditor_UnrealEd!UEditorEngine::Exec() [D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\EditorServer.cpp:5722]
UnrealEditor_UnrealEd!UUnrealEdEngine::Exec() [D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\UnrealEdSrv.cpp:659]
UnrealEditor_UnrealEd!FEditorFileUtils::LoadMap() [D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\FileHelpers.cpp:2761]
UnrealEditor_UnrealEd!FEditorFileUtils::LoadDefaultMapAtStartup() [D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\FileHelpers.cpp:4336]
UnrealEditor_UnrealEd!FUnrealEdMisc::OnInit() [D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\UnrealEdMisc.cpp:359]
UnrealEditor_UnrealEd!EditorInit() [D:\build++UE5\Sync\Engine\Source\Editor\UnrealEd\Private\UnrealEdGlobals.cpp:134]
UnrealEditor!GuardedMain() [D:\build++UE5\Sync\Engine\Source\Runtime\Launch\Private\Launch.cpp:159]
UnrealEditor!GuardedMainWrapper() [D:\build++UE5\Sync\Engine\Source\Runtime\Launch\Private\Windows\LaunchWindows.cpp:147]
UnrealEditor!LaunchWindowsStartup() [D:\build++UE5\Sync\Engine\Source\Runtime\Launch\Private\Windows\LaunchWindows.cpp:283]
UnrealEditor!WinMain() [D:\build++UE5\Sync\Engine\Source\Runtime\Launch\Private\Windows\LaunchWindows.cpp:330]
UnrealEditor!__scrt_common_main_seh() [d:\a01_work\6\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288]
kernel32
ntdll

If you know what’s going on, I’d really appreciate any kind of help

1 Like

Thanks for the extra info. Here is an idea,

Since ‘Foliage’ is mentioned in the callstack try this:

Before opening the map that crashes open the console (tilde key) and type showflag.instancedfoliage 0

Now try opening the map. If it does open, try opening the foliage mode and deleting all foliage.

I opened UE5 and before starting my project, I tried to open the terminal by pressing the ‘~’ key, but the terminal wasn’t opening. Do I need to be in the project in order to open it?

Yes, you’d need to be ‘in editor’ as opposed to the loading screen.

The map that loads on startup is defined in config/DefaultEngine.ini (that’s why it loaded the default map when you deleted it before) - So try loading into that map and entering the command.

I’ve heard of some foreign keyboards having trouble opening the console, in UE5 there is now a ‘enter console command’ text box at the bottom of the editor!

1 Like

I loaded up the project without the DefaultEngine.ini and it took me to the default level, and I entered the command, but when I hit enter, nothing seemed to change, so I put the original DefaultEngine.ini back in the files and reopened the project, but I still got the same crash report

So, if you paint some foliage in the default level, you’ll see it disappear.

My assumption is that you have foliage in your level that is crashing when opening the level.

If you haven’t used / are not familiar with the foliage painting system this may be a dead-end.

I did use the foliage paint tool for my project, but I can’t get into the project to remove it which seems to be the problem

If you delete the line “EditorStartupMap…” (remember to save the document) in your broken projects DefaultEngine.ini are you able to open the project?

1 Like

I can open the project, but it’s just the default map

Cool, so the situation is now you are in your project, but if you try and open that map your project will crash.

Go ahead and paint some foliage in the default map so you can be sure you’re entering the command correctly.

Enter the command. - The foliage will disappear.

I’ve verified that hiding the foliage via this command should persist through level changes.

Can you open the crashing level now?

I entered the command correctly and the foliage disappeared, but I still cannot open the crashing level

Thanks for checking that, unfortunately I think It’s now safe to classify that idea as a ‘dead end’

If you have a previous version of this level that you can open, you can copy-paste actors between levels to rebuild it. I can’t think of any other ideas right now. If you wait until 5.1 there is a small chance this crash will be fixed.

Okay, thanks for your help

1 Like

LoginId:6c5182d340f1e553a36c9e87baaa5e2c
EpicAccountId:3b1ba69cbbce43c9aa609e6ed6d70652

Unhandled Exception: 0xe06d7363

KERNELBASE
VCRUNTIME140
MixedRealityInterop
MixedRealityInterop
MixedRealityInterop
MixedRealityInterop
MixedRealityInterop
UnrealEditor_WindowsMixedRealityHMD
UnrealEditor_WindowsMixedRealityHMD
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
kernel32
ntdll

Anyone here who can help me, i am stuck in this error when i run my project then i face this error

I poured my soul into my project only to have it’s delicate ■■■ break for some unknown reason, thanks to you, it is saved. EPIC should really think about a simple ‘Repair’ button to examine and fix issues

Thanks!

1 Like

I just verified my installed version of Unreal Engine 5.3.2 and it worked, the project was not crashing anymore,

This fixed my crash! Deleting the DefaultEngine.ini folder forced the editor to recompile everything, so I guess that it fixed my material’s issue.

1 Like