How-to: Troubleshoot Crashes
This troubleshooter guide has some tips to try and solve crashing problems when using Serato Software
The first step is to ensure you're running the most recent version of your Serato Software. To check what the most recent version is, go to the downloads page:
Detecting and removing corrupt files
The most common cause of a crash is having a corrupt file in your music library. You will need to make sure you have all your files analyzed and remove any files marked as corrupt.
To remove corrupt files:
- Disconnect the Serato supported device (Rane Mixer/Soundcard or DJ Controller).
- Click on the 'analyze files' button to analyze your whole library (This can take some time with a large library).
- Click on your ALL crate
- Click on the first empty box of your library's column header to group files by type.
- Delete all files marked with the 'corrupt' icon by using CTRL + SHIFT + DELETE (This will send those files directly to the trash/recycle bin):
NOTE: Make sure you don't re-import these corrupt tracks into your Serato Software music library. It is wise to delete these files from your hard drive. If you want these tracks, you can either re-download, re-rip, or re-encode these tracks and then import these new versions (check these for corruption too).
A useful thing to do if you're getting crashes and can't find a solution is to send Serato a crash log if possible.
NOTE: A crash is when the program shuts itself down, and NOT when the program freezes or when you have to force quit the application.
Crash logs can be found here:
- Under Windows XP you need to have Dr Watson enabled to log crash dumps. Read the guide to do that here.
- For Windows Vista and Windows 7, read the guide here.
- Under Mac OS X, read the guide here.
Attach any logs to your Help Request if you have one, or start a new Help Request:
- Create a Scratch Live Help Request
- Create an ITCH Help Request
- Create a Serato DJ Intro Help Request
- Create a Serato DJ Help Request
Your log will help Serato make the software as resistant to crashing as possible.
Renaming the database V2 file
Another possibility is your database file is corrupt. To test that, try renaming it as follows.
To rebuild your Database V2 file, follow the instructions in this article: here.
If this works, it would be helpful to attach your corrupt database file to your help thread for Serato for analysis.
If you've tried the processes in this guide and still experience crashing, we want to help. Create a Help Request so that the Support teams from Serato and your hardware manufacturer can help.