1. Check if you have all project built with same unmixed compiler version 060. Still getting error, then go to Step 2. Are you using same compiler options when you switch compilers.
2. Start with the project built with compiler prior to 060 (051 or smthng, discarding files that have compiler bug), which comes clean while debugging. Slowly, incude some set of DLL's to be built with 060, and notice if the crash comes while debugging. Then include more DLL's to build with 060. If that is practical to handle given the multiple levels of DLL, that can narrow down the error location window. In debugging environments that I worked, there is also a possibility of system or environment files interfering with the application locks/synchronization., causing deadlocks and crashes as well, though this might not be the case here.
If1. & 2.does not work out well, you may need to work with some system expert that has extensive knowledge of Process Monitoring tools , only in case its not caused by the compiler. But anyway, it may give some insight into the cause & nature of crash.