# Experiencing crash to Desktop from resonanceaudio.dll in FMOD 1.10.20 Unity 2019.2.21f1 **URL:** \ **Category:** Unity\ **Created:** [April 3, 2020, 2:20pm UTC](https://qa.fmod.com/t/experiencing-crash-to-desktop-from-resonanceaudio-dll-in-fmod-1-10-20-unity-2019-2-21f1/15610 "2020-04-03T14:20:18Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![max.danielsson](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/max.danielsson/32/1065_2.png) [@max.danielsson](https://qa.fmod.com/u/max.danielsson)\ **Post date:** [April 3, 2020, 2:20pm UTC](https://qa.fmod.com/t/experiencing-crash-to-desktop-from-resonanceaudio-dll-in-fmod-1-10-20-unity-2019-2-21f1/15610/1 "2020-04-03T14:20:18Z")
Hi! We’re experiencing quite frequent runtime crashes in both debug and development builds of our Unity project. Most, if not all crashes are immediate and appear to come from resonanceaudio.dll when running the application through the visual studio debugger. `Unhandled exception at 0x00007FF8F2C53701 (resonanceaudio.dll) in ******** _crash.dmp: Fatal program exit requested. occurred` ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/2/2fc47e24f7269728f19563c4d153bcb168323580.png) We’re running FMOD 1.10.20 and Unity 2019.2.21f1. Anyone ever experienced anything similar? The crashes and log files do not give us any useful hints so far, and we don’t have any clear steps of reproduction in our game. The crashes appear quite random with no action in particular causing a crash. On some older CPU’s it appears like it never or very rarely happens, but is quite frequent on newer machines, both Intel, AMD, Nvidia and Radeon systems. Crashes so far have been detected on both Windows 8 and Windows 10. Is it possible to get access to a version of the resonanceaudio.dll file with debug symbols, or alternatively the exact source used by the FMOD project so we can compile one ourselves and be able to do some deeper debugging? We’ve attempted to run the newer FMOD 2.0 build, but it does not seem to have any impact on the crash rate. We make quite frequent use of resonance audio features in our game, the runtime was stable when we were just using FMOD without resonance audio, but some time after we started using resonance audio features in our FMOD studio project these problems appeared. Thankful for any input on the topic. ---
**Author:** ![brett](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/brett/32/261_2.png) [@brett](https://qa.fmod.com/u/brett)\ **Post date:** [April 4, 2020, 6:54am UTC](https://qa.fmod.com/t/experiencing-crash-to-desktop-from-resonanceaudio-dll-in-fmod-1-10-20-unity-2019-2-21f1/15610/2 "2020-04-04T06:54:15Z")
The best thing I can suggest is to check your input to the plugin. This will be the listener and the event positions, velocities, and direction vectors to fmod (adn which methods in unity do you use to do this). As this doesnt normally happen, but you’re getting it a lot , i’d maybe even try and isolate things to the point the crash doesnt happen any more. Ie stop passing data to the functions one parameter at a time, even if it sounds wrong, just to get the issue to stop. If it is not parameters, even turning off events in case there is a particular combination of the resonance plugin and other effects or sounds that cause this to happen. The best thing for us is a reproduction but I can understand this is more work. We can of course provide debugging libraries to help us track down the issue. regards Brett ---
**Author:** ![max.danielsson](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/max.danielsson/32/1065_2.png) [@max.danielsson](https://qa.fmod.com/u/max.danielsson)\ **Post date:** [April 5, 2020, 6:46pm UTC](https://qa.fmod.com/t/experiencing-crash-to-desktop-from-resonanceaudio-dll-in-fmod-1-10-20-unity-2019-2-21f1/15610/3 "2020-04-05T18:46:20Z")
Thanks! It’s the path we’re currently taking, trying to guess what might be causing it and reducing the possibilities. If you could, getting us a .dll with debug symbols would be really useful. ---
**Author:** ![killerloader](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@killerloader](https://qa.fmod.com/u/killerloader)\ **Post date:** [April 30, 2020, 12:03am UTC](https://qa.fmod.com/t/experiencing-crash-to-desktop-from-resonanceaudio-dll-in-fmod-1-10-20-unity-2019-2-21f1/15610/4 "2020-04-30T00:03:27Z")
Any update on this issue? We’re experiencing a similar problem with our project. The crash to desktop is relatively difficult to reproduce for us so a trial and error approach will only be our last resort. We’re also using VR (VRTK with SteamVR), and I’ve seen at least one other article with this issue being reported while using VRTK. ---
**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\ **Post date:** [May 7, 2020, 4:23am UTC](https://qa.fmod.com/t/experiencing-crash-to-desktop-from-resonanceaudio-dll-in-fmod-1-10-20-unity-2019-2-21f1/15610/5 "2020-05-07T04:23:40Z")
What versions of FMOD, Unity and Steam are you using? Are you able to share any logs you might have? ---
**Author:** ![killerloader](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@killerloader](https://qa.fmod.com/u/killerloader)\ **Post date:** [May 7, 2020, 6:52am UTC](https://qa.fmod.com/t/experiencing-crash-to-desktop-from-resonanceaudio-dll-in-fmod-1-10-20-unity-2019-2-21f1/15610/6 "2020-05-07T06:52:57Z")
Thanks for the response, my issue was resolved in another thread, the solution is in a PR on the resonanace audio github project. > [@FMOD Unity integration crash with ResonanceAudio](https://qa.fmod.com/t/fmod-unity-integration-crash-with-resonanceaudio/15710): > > Hi, me and my team are experiencing a crash in our game (in editor, and in our release builds) Unity crashes to desktop without any error message or log, however windows event viewer shows this: Faulting application name: Unity.exe, version: 2018.3.12.64867, time stamp: 0x5ca7b142 Faulting module name: resonanceaudio.dll, version: 0.0.0.0, time stamp: 0x5be28099 Exception code: 0xc0000409 Fault offset: 0x00000000000638b1 Faulting process id: 0x19d0 Faulting application start time: 0x01d61ed45f…