Your DAW freezes or quits the moment a plugin loads, or when you open a certain project, and it takes the whole program down with it. It looks alarming, but it is almost always one bad or incompatible plugin rather than a fault in your machine or your DAW. There is a sensible order to find the plugin and fix it, the same for any host on Mac or Windows.
This is host-agnostic. The steps are the same in every DAW or video editor; only the menu names differ, so check the wording in your own preferences and plugin manager as you go.
Because one plugin hit something it could not handle and pulled the host down with it. A DAW loads plugins inside its own program, so a single plugin that fails badly can freeze or quit the entire application even though the rest of your system is fine. That is the good news: you are usually looking for one bad or incompatible plugin, not a broken computer.
The reason it feels random is that nothing on screen names the culprit at the moment it happens. But a crashing plugin almost always fails at a predictable point, and that point tells you a lot. It usually crashes on load, on a preset, or on a specific project, so the first useful thing you can do is note exactly when it happens.
Note exactly when the crash happens, because the timing points almost straight at the plugin. A crash on startup, a crash when you pick a certain sound, and a crash that only ever hits one project are three different stories, and each one narrows the search on its own.
Two things turn that guess into a name. Read the DAW crash log: when a host quits, it usually writes a report that names the plugin or its file near the top, and that alone often ends the search. And load the DAW in safe mode, or with plugins disabled, then bring them back a few at a time until it crashes again; the group that brings it down contains your plugin.
The table below maps the common way each one shows up to a likely cause and a fix.
| Symptom | Likely cause | Fix |
|---|---|---|
| DAW freezes or quits as it starts | A plugin fails while the host scans or loads it at launch | Start in safe mode or with plugins disabled, then rescan and remove the one that fails |
| Crash the moment you load one plugin or preset | That plugin or preset is incompatible or corrupt | Update the plugin, or delete its preference and preset cache, then reinstall it |
| Only one project crashes, others are fine | A plugin, or a corrupt plugin state, saved in that project | Open a different project to confirm, then remove or replace that plugin in the session |
| Freezes or crashes under heavy load | The CPU or RAM ran out of headroom | Raise the buffer size, freeze or bounce heavy tracks, and close other apps |
| The plugin disappears from the list after a crash | The host blocklisted it when it failed validation | Rescan or clear the blocklist, then update or reinstall the plugin |
| It plays but the audio breaks up rather than crashing | Dropouts under load, not a true crash | See why does my audio crackle and pop |
Once you know which plugin it is, work down a short list of fixes and stop the moment the DAW stays up. They run from the most common and the least disruptive to the last resort, and none of them require touching the rest of your system.
If it turns out to be one plugin and none of this settles it, contact that plugin's maker with your DAW and operating system version, and tell them exactly when it crashes. That combination is what they need to reproduce it, and a crash that is specific to one plugin is theirs to fix. If instead the plugin then vanishes from the list altogether, that is a separate problem covered in why a plugin does not show up in your DAW.
Keep your plugins and your DAW on versions that are known to work together, and save often so a crash costs you seconds rather than a session. Most repeat crashes come from a version drifting out of step or from a single unstable plugin that never got replaced.
Most of this page is about one misbehaving plugin rather than a fault in your DAW. While you track it down, it helps to have a plugin you know is stable, so you can keep making sound instead of restarting the host.
Every Tunary instrument has a browser demo that installs nothing and needs no account, so you can keep working and hear a plugin play while you sort out a misbehaving one in your own DAW. The Collection is three of them: ARGISH, SILT and REHEAT.
The installed versions are built to pass a host's validation cleanly: AU, VST3, AAX and a standalone app on macOS, signed and notarized, and a VST3 on Windows. So they load and validate on the first launch, rather than adding to the trouble on this page.
Try one free in your browser first, no install and no account. The whole Collection is one purchase.
We write these when there is something worth writing down. One email when a new one lands or a new Tunary instrument ships. No newsletter, no schedule.
Tunary