My cakewalk project fails rendering at the same point every time.

[Santiago Nelson]

Bouncing the project to a track? I'm not sure what you mean exactly Base 57, but Byron Dickens I have frozen all the tracks.

ALSO UPDATE: I got it to finally export using these settings: (it was 24 bit not 32)

I had forgotten to set it to "time selection however", this time I turned off "Render in Real-time" but I actually got lucky and the project didn't mess up the bus automation's like it did prior when I had "Render in Real-time" off, so I don't know if I just got lucky or if this will keep working, I'll try and render just my section, after I make a small change to an instrument I wanted to tweak. hopefully it stays good!

[mettelus]

I would recommend doing a cleanup of that project, especially if it is in its final stages. Before you start, do a File->Save As... with a new name (you can put it in the existing project folder).

Once that is done, I would do the following:

1. Delete all of the Archived tracks. If you are not using them, get rid of them.
2. Trim off the right end of the project (unless your export end is really 321 bars?). Some of the tracks appear to have no data, but still go on (Tracks 5, 6, and 9 from the OP). If specific to only certain tracks, you can split those and delete everything to the right, especially if they are truly empty... is that automation data in those?
3. Do a deep dive into what FX and automation you are using. Some FX are not CPU friendly at all, but unfortunately Cakewalk doesn't give you a list of FX running in the project and load/lag associated with them. As this is happening in the same place, I am highly inclined to assume it is an FX choking. When tracking, you want buffers low, but when mixing you want to bump those up in preferences (to 512, 1024, or sometimes 2048). This gives the CPU more time to fill buffers and is required if you have unbounced Melodyne Region FX in the project.
4. Check the event list for where the crash is occurring just to see if there is something in there that is obvious (this is unlikely, but good to check anyway).
5. If that will offload at some point, I would also consider creating a another project at 44.1/24 and drag/dropping the new cwp from your browser into it (that will populate the new project with the data from the cleaned up one), then do another Save to that second new one so it is in a 44.1/24 format.

Just bear in mind, that even with a capable computer, the right recipe will drive it to its knees. Rather than save/keep everything (this is better done through saving versions as you go), try to keep things simpler in the working version. 

[57Gregy]

I'm wondering why so have so many muted tracks that are selected and the export option to render muted/soloed tracks? Plus, it seems like most of the tracks still have an input selected.
Confuses me. Maybe confusing the computer, as well.