interesting...cleared my History folder... I had been using 1.9.2 up until now.

After I gave myself read/write access to the c: drive Serato and Serato Backup folders, it didn't seem to fix the issue. I cleared my History folder and haven't crashed since.

I also changed the Display setup to 20 frames per second based on another thread suggestion

It appeared to crash when I did a mouseover on any section that was black on the GUI. Not sure what happened since. The last thing I did was clear my history folder.

somebody closed this thread in error. I didn't close it. Any thoughts?

That day I thought I fixed it but it did not. Same issue...

So your current issue is crashing while analyzing?

crashing whatever I do. On 1.9.2 on Winxp everything works flawlessly. I have 0 corrupt files. I could never upgrade to 2.0 or higher - error messages said out of memory. I got a new PC with Win7-64bit Enterprise with 8GB RAM - external 2TB drive with plenty of free space. I crash just trying to play a few songs on the internal player. I haven't tried to hook up the Sl1 box yet.

some thoughts:
- Need to Analyze all over again? I didn't see anything that said you need to analyze files when moving from 1.9 to 2.
- don't think my Dbv2 file is corrupt since it works perfectly on 1.9.2 and every version earlier than that. I can analyze more than 1000 files at a time with no issues
- My guess is the admins will get me to redo my database. I understand that might be the easiest solution but I wish Serato team would just say you can't go from 1.9 to 2. without ditching your old database v2.

I am sticking to 1.9.2 since it is the only stable dataa

Know that the database can get corrupt for many reasons. None of which can be pinpointed.
Rebuilding it is not hard though.

Also know that just because it works in 1.9.2 doesn't mean something in it is not corrupt... at least to 2.0.

It is always recommended to re-analyze your library when updating to a new version as various versions handle/tag corrupt files differently.
It is very important to get rid of ANY corrupt files found.

All of this is irrelevant if your going to stick with 1.9.2 though.

With all due respect, I wish someone would elaborate on "handling tags differently".

If someone could give me a bit of a clue about what changed between 1.9 and 2, it would save us the few weeks to completely re-analyze. Also, if it is handling tags differently, perhaps I can make those changes without actually rebuilding the database.

If someone would just state in the requirements that users of 1.9 MUST rebuild the database, I could handle the truth. It was never stated as a prerequisite or requirement.

Rebuilding your database is NOT a requirement for updating to 2.0 or any version for that matter.
It IS suggested that you re-analyze your entire library when updating to a new version though due to various versions handle corrupt files differently.
Some versions may tag files as corrupt where as others won't.
Corrupt files may freeze or crash your system so its very important to get them out.