Search Issue Tracker

Active

Under Consideration for 6000.1.X, 6000.2.X, 6000.3.X

Votes

19

Found in

6000.1.1f1

Issue ID

UUM-104826

Regression

No

Crash on GfxDeviceD3D12Base::DrawBuffersCommon 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. Creating a new Unity project
2. Opening an existing Unity project
3. Entering Play Mode
4. Using Package Manager
5. Working with Materials or Textures
6. Using the Inspector window
7. Baking lights
8. Compiling scripts
9. Idling in the Editor for a longer period
10. Browsing assets via the Project window

Reliable *repro case* is attached in a related bug: [https://jira.unity3d.com/browse/UUM-108405]. Because the list above doesn't provide explicit repro steps, please use the repro case in that project.

Reproducible with versions: 6000.1.0f1 - 6000.1.9f1, 6000.2.0b1 - 6000.2.0b8

Reproducible on: Windows 11 (reporter), Windows 10 (other reporters)

Notes:
* Not reproduced by CQA
* Forcing Unity Editor to launch with the -force-d3d11 command line argument fixes the crash

First few lines of the stack trace:
{noformat}
0x00007FFE0EF674BF (Unity) GfxDeviceD3D12Base::DrawBuffersCommon
0x00007FFE0EF66FCC (Unity) GfxDeviceD3D12Base::DrawBufferRanges
0x00007FFE0EF672A9 (Unity) GfxDeviceD3D12Base::DrawBuffers
0x00007FFE106FAF3D (Unity) GfxDeviceWorker::RunCommand
0x00007FFE106FE6BC (Unity) GfxDeviceWorker::RunExt{noformat}

Comments (14)

  1. mario-antunez-sapristi

    Jul 24, 2025 09:57

    Continues whith crashes constantly (6000.1.12f1).

  2. AceOfRubies

    Jul 17, 2025 14:21

    Browsing assets via the Project window seems to be primary issue for me. I'm using the latest Nvidia drivers, I've changed DirectX version to 11 in the settings, I've used the command line, and none of these have worked. Every time I try to browse assets, it crashes constantly.

  3. Chemnitzer

    Jul 10, 2025 21:34

    I have the same issue (already sent several bug reports). Since someone mentioned that the GPU driver could be the reason: I had the crashes with an one year old nvidia driver, then the same crashes with the latest one. So it doesn't matter. My system: Win 11 24H2, Intel i5-8600k, GTX 1070 Ti (but I guess, this is known by the log files 😄).

    But the command line argument workaround works well for me. Thank you.

    If someone else is wondering how to add command line arguments:
    1. Open Unity Hub.
    2. Click on the 3-dot-button right next of your desired project.
    3. Select "Add command line arguments"
    4. Paste them ( -force-d3d11 ) in and Save.
    5. Then when opened your project, check in the title bar that it is saying "<DX11>" at the end.

  4. AniAko

    Jul 09, 2025 12:38

    Still having this issue. It's almost completely random. Sometimes at certain points in my project it fails, sometimes it trucks on. But when it crashes, it CRASHES the Unity editor with no recourse to continue. Not even the bug-report shows up. It's insane that I have had to launch Unity at least 2 dozen times a day wasting countless hours for a problem that hasn't been fixed in the last 5 versions.

  5. hello_unity160

    Jul 07, 2025 18:57

    I switched from using DX12 to DX11 and this seems to have resolved the issue.

  6. Bohacik

    Jun 30, 2025 15:40

    I had that problem today because I updated the GPU driver yesterday, and that turned out to be the issue. I downgraded it to an earlier version, and now everything is working, at least for now.

  7. bsivko

    Jun 10, 2025 05:04

    I have several crashes per day in Unity Editor which goes to this issue after report. Should I continue to send these reports?

  8. Mucch

    May 22, 2025 02:41

    It was mentioned as a known issue in the release notes for 6000.1.4f1, so we'll just have to wait for a fix. I had a crash during the tutorial, but when I used 6000.0.49f1 it worked fine on Windows 10.

  9. yznikfortyni

    May 20, 2025 18:03

    Not on windows 11, on windows 10 I also have this problem

  10. Snigros

    May 20, 2025 11:28

    Editor still crashing with 6000.1.3f1....

    A sort of workaround (at least to make the editor a bit more stable) seems to be to set the Graphics API for Windows to DX11 then DX12 (which is presumably what the editor also uses) while having the UWP Graphics API set to DX12 and then DX11 (so DX12 is still used in the UWP build)...

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.