# IplugEffect crashed DAW after open plugin **URL:** \ **Category:** Windows\ **Created:** [18 June 2021 19:53 UTC](https://iplug2.discourse.group/t/iplugeffect-crashed-daw-after-open-plugin/417 "2021-06-18T19:53:46Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![SKyZz](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@SKyZz](https://iplug2.discourse.group/u/SKyZz)\ **Post date:** [18 June 2021 19:53 UTC](https://iplug2.discourse.group/t/iplugeffect-crashed-daw-after-open-plugin/417/1 "2021-06-18T19:53:46Z")
We have the same code: IplugEffect (from examples) We have 2 instances (VM): A: **Windows 10 1809 x64 Build** (Instelled VS19 + tools) B: **Windows 10 1809 x64 Test (Clean + Reaper)** We are building IplugEffect on **Windows 10 1809 x64 Build** and scanning/validation… look good after we send the artifact to **Windows 10 1809 x64 Test (Clean + Reaper)** and scanning & validation - ok but we are getting exit from DAW after we add to FX channel IplugEffect plugin How to resolve this problem? Maybe add to any libs to the installer? Thanks ---
**Author:** ![olilarkin](https://yyz2.discourse-cdn.com/free1/user_avatar/iplug2.discourse.group/olilarkin/32/2_2.png) [@olilarkin](https://iplug2.discourse.group/u/olilarkin)\ **Post date:** [18 June 2021 20:09 UTC](https://iplug2.discourse.group/t/iplugeffect-crashed-daw-after-open-plugin/417/2 "2021-06-18T20:09:44Z")
You need to debug it and see where it crashes ---
**Author:** ![SKyZz](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@SKyZz](https://iplug2.discourse.group/u/SKyZz)\ **Post date:** [18 June 2021 21:52 UTC](https://iplug2.discourse.group/t/iplugeffect-crashed-daw-after-open-plugin/417/3 "2021-06-18T21:52:58Z")
If this was when building on a machine for builds, it’s easy, but on a clean machine, I/you need to think about it, is there an example of displaying a message through the VST to check the strings? ---
**Author:** ![olilarkin](https://yyz2.discourse-cdn.com/free1/user_avatar/iplug2.discourse.group/olilarkin/32/2_2.png) [@olilarkin](https://iplug2.discourse.group/u/olilarkin)\ **Post date:** [18 June 2021 22:42 UTC](https://iplug2.discourse.group/t/iplugeffect-crashed-daw-after-open-plugin/417/4 "2021-06-18T22:42:14Z")
Since you’re using virtual machines it’s possible that the crash is due to OpenGL drivers. Perhaps you could try building using skia cpu mode, And see if the same thing happens. Here is a good article about debugging release build crashes with pdb files > **[Visual Studio Crash Dumps — A Guide For Plugin Developers](https://www.cantabilesoftware.com/blog/visual-studio-crash-dumps---a-guide-for-plugin-developers-5b2a666d94e2/amp/)** > > For any software used in live performance, rock solid stability is the number one priority. This has always been, and always will be the… Please make a pull request if you find/fix a problem Thanks ---
**Author:** ![olilarkin](https://yyz2.discourse-cdn.com/free1/user_avatar/iplug2.discourse.group/olilarkin/32/2_2.png) [@olilarkin](https://iplug2.discourse.group/u/olilarkin)\ **Post date:** [18 June 2021 23:08 UTC](https://iplug2.discourse.group/t/iplugeffect-crashed-daw-after-open-plugin/417/5 "2021-06-18T23:08:27Z")
The fact you mention that VS2019 is not installed makes me think it might be a /MT /MD issue, but the iPlug2 default /MT means it should work on machines without the MSVC runtime installed ---
**Author:** ![SKyZz](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@SKyZz](https://iplug2.discourse.group/u/SKyZz)\ **Post date:** [19 June 2021 10:36 UTC](https://iplug2.discourse.group/t/iplugeffect-crashed-daw-after-open-plugin/417/6 "2021-06-19T10:36:30Z")
We also installed VS on test clear machine and got the same. I think it’s problem with graphics on VM. We will test this too and notify ASAP