Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Join us on Dec 8, 2022, between 7 am & 7 pm EST, in the DOTS Dev Blitz Day 2022 - Q&A forum, Discord, and Unity3D Subreddit to learn more about DOTS directly from the Unity Developers.
    Dismiss Notice
  3. Have a look at our Games Focus blog post series which will show what Unity is doing for all game developers – now, next year, and in the future.
    Dismiss Notice

Bug Windows: Native Crash in igd10iumd64 affecting Intel Integrated GPU users

Discussion in 'Visual Effect Graph' started by Doodums, Aug 31, 2022.

  1. Doodums

    Doodums

    Joined:
    Feb 19, 2011
    Posts:
    21
    Hi,

    I'm getting a large volume of "Native Crash - KiUserExceptionDispatcher" reports. I've included a subset of them in the link below as well as what GPU the user was using. In all the logs, the crashes appear within the igd10iumd64.dll, but I'm unable to see what the error message is and I'm not sure where to find the pdb to upload to Unity Analytics to enable those logs.

    https://imgur.com/a/IyIS74Z

    I'm using 2021.3.8f1. The issue was occurring on 2020.3.12f1 and 2020.3.38f1.
    The project uses URP with almost all Shaders written with Shader Graph, and 98% of VFX done through VFX graph, with about 3 bullet projectiles using Shuriken. Our game is a Tower Defence, and the crashes seem to consistently appear in the later waves where the players have more on screen. I've not seen any pattern yet with any specific unit or spell triggering the crash. Quite a lot of our VFX use the Particle Strip node which has caused me to believe this might be our issue:
    https://issuetracker.unity3d.com/is...x-that-has-a-particle-strip-node-to-the-scene

    The link above and from what I can see within those linked stack traces make me believe this is within VFX Graph. If it's not, let me know what area is causing the crash and I will post in those forums instead. Any advice as to how I can further track this down would be appreciated. I don't have access to the hardware and I'm unable to replicate the problem on my side.