Troubleshooting crashes of Live
- Live Versions: All
- Operating System: All
Live crashes during start-up (does not start)
A number of issues might prevent Live from starting. Please read this dedicated article to find out more.
Since Live 9.2 brings improvements to the plug-ins framework, certain out-dated plug-ins may cause Live to crash at launch. Please see this article for a full explanation.
If you are using iLok plugins on Windows 8.1 or Windows 10 and experiencing crashes, it may be caused by an issue connected to the PACE software.
Out of memory issues
The 32-bit version of Live, like every 32-bit application, can address up to 2GB on a 32-bit operating system and up to 4GB memory on a 64-bit operating system. It will crash when it requires more than those 2GB or 4GB respectively. Find out how to deal with RAM limitations and avoid Out of Memory crashes with the 32-bit version of Live.
In order to recover your set and to prevent these out of memory crashes please read this article about RAM limitations.
Another way to remedy out of memory crashes is to use the 64-bit version of Live which can use a theoretical maximum of 16 exabytes of RAM. Please refer to this guide to find out more about the benefits and limitations of using Live 64-bit.
Live crashes while using it
Make sure Live is up to date. Under Preferences → Licenses Maintenance, verify that "Get Software Updates" is active.
You can also manually download the latest version by either clicking on Help → Check for Updates in Live or by accessing your Ableton User Account.
Make sure that the following third-party software and drivers are up to date:
- Operating System
- Audio interface drivers
- MIDI controller drivers
- Graphics driver
Max for Live
Requesting further support
When restarting Live after a crash, Live automatically displays a Crash Lesson with a link to a Crash Report. Please send this Crash Report to email@example.com to help improving Live's stability. If you need feedback or further help, please send the Crash Report as an attachment to our Technical Support. Feel free to include in your email further details about how the crash happened or which operation seemed to have prompted the crash.