Microsoft Visual C++ Runsime Library

Program:C:\program files\serato\scratchlive\scratchlive.exe

this application has requested the runtime to terminate it in an unusual way.
Please contact the spplication's support team for more information.

************URGENT*************
Please help I have a gig tonight

Computer is Dell Latitude D 620 Genuine Intel(R) cpu t 2300 @1.66ghz, 2.99gb of ram

Do you have another computer to try?

Are you using an external HD?

Does the whoole computer go unresponsive or is it only Scratch Live?

I don't have another computer. I am playing with a WD 500g external. For the most part its just serato that goes unresponsive. Sometimes when I try to load a track serato just disappears then I have to load the program again. I talked with Rafael he suggested that I try to elimanate recent files on the external to see if this is the problem. I have done that and the problem does go away however I can't pinpoint the exact files that are causing the problem. Second I am getting a "out of memory" box from time to time. This box doesn't allow me to close serato normally.

Hi djnickels,

Have you analyzed all your files? If so, look for all the files with a corrupt file icon and delete them from your library.


You may need to increase the amount of virtual memory you have set. Please take a look at this article and see if if helps -> www.delete-computer-history.com (click link).

Hi, I recently made some changes to a setup and found myself with the out of memory error. This was preceded by a total crash of the software after loading all files and playlists. One had only to click on the interface and there was a staccato sound and the serato interface was gone.

I went back to 1.8.2 from 1.9.1 but this didn't work. So I started working backwards from latest personal software updates/installs that I knew I shouldn't have done since it would change things on a PERFECTLY working system:

I had tried mytunesync. I removed that.
In order to get mytunesync to work I had to install Java 6 and Bonjour by Apple. I removed all Java... 6 and the 5.1 update. I removed Bonjour.
Just for giggles I think I installed spybot. I removed it.
After each removal I tried a fresh uninstall and reinstall of Serato 1.9.1.

After a restart, Serato would get to my World playlist and it kept hanging there. So I had iTunes rebuild the ID3 tags in 2.3. It swung past World but hung in the last playlist called Special World. I discovered and updated to 2.0 hoping that it might not have the same issue. It did. Although I must say it was quite pretty and came all the way up to completely loaded before it crashed. It crashed like 1.8.2... funny sound and disappear.

I rebuilt all ID3 tags and tried again. It crashed but this time it wrote to the external and created the backups.

I got up in the morning and uninstalled Serato 2.0 and reinstalled 1.8.2. SUCCESS!! Tonight I'll go back and try the 2.0 install... it looked too good to pass up!

So... I believe the key is definitely a corrupt file or two. I think mytunesync may have tried to write to or change a file... and this may be causing Serato problems.

I am running a Toshiba Satellite 1.73 ghz with 2gb memory and a Terabyte external.

Hope this helps someone else!!!

Hey DJ_Milestone,

Thanks for the information :) Corrupt files are always dangerous as they can cause all sorts of problems that you may not think are related to them. I'm glad you managed to get your issue resolved, enjoy 2.0 :)

Hey Michael,

You're welcome. I discovered that whatever was going on was not going away on the PC. Serato 1.9.1 and 2.0 were still having the out of memory issues even though 1.8.2 loaded properly. I saved the itunes library files to the external and proceeded to wipe and reinstall (just to be certain that it's nothing installed). I will be able to test starting with 1.9.1 tonight. I may even go for gumption with 2.0 from the start (couldn't hurt).

Of course, the reason all of this came to be was because of mytunesync. I am convinced of it now as, the two libraries I wanted to sync were on a mac and a pc. While I was wiping the PC, I put my G4 powerbook into play with the Serato. Serato couldn't find a single song in the itunes library until I set the ID3 tags again. Unlike the PC however, the Mac version was completely back up and running after this was done (it took a LONG time to get started but the library is large and that is understandable). it is flawless however.... I will put it through more paces this evening to be certain.

So... for those that might consider it... for now... mytunesync and Serato are NOT compatible. As it is I highly recommend having the lightest load possible on the computer to avoid conflicts.

Hey Michael,

Well... I spoke far to soon. Whatever changes had been made, have been unmade and I still experience the crashing under 1.9.1 and 2.0. It's rather odd. I wiped and reinstalled the PC. I wiped and recopied the files from the original drive. Perhaps there is a memory issue with 1.9.x forward? Because 1.8.2 loads completely and plays very well.
Anyway... embarrassed that I have to return with bad news but glad to have at least one version of Scratch working!!!

Hey DJ_Milestone,

Which OS are you using when you have these crashes?

Windows XP SP2 Intel Pentium M Processor 1.73 Ghz Toshiba w/2 GB memory.

Oddly... I updated to 1.9.0 from 1,8.2 and it works!

I'm totally confused by this! ;-)

A crash dump would be very helpful to find out what's going on. Can you please take a look at this article on how to get a crash dump -> www.serato.com (click link).

Can you then please try to reproduce this crash using 2.0, then attach the crash dump to this thread for us to take a look at. Thanks :)

Here you are. I think this is the right file. 2.0 wouldn't load. 1.9.0 is working again.
Let me know what you find. For giggles I updated the bios, audio and video driver from Toshiba's web site.

Windows XP SP2 Intel Pentium M Processor 1.73 Ghz Toshiba w/2 GB memory.

Oddly... I updated to 1.9.0 from 1,8.2 and it works!

I'm totally confused by this! ;-)

Hey DJ_Milestone,

Unfortunately the crash dump didn't work properly - were you definitely using 2.0 to make that crash dump?

Yes. I went into dr. watson and pulled this information. I believe it is the text version of the dump.