Unreal 5.3.2 crashes constantly despite having 4090 and 128 GB Ram

Development Getting Started & Setup
,
1

Hey everyone, I’m a new member here. I’m encountering a frustrating issue while working with Unreal Engine. I’m attempting to create a short film, but Unreal Engine 5.3.2 keeps crashing repeatedly. Whether I’m opening a city sample or a blank project, it consistently crashes. I’ve tried numerous solutions found online, from reinstalling Unreal Engine to redownloading the city sample, but nothing seems to work. Interestingly, switching from DirectX 12 to DirectX 11 reduces the crashes, but it’s not a viable solution as it limits my usage of the city sample.

My PC specs are as follows:

  • Intel i9 13900k
  • Nvidia RTX 4090
  • 128 GB RAM

I’ve ensured that my studio drivers are up to date, adjusted settings in the Nvidia Control Panel and Windows Display settings to prioritize Unreal’s usage of my RTX 4090, and increased the page file size. It’s worth noting that I don’t experience this issue with other 3D applications I use.

Please help me to resolve this issue.

Here are the errors I get when the engine crashes.

First Error

Assertion failed: InHashSize > 0u && InHashSize <= 0x10000 [File:D:\build++UE5\Sync\Engine\Source\Runtime\Core\Public\Containers\HashTable.h] [Line: 470]

UnrealEditor_RenderCore
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_RenderCore
UnrealEditor_RenderCore
UnrealEditor_Engine
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
kernel32
ntdll

Second Error

Assertion failed: bSucceed [File:D:\build++UE5\Sync\Engine\Source\Runtime\RenderCore\Private\ShaderResource.cpp] [Line: 629]

UnrealEditor_RenderCore
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
kernel32
ntdll

Third Error

Assertion failed: NextPageByteOffset + PageSize <= MaxPageBytes [File:D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Private\Rendering\NaniteStreamingManager.cpp] [Line: 372]

UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
kernel32
ntdll

2

The exact same thing keeps happening to me and I get the same exact errors. It is so annoying, I can work for like 3-5 minutes before me moving an asset crashes unreal. I also have a beefy computer so this error bewilders me.

1 Like
3

You’re lucky it gives you 3-5 mins, mine only lets me see the editor for a couple seconds and lights off. My specs are the same and I have updated everything, so far no stone left unturned. This issue started exactly 2 weeks ago.

4

It’s worth a try! I also read somewhere that there has been a particular problem with 4090 and Unreal.

1 Like
5

This is super frustrating when it happens.

Things to try include downloading some USB installer that will let you run memtestx86 and PRIME95, for some stress testing of the CPU side.

Another thing to look at is the power supply.

See also:

6

I already have a latest Studio drivers. I tried switching between Game Drivers and Studio Drivers. Both have the same problem.

7

I tried running benchmarks and my benchmarks are at par with others on the internet. No problems found in my CPU or GPU.

8

I will never buy another Intel CPU again. Willing to bet everyone in this reply thread has a 13900k including myself. It’s not the GPU. It’s that garbage furnace the 13900k.

Can’t wait until 5090s and the next line of AMD release. Def switching to AMD on my next build.

2 Likes
9

Exact same issue here, also 4090 with a 13900k

constantly crashing on nanite, not loading meshes properly, blue screening everytime i try to load nanite maps etc. But then I check my task manager and my GPU is only using like 10% of its capacity.

10

13900k crashes in UE5 all versions. Since 1 year I bought 13900k then all projects crash at meannigless points. I tried to undervolt such things then still crashes more than that BSODs, Even at youtube PC crashes to BSOD. There are P-cores E-cores, I follow during UE5 work, the E-cores doesn’t handle anything. I had 3900x 24 cores was working perfect. What kind of stupid I am got 13900K for more cores not working crashing in any simple work. Intel frustration is over, I’m looking for 7950x3D AMd for UE works, All my job is pending due to this Intel processor.

11

Yeah 1914900k and RTX 4090 and constant issues. Just now making a landscape and one small undo button has crashed the entire thing and lost all progress with it. It has perma killed another project. I’ve done all the bios stuff and updates possible (before that it was way worse and almost impossible to play any DX12 game).

Thinking of reconfiguring the entire build to AMd. Annoyingly I was AMd before and fancied a change

12

Just like you all, same issues here, except my problems stem from use with the VIVE Pro 2 headset in UE 5.3.2
i9-13900KF, 24 cores
RTX 4090
64 GB RAM

UE 5.3 normally works fine, unless I try running a project in VR. Then it gets extreme lag and jittery, GPU maxes out, CPU shoots up and then either a project crash or complete desktop freeze for 30sec - few minutes. And here I thought these system specs were plenty for UE development :frowning:
If anything, im just adding my name to the list in case a fix comes out soon.

13

I also met this problem. After my attempts, I found that it is because the Settings of the below picture need to be enabled in the urban instance building I introduced, but this error will occur when the packaging is enabled, and it will not be enabled if it is not enabled. I wonder if yours is not.
Delete it from configuration file defaultenine. ini
r.VirtualTextures=True
r.AllowStaticLighting=False

image

image
image891×176 22.3 KB

14

I know i am a bit late to the party but if you are using world partition try changing the Runtime Hash Default Class in the project settings to SpatialHash