[Gpu hung] RenderVirtualShadowMaps(Nanite) - NodeAndClusterCull

Development Rendering
, ,
1

All the crash file is below.

2

重现步骤
Hi, we have met gpu hung in our development game. ​The nv-gpudump shows the crash is related to PageRectBoundsBuffer memory access invalid. It happens on nvidia 4060 when loading the level.[Image Removed]

3

Hello,

We are seeing similar GPU crashes in this area but don’t have a known fix yet. For now we’re tracking the work on this issue here: Unreal Engine Issues and Bug Tracker (UE\-230827) The crash is in a different function and pass, however it appears to have similar characteristics.

4

Thanks, Alex. I have some new info. If i turned off async compute transient aliasing(r.RDG.AsyncComputeTransientAliasing

0 ), the crash seems not happened any more.

5

By any chance do you have a way to repro this issue that you can share with us?

6

Hello, I just found this thread looking for more info on this crash, and I may have a consistent repro in the editor with the City Sample project:

  • Create a new project from the City Sample fab with UE 5.5.4
  • Open Small_City_LVL
  • Load a world partition area and save so that it loads that area when opening the map
  • Switch to software Lumen in the project settings (disable raytracing)
  • Restart and open Small_City_LVL while shaders are still compiling (using -noshaderddc if necessary)
  • At this point, I get the NodeAndClusterCull GPU crash while the level loads 100% of the time.

GPU info:

[2025.08.30-17.38.22:903][  0]LogD3D12RHI: Found D3D12 adapter 0: NVIDIA GeForce RTX 4080 (VendorId: 10de, DeviceId: 2704, SubSysId: 13bd196e, Revision: 00a1
[2025.08.30-17.38.22:903][  0]LogD3D12RHI:   Max supported Feature Level 12_2, shader model 6.7, binding tier 3, wave ops supported, atomic64 supported
[2025.08.30-17.38.22:903][  0]LogD3D12RHI:   Adapter has 16050MB of dedicated video memory, 0MB of dedicated system memory, and 32651MB of shared system memory, 2 output[s]
[2025.08.30-17.38.22:903][  0]LogD3D12RHI:   Driver Version: 566.03 (internal:32.0.15.6603, unified:566.03)
[2025.08.30-17.38.22:903][  0]LogD3D12RHI:      Driver Date: 10-15-2024
7

Sorry, I am unable to consistently reproduce this issue.

8

[Content removed] does the crash you’re experiencing happen in 5.6 with those steps?

9

Ah, sorry I misread this ticket, I’ve only tested this for 5.5.4