Search Issue Tracker

Won't Fix

Votes

9

Found in

2018.3.0a1

2018.3.5f1

2019.1.0a1

2019.2.0a1

2019.3.0a1

Issue ID

1127974

Regression

No

Editor crashes with GfxDeviceD3D11Base::CopyRenderSurfaceDesc after changing Editor layout using laptop GeForce Battery Boost

Graphics - LowLevel

-

How to reproduce:
1. Open new Unity project
2. Unplug the laptop from charging
3. Turn on Battery Boost on GeForce Experience
4. Change Editor layouts several times and move any window afterward
5. After one tab turns completely white, change the layout a few more times
-----------------------------
Observe the crash

Reproduced with: 2018.3.6f1, 2019.1.0b4, 2019.2.2f1, 2019.3.0a12

Notes:
1) IMPORTANT! The laptop must be unplugged and GeForce Experience Battery Boost must be turned on.
2) Lately, there have been users stating that the issue reproduces even when the laptop is plugged in and GeForce Experience Battery Boost is disabled

Errors:
Assertion failed on expression: 'SUCCEEDED(hr)'
d3d11: swap chain: w=1143 h=542 fmt=28
d3d11: failed to create swap chain [0x887a0005]
D3D11: Failed to create RenderTexture (910 x 397 fmt 27 aa 1), error 0x887a0005
D3D11: Failed to create render texture primary DSV (error 0x80070057)

  1. Resolution Note:

    This issue is caused because of Timeout Detection Recovery (TDR). This is a way for the Windows display manager to recover from bad situations or potentially hung GPUs, however it can be very aggressive and we as programmers or content producers have to be careful not to throw too much work on the GPU in the same "batch" unless it triggers.

    The principle is this: if you submit work for a frame (or more correctly a piece of a frame) that takes more than a certain amount of time TDR kicks in and restarts the driver. It's nothing we at Unity can do much about sadly. However we have already added a new message dialogue for this in upcoming versions so you should get more information.

    What you, as a user, can do is to either reduce workload (less vertices, fewer objects, simpler shaders), ensure the GPU can run at full speed (have laptop plugged in and cooled) or you can potentially increase the timeout as described on this Microsoft page:
    https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys

    NVIDIA also has some tools in the Control Panel to play around this limitation.

Comments (21)

  1. paulex

    Jun 30, 2019 14:13

    COLINDARKWIND your solution worked for me, thank you very much!!

  2. StefanJanssen

    Jun 06, 2019 19:44

    I'm on desktop and according to the crash report this issue is the same as mine. I was on 2019.3.0a3. According to this bugreport this issue should have been fixed in that release so something is still broken.

  3. SLGSimon

    May 15, 2019 16:24

    I got this in 2019.1.2f1 when updating my graphics drivers on desktop

  4. RickyHoughton

    May 08, 2019 18:59

    I have problem that more closely resembled CARLOSEJT. I am not on battery, I am plugged in.

    One solution I am using now is that I switch from game view to 'asset store' view and then resize the 'asset store' window, then come back to 'game' window. This does not cause it to crash.

    I have confirmed that my NVIDIA CPU is configured to be used by laptop, not the built-in GPU from Intel.

    Ricky

  5. gaspard_leon

    Apr 14, 2019 07:05

    I just got this on my laptop, which does not contain a dedicated GPU, it only has an Intel on-chip GPU: Intel i5-4200U with Intel HD 4400
    Note I was on battery however

  6. captain_blah

    Mar 21, 2019 12:58

    I received this error on 2018.3.8f1.
    My hardware: AMD Radeon Vega64, AMD Ryzen 7 1700X CPU (Desktop)

    Steps to reproduce:

    - Enter play mode
    - Drag console tab
    - Press'Esc' while still dragging

  7. Umresh

    Mar 13, 2019 06:11

    Same issue is on unity 2018.3.6f1,2018.3.7f1,2018.3.8f1.

  8. ColinDarkwind

    Mar 08, 2019 03:54

    Erm, and now I see that you have battery boost on. Ignore my comment! Turning it off is the only way I've gotten it to work.

  9. ColinDarkwind

    Mar 08, 2019 03:53

    I had the same problem on my new Razer laptop and it was killing me. I just came across the solution, at least for me.

    GeForce experience added a "Battery Boost" that, when I disabled it, fixed my problem.

    To solve:
    - Open GeForce Experience
    - Click the settings icon (gear) in the upper right
    - On the left bar, switch from "General" to "Games"
    - On the right, there is a box that says "Battery Boost"
    - Disable this by hitting the little toggle switch

    It fixed my problem. I'd love to hear if it fixes yours too.

  10. carlosejt

    Feb 23, 2019 19:52

    I update the drivers, and set the NVidia processor as the preferred in Nvidia Control Panel, and follow the same

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.