# UE 5.7 Pathtracer Fatal error in large scenes

**URL:** <https://forums.unrealengine.com/t/ue-5-7-pathtracer-fatal-error-in-large-scenes/2678561>\
**Category:** Rendering\
**Tags:** Path-Tracer, unreal-engine, dx12, question\
**Created:** [November 25, 2025, 1:24pm UTC](https://forums.unrealengine.com/t/ue-5-7-pathtracer-fatal-error-in-large-scenes/2678561 "2025-11-25T13:24:45Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![SinnPhilipp](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SinnPhilipp](https://forums.unrealengine.com/u/SinnPhilipp)\
**Post date:** [November 25, 2025, 1:24pm UTC](https://forums.unrealengine.com/t/ue-5-7-pathtracer-fatal-error-in-large-scenes/2678561/1 "2025-11-25T13:24:45Z")

</div>

Hello,

after upgrading a project from 5.5 to 5.7, I get the following crash in Pathtracer:

`Fatal error: [File:D:\build\++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Util.cpp] [Line: 1030] `

`Adapter->CreateCommittedResource( InDesc, GetGPUMask(), HeapProps, InInitialD3D12Access, InResourceStateMode, DefaultAccess, InClearValue, &NewResource, InName, false) failed `

`at D:\build\++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12PoolAllocator.cpp:524 `

`with error E_INVALIDARG`

It happens in Editor and MRQ (Remote Rendering, Editor closed).

It seems to be an issue with the amount of data. When I remove some meshes, it renders fine. No particular mesh seems to be the culprit but just the total amount of data. I cannot share my level due to confidentiality but it is has around 85 000 static mesh actors.

I changed some pool and heap Cvars but to no avail. I tested it on different machines but neither more RAM nor VRAM make a difference. Nanite makes no difference either.

I did not run into this limit in 5.5. I could view this and even larger scenes in Pathtracer without any issues.

Any suggestions on what else to try or data I could provide to analyse the issue are greatly appreciated. 🙂

Best regards,

Philipp

---

<div class="post-metadata">

**Author:** ![d1myan](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@d1myan](https://forums.unrealengine.com/u/d1myan)\
**Post date:** [December 2, 2025, 7:05pm UTC](https://forums.unrealengine.com/t/ue-5-7-pathtracer-fatal-error-in-large-scenes/2678561/2 "2025-12-02T19:05:34Z")

</div>

![Screenshot_5](https://d3kjluh73b9h9o.cloudfront.net/original/4X/b/8/e/b8e49d7f31ad67ebcf36ac63462fe9aadc28e886.jpeg)

I get the same error when loading one Level, which worked well on unreal 5.6. The level on Lumen and I was eventually able to load it when I deleted the geometry uploaded via datasmith from 3dsmax. I was waiting for it to be fixed on 5.7.1, but the error remained in the same place. Nvidia rtx a4000 graphics card and latest Studio 581.80 drivers

---

<div class="post-metadata">

**Author:** ![EvanHammel](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/evanhammel/32/1194625_2.png) [@EvanHammel](https://forums.unrealengine.com/u/EvanHammel)\
**Post date:** [December 2, 2025, 10:05pm UTC](https://forums.unrealengine.com/t/ue-5-7-pathtracer-fatal-error-in-large-scenes/2678561/3 "2025-12-02T22:05:17Z")

</div>

Did you guys check in the logs that Unreal outputs to your project directory Saved/Logs folder? This has helped us troubleshoot crashes many times. There will be a lot more information there and help pinpoint what is crashing the engine.

---

<div class="post-metadata">

**Author:** ![SinnPhilipp](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SinnPhilipp](https://forums.unrealengine.com/u/SinnPhilipp)\
**Post date:** [December 3, 2025, 8:25am UTC](https://forums.unrealengine.com/t/ue-5-7-pathtracer-fatal-error-in-large-scenes/2678561/5 "2025-12-03T08:25:28Z")

</div>

Thank you for the suggestion. Unfortunately, I did not find anything useful in the log. This is the relevant part:

> [2025.12.03-08.08.42:205][105]LogD3D12RHI: Display: D3D12 CreateCommittedResource failed with params:  
> Heap Type: 1  
> Heap Flags: 4096  
> Resource Dimension: 1  
> Resource Width: 16893824  
> Resource Height: 1  
> Array Size: 1  
> Mip Levels: 1  
> Format: 0  
> Resource Flags: 0  
> [2025.12.03-08.08.42:205][105]LogD3D12RHI: Error: Adapter-\>CreateCommittedResource( InDesc, GetGPUMask(), HeapProps, InInitialD3D12Access, InResourceStateMode, DefaultAccess, InClearValue, &NewResource, InName, false) failed  
> at D:\build++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12PoolAllocator.cpp:524  
> with error E\_INVALIDARG
> 
> [2025.12.03-08.08.42:216][105]LogWindows: Error: appError called: Fatal error: [File:D:\build++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Util.cpp] [Line: 1030]  
> Adapter-\>CreateCommittedResource( InDesc, GetGPUMask(), HeapProps, InInitialD3D12Access, InResourceStateMode, DefaultAccess, InClearValue, &NewResource, InName, false) failed  
> at D:\build++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12PoolAllocator.cpp:524  
> with error E\_INVALIDARG
> 
> [2025.12.03-08.08.42:216][105]LogWindows: Windows GetLastError: Der Vorgang wurde erfolgreich beendet. (Translation: Process completed successfully) (0)  
> [2025.12.03-08.08.50:725][105]LogRHI: Error: Breadcrumbs ‘RHIThread’
> 
> - Scene
> - RenderGraphExecute - /ViewFamilies
> - SceneRender - ViewFamilies
> - Frame 17104
> 
> [2025.12.03-08.08.50:725][105]LogThreadingWindows: Error: Runnable thread RHIThread crashed.  
> [2025.12.03-08.08.50:725][105]LogWindows: Error: === Critical error: ===  
> [2025.12.03-08.08.50:725][105]LogWindows: Error:  
> [2025.12.03-08.08.50:725][105]LogWindows: Error: Fatal error: [File:D:\build++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Util.cpp] [Line: 1030]  
> [2025.12.03-08.08.50:725][105]LogWindows: Error: Adapter-\>CreateCommittedResource( InDesc, GetGPUMask(), HeapProps, InInitialD3D12Access, InResourceStateMode, DefaultAccess, InClearValue, &NewResource, InName, false) failed  
> [2025.12.03-08.08.50:725][105]LogWindows: Error: at D:\build++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12PoolAllocator.cpp:524  
> [2025.12.03-08.08.50:725][105]LogWindows: Error: with error E\_INVALIDARG

The rest is just the stack trace.

Also happens in 5.7.1

---

<div class="post-metadata">

**Author:** ![PhilippeMinuit](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@PhilippeMinuit](https://forums.unrealengine.com/u/PhilippeMinuit)\
**Post date:** [January 21, 2026, 1:59pm UTC](https://forums.unrealengine.com/t/ue-5-7-pathtracer-fatal-error-in-large-scenes/2678561/6 "2026-01-21T13:59:55Z")

</div>

I have found this is a combination of using Hardware ray tracing, real time captured sky lights and large scenes. In my case, we use Ultra dynamic sky and the datasmith pipeline to import large architectural projects and render them for clients. 5.7.1 is completely useless to us now that this is impossible. I have not yet found a fix for this issue

---

<div class="post-metadata">

**Author:** ![SinnPhilipp](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SinnPhilipp](https://forums.unrealengine.com/u/SinnPhilipp)\
**Post date:** [January 26, 2026, 9:17am UTC](https://forums.unrealengine.com/t/ue-5-7-pathtracer-fatal-error-in-large-scenes/2678561/7 "2026-01-26T09:17:33Z")

</div>

I created a bug report Case # 23429588

---

<div class="post-metadata">

**Author:** ![SinnPhilipp](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@SinnPhilipp](https://forums.unrealengine.com/u/SinnPhilipp)\
**Post date:** [February 16, 2026, 2:39pm UTC](https://forums.unrealengine.com/t/ue-5-7-pathtracer-fatal-error-in-large-scenes/2678561/8 "2026-02-16T14:39:24Z")

</div>

The issue seems to be fixed in UE 5.7.3. I could render the previously crashing scene in Editor and MRQ.

Thank you for the fix!
