Editor Crash - Createdirect3d11surfacefromdxgisurface

Hi everyone,

I’ve been running into an issue fairly consistently: In one of my scenes the editor crashes as soon as I start orbiting (alt + left click) the camera.
Zooming in/out does not seem to cause a crash, neither does changing the FOV.

EDIT: It turns out the crash only happens when the scene view is focused.

This happens in 2018.2, 2018.3 and 2019.1b10.

I tried submitting a bug report, but the error reporting from crashed saying it failed to read a file.
I’m happy to provide dmp files and anything else to someone at Unity.

Thanks!

Error log:

Unity Editor by Unity Technologies [version: Unity 2019.1.0b10_dbf1e96a8b63]

d3d11.dll caused an Access Violation (0xc0000005)
  in module d3d11.dll at 0033:aa274240.

Error occurred at 2019-04-12_110800.
C:\Program Files\Unity\Hub\Editor\2019.1.0b10\Editor\Unity.exe, run by dario.

74% physical memory in use.
16276 MB physical memory [4086 MB free].
6460 MB process peak paging file [4115 MB used].
4783 MB process peak working set [1095 MB used].
System Commit Total/Limit/Peak: 19497MB/22263MB/20877MB
System Physical Total/Available: 16276MB/4086MB
System Process Count: 278
System Thread Count: 3625
System Handle Count: 123249
Disk space data for 'C:\Users\dario\AppData\Local\Temp\Unity\Editor\Crashes\Crash_2019-04-12_150754912\': 24594718720 bytes free of 242334482432 total.

Write to location 00000000000000E0 caused an access violation.

Context:
RDI:    0x00000117eaff6750  RSI: 0x0000000000000001  RAX:   0x00000117fbb80190
RBX:    0x00000117f039f6c0  RCX: 0x00000117fbb80188  RDX:   0x0000000000000000
RIP:    0x00007ffbaa274240  RBP: 0x0000000000000000  SegCs: 0x0000000000000033
EFlags: 0x0000000000010206  RSP: 0x0000000c3f0fd7c8  SegSs: 0x000000000000002b
R8:     0x0000000000000001  R9:  0x0000000000000000  R10:   0x0000000c3f0fb4f0
R11:    0x0000000c3f0fd750  R12: 0x0000000000000001  R13:   0x00007ff7b7d7feb0
R14:    0x0000000000000000  R15: 0x00000117ed189740


Bytes at CS:EIP:
66 83 a2 e0 00 00 00 00 48 8b c1 48 81 c2 e8 00

Mono DLL loaded successfully at 'C:\Program Files\Unity\Hub\Editor\2019.1.0b10\Editor\Data\MonoBleedingEdge\EmbedRuntime\mono-2.0-bdwgc.dll'.


Stack Trace of Crashed Thread 13488:
0x00007FFBAA274240 (d3d11) CreateDirect3D11SurfaceFromDXGISurface
0x00007FF7B2966A76 (Unity) PAL_Memory_Free
0x00007FF7B2971A69 (Unity) PAL_Memory_Free
0x00007FF7B29F64EF (Unity) PAL_Memory_Free
0x00007FF7B29F8C3B (Unity) PAL_Memory_Free
0x00007FF7B29F9005 (Unity) PAL_Memory_Free
0x00007FF7B35A5857 (Unity) PAL_Memory_Free
0x00007FFBAEB07974 (KERNEL32) BaseThreadInitThunk
0x00007FFBB0ECA271 (ntdll) RtlUserThreadStart

Stacks for Running Threads:

Does it also fail if you just open this project in the editor and click “Help > Report a bug…”?

Alternatively, you could submit a bug-report with all the required information, but without the project itself, and ask Unity QA to provide a safe owncloud location, where you can upload your project (as .zip archive for example) afterwards.

If either of these options work for you, then please submit a bug-report as described in this document:

It’s important that you report these issues together with a reproduction project if you want them to get fixed. If you don’t do it, it might be a long time until someone else reports them or until Unity Technologies find them.

After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. You can post the Case number (number only, not the link) in this forum thread for Unity staff to pick up, in case they see it.

After upgrading to 2019.1.0f1 I managed to submit a bug report: Case 1146327

1 Like

Do you call Shader.WarmupAllShaders()? In my case this was the problem and traces showed the same API failure: CreateDirect3D11SurfaceFromDXGISurface in D3D11.DLL.