Project goes so far and just stops.

This is a new one for me.
 
I guess I need to know where the crash dumps are kept and how to read them. Windows dumps. Sonar just stops. I can tell you that it seems like an audio dropout but Sonar does nothing but crash. At the same point, in the timeline, in the project as well.

Hello Robert welcome to the forums!
 
Here is a checklist...
 
Does this happen with new projects?
Have you checked the windows event viewer?
 
Have you updated all your drivers esp your sound interface?
Have you run windows update?
Run this: http://forum.cakewalk.com/Driver-Boost-m2928792.aspx
Have you investigated your latency with latency monitor? (check google for instructions)
 
Cheers
 
Oh and ps I assume you have X3A patch installed?

> Oh and ps I assume you have X3A patch installed?
 
I'm using X2 as stated in my signature.
 
Install X2A patch. Otherwise please check my previous post (I'm not sure what you have tried or not tried - or indeed if this is a response to my post).
 
> AFAICT, there should be no reason for this.
 
It could be for any of the reasons I have posted, or you may find something in the event viewer.
 
> I'm going to create a new project with all the correct settings and copy the clips over and see what happens.
 
Good idea, good luck.

I changed the audio and midi buffers and no joy.
 
This copy and paste this is turning out to be a disaster. Even one track at a time.

I can't seem to figure this out. Maybe Sonar has broken somehow. It's happened to me before. I've ran other projects that use more CPU and no problems there.
 
Does anyone have the info about removing Sonar completely for a re-install.

Not sure we are talking about the same thing, but sometimes a song will play a few measures and stop.  Nothing but a restart fixes it.

Just to verify, did you adjust the audio and I/O buffers? I had a very repeatable audio engine dropout with the X3 demo file (exactly at the start of the 18th bar every time) because the buffers were too high. The X3 demo file is actually a good one to tailor your buffers with because it is handy and fairly complex (mute the final mix down track, and play the rest of the file for the test).
 
Tailoring DAW buffers:
Stay in ASIO mode first. There is some tailoring that needs to be done between the audio buffer and the I/O buffers. I had my ASIO buffer too high the other day and FastBikerBoy sent me back a nice PM on this:
 
   Start with the ASIO buffer at 128 (Preferences->Audio->Driver Settings->ASIO Panel...), and I/O buffers at 512 (Advanced Mode: Preferences->Audio->Synch and Caching)

1. Set preferred audio buffer.
2. Start playback.
3. If it drops out or other issues adjust I/O buffers. Try 512 for both as a starting point.
4. Repeat steps 2 & 3. Try adjusting buffers both up and down until happy. 256 jumps should do.
5. If after trying all sizes up to 1024 you still have issues go back to step 1 and increase audio buffer.
6. Repeat as necessary until you find the "magic" combination for your setup.

   The 128 audio and 512 for I/O was the "magic" combo for me.

I stated that I tried the buffers both audio and midi. I've adjusted latency setting. Those are the simple things to try.
 
The event viewer says that Sonarpdr hangs.
 
I noticed last night that there were track oddities. Tracks that won't play for whatever reason. I copied the clips to a new track and they played but there is still more weirdness I'm finding out with this track and have no idea how it got this way.
 
I had to stop messing with it as it was consuming to much time. I'll probably give it a go again tonight.

Whelp, I have no idea what I did but I just played the track and it worked fine. I'm going to go bang my head on something or maybe count to 10. I haven't decided. I guess the good news is that it's working fine.
 
There were tracks that were not showing up in the inspector properly. Say track 32 was a secondary guitar track. I record both an amped and clean track and in this case, the clean track, 32, was not showing up properly. Every other track would show up in the inspector but that one. When I selected it, or just put in focus, the inspector showed it's bus going to itself.  I copied the clips and put them in a new track, deleted the weird ones, there were several, and set everything the way I wanted. Plus I did some window cleaning and both seemed to have fixed the problem.
 
That "driver booster" was a nightmare. It updated drivers fine but played havoc on the Catalyst Control Center (the software to control my video card). I guess I'll use it to find out what needs updating and just go find the drivers myself rather than let it do it.
 
Thank you everyone for helping.
 
BTW - CakeAlex, Welcome to the forums! ;-)