Search Issue Tracker
Won't Fix
Votes
29
Found in
6000.1.10f1
6000.2.2f1
6000.4.0a1
Issue ID
UUM-107390
Regression
No
Crash on D3D12SwapChain::Present when performing various Unity operations
A recurring crash issue in the Unity Editor has been observed, affecting various workflows. These crashes have been reported to happen when:
1. Opening a Unity project
2. Entering Play Mode
3. Changing the Editor layout
4. Adding a GameObject to the Scene
5. Adding Components
6. Using Package Manager
Reproducible with versions: 6000.1.0f1 - 6000.1.10f1, 6000.2.0b1 - 6000.2.2f1
Reproducible on: Windows 11 (reporter), Windows 10 (other reporters)
Note: Not reproduced by CQA
First few lines of the stack trace:
{noformat}
0x00007FF8699B5DA9 (amdxc64) OpenAdapter12
0x00007FF869BF44B5 (amdxc64) OpenAdapter12
0x00007FF8697B9487 (amdxc64) OpenShimInterface
0x00007FF8968454DE (D3D12Core) D3D12GetInterface
0x00007FF89684782F (D3D12Core) D3D12GetInterface{noformat}
{noformat}
0x00007FF88BB2786B (nvwgf2umx) NVAPI_Thunk
0x00007FF88BB27516 (nvwgf2umx) NVAPI_Thunk
0x00007FF88BCA597C (nvwgf2umx) NVAPI_Thunk
0x00007FF88B34F658 (nvwgf2umx) OpenAdapter12
0x00007FF88D903484 (D3D12Core) D3D12GetInterface{noformat}
Comments (7)
-
dest-69
Sep 16, 2025 09:27
For me, working on these versions is currently impossible since it keeps crashing. I’ve also disabled DirectX 12 using the `-force-d3d11` command. I’ll keep an eye on the fix, and once it’s resolved, I’ll switch back to DirectX 12.
-
sachelkas
Sep 11, 2025 17:57
Is this error present in version 6.3?
-
sachelkas
Aug 28, 2025 06:09
Please solve this problem
-
Code_TR
Aug 22, 2025 12:00
When i switched unity 6 from unity 2022, my game crashing almost everytime
I think it's related to the lights -
Codersama
Aug 22, 2025 08:06
August is almost over, and this issue isn't solved yet
-
unity_089B72345176775089C3
Jul 24, 2025 23:57
For me turning off / removing DX12 from the graphics resolve this issue for me, which.. turns off a lot of features. But in the meantime it caused this issue to go away.
-
Doni_gandoni
Jun 08, 2025 04:00
Is this issue resolved or will it be resolved in the next patch?
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
We have tried to keep an eye on this crash for a while. Unfortunately, this is a hardware configuration/driver problem because crash callstacks point to vendor-specific driver functions, like OpenAdapter12() in libraries, such as amdxc64.dll (AMD), nvwgf2umx.dll (NVIDIA), qcdx12arm64xum.dll (Qualcomm), etc. Since, as a result, our code in the engine can not even start any crash-analysis on DirectX 12, we can not debug or fix such problems on our side. The only recommendation we can give is to update the drivers and/or to perform full uninstallation (i.e., using "Display Driver Uninstaller" tool) followed by a clean installation of the driver.