Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.11f1
Issue ID
UUM-55368
Regression
No
[DX11] VFX ShaderGraph on D3D11 causes NVIDIA driver crash
Steps to reproduce:
1. Open the attached user's project "ProjectGPUCrash.zip"
2. Perform a standalone Windows development build and leave it running
3. Open "Assets/Scenes/SampleScene.unity" and enter Play Mode
4. Wait for the crash to occur and make sure the Player and/or the Editor is not focused
Expected results: Editor and or the Player does not crash
Actual results: Editor and or the Player crashes
Reproducible according to the customer: 2022.3.11f1
Could not test with 2021.3.32f1, 2022.3.11f1, 2023.1.17f1, 2023.2.0b17, 2023.3.0a13 due to local reproduction being unsuccessful
Reproducible according to the customer: Windows
Not reproducible on: Windows 10, Windows 11
Notes:
- As noted by the Customer, the crash only occurs on D3D11 with Nvidia GPU's, D3D12 and Vulkan with AMD GPU's do not reproduce the crash.
- The crash may not happen immediately and may not always occur
- The crash might sometimes occur when you are alt-tabbed to another window
- Take note of the warning in the console: "Shader warning in '[meshTrails] [Trail Bodies] Initialize Particle Strip': use of a potentially uninitialized variable (GetParticleIndex) at kernel CSMain at meshTrails.vfx(191) (on d3d11)"
- This warning is important as NVIDIA Nsight Aftermath identifies this shader (via shader hash) as the cause of the crash
- Screenshots from NVIDIA Nsight are attached ("01_nvidia_insight_crash.png" and "02_nvidia_insight_hash.png")
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.