Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
4
Found in
6000.0.47f1
6000.1.1f1
6000.5.0a1
Issue ID
UUM-104889
Regression
No
[Intel] Crash on BufferD3D12::BeginWrite when opening a newly created URP project with DirectX12 set as the default graphics API
Reproduction steps:
1. Create and open a new Universal 2D/3D project
2. Observe the crash
Reproducible with: 6000.0.47f1, 6000.1.0f1, 6000.1.1f1, 6000.1.0b3
Reproducible on: Windows 10 (1809) (user's), Windows 11 (24H2) (user's)
Not reproducible on: No other environments tested
Notes:
- Not reproduced by CQA
- Not reproducible with newly created BiRP project
- Not reproducible when launching Editor with -force-vulkan or -force-d3d11 command-line argument
First few lines of stack trace:
0x00007FFBDEE9EFD8 (Unity) BufferD3D12::BeginWrite
0x00007FFBDEBEC0E9 (Unity) GfxDevice::UpdateBufferRanges
0x00007FFBE063A75F (Unity) GfxDeviceWorker::RunCommand
0x00007FFBE063E6BC (Unity) GfxDeviceWorker::RunExt
0x00007FFBE063E7EF (Unity) GfxDeviceWorker::RunGfxDeviceWorker
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
akinoreiki
Nov 11, 2025 14:54
I am also having this issue on AMD processor system using Unity 6000.2.10f1.