Search Issue Tracker
By Design
Votes
0
Found in
5.3.4f1
Issue ID
805506
Regression
No
Unity crashes/fails to render if drivers are updated while Unity is open
Steps to reproduce:
1. Create new project and set editor to DX9
2. Update NVidia drivers while editor is open
3. After drivers are updated notice that Unity editor doesn't render anything
4. Force-quit editor and open Editor.log
5. Notice that it's spammed with: HandleD3DDeviceLost: still lost
6. Rollback drivers
7. Re-open editor but this time in DX11
8. Update drivers again
9. Notice that editor crashes
10. Open Editor.log and notice few asserts printed before crash:
SUCCEEDED(hr)
(Filename: C:/buildslave/unity/build/Runtime/GfxDevice/d3d11/D3D11Window.cpp Line: 215)
SUCCEEDED(hr)
(Filename: C:/buildslave/unity/build/Runtime/GfxDevice/d3d11/D3D11Window.cpp Line: 215)
D3D11: Failed to create RenderTexture (1075 x 451 fmt 44 aa 1), error 0x887a000)
(Filename: C:/buildslave/unity/build/Runtime/GfxDevice/d3d11/RenderTextureD3D11.cpp Line: 308)
SUCCEEDED(hr)
(Filename: C:/buildslave/unity/build/Runtime/GfxDevice/d3d11/RenderTextureD3D11.cpp Line: 622)
SUCCEEDED(hr)
(Filename: C:/buildslave/unity/build/Runtime/GfxDevice/d3d11/RenderTextureD3D11.cpp Line: 636)
Reproduced with: 5.1.4f1, 5.2.4f1, 5.3.5p4, 5.4.0b22
Comments (2)
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
- Project Auditor suggests to update package to a lower version than installed when the recommended package version is not the latest version
- Low performance when multiple meshes using BlendShape are rendered on screen
- TMP Dropdown visually corrupts or disappears when its own GameObject is assigned to "Caption Image" or "Placeholder" elements
- Usymtool tries to upload GameAssembly.pdb when it doesn't exist after building with Mono backend
- “NullReferenceException” error thrown in the Console when running HDRP Wizard “Fix All” in URP project after installing HDRP Package
DonCorben
Apr 16, 2020 13:40
Ive got 2019.218f1 - same issue
aluzino1811
May 10, 2018 06:53
Same here