I have personally never been able to produce the error in a fresh project. In fact, removing PC modules, saving, then reopening solved the crashes for me. I could even re-add the offending modules with no problems.
I haven't been able to figure out exactly what causes it. Your steps are exactly what produced the issue for me except most of the time my projects are fine and run without crashing, no matter if they're simple or complex. Once it becomes afflicted, it will very consistently crash from your list of steps.
 
If we could reliably reproduce this in a fresh project it'd go a long way towards solving it.

CakeAlexS
Vernon I followed the steps and your note however I had to create my own steps (in order to fill in the gaps)...
After testing via my guesswork it became obvious I'm never going to recreate this issue unless I have the specific steps.

I'm not sure what we are supposed to do, record, play back, can we be specific about what "switch to different tracks" means? Are we clicking on layout view (on the other monitor) or tracks on the console view, where are we clicking (the track numbers at the bottom, clips?). Could we be totally specific about this...
 
Thanks..

My Current steps... (Modified)

1) Create new project (select normal template).
2) Insert 8 audio tracks.
3) Undock Console View and drag to 2nd monitor.
3a) Add CL (Concrete Limiter) to Master bus
4) Expand Pro Channel in console view
4a) Go to different tracks in console view.. Add effects .. Take them away.. select from the bottom... have fun with it..
4b) After going to different tracks.. in CV go back to the Master bus in CV
4c) Repeat process until white screen....
5) If I take the CL out... No crash..
 
 
Hi Alex,
 
I took the liberty of modifying your steps above.  When I had talked to the guys at Cakewalk they "found" a machine that exhibited the behavior.  So while it may not affect every machine.. it is definitely reproducible. I appreciate everyone's input and effort into this.. Thanks.

One additional thought - LunaTech - I notice you have a Saffire Pro40. I use a pair of them.

jeebustrain
One additional thought - LunaTech - I notice you have a Saffire Pro40. I use a pair of them.

I do but not a factor in this case as I use the Pro 40 for my PT rig...Hopefully we can get so traction on this.

Since moving to Win8.1 x64 I haven't seen this issue. The move to new OS coincided with this new PC as well as X3.

mudgel
Since moving to Win8.1 x64 I haven't seen this issue. The move to new OS coincided with this new PC as well as X3.

That was exactly my experience - this was a totally new build on 8.1 x64, running X3c. It was rock solid.
 
Between then and opening this particular project, I did the following things:
Install X3d
Install Komplete9
Install Concrete Limiter PC
Install Expander/Gate PC
 
Unfortunately, I did NOT create a restore point prior to X3d, so rolling that back is impossible (short of a reinstall).
 
Also - tonight I started messing with a project that I had originally created in X2, then had already opened in X3c. I have not been able to make this particular one crash yet. The night is young, though.

I am frustrated with this thread, as I could repeat this 100% with X2a. I assumed it was fixed, but this thread made me go searching for it last night and I cannot. My machine hasn't changed one iota (other than updates) and installing X3, so now I am just baffled.
 
I did happen to find a weird one, by having Geist on a second monitor, saving the file, then trying to reopen with File->Recent Files list... X3 would "just close." When reopened the Recent Files list no longer had that file listed, but X3 only closed when using the recent file list. The file reopened by any other method fine. It is almost like a registry pointer error (i.e. X3 has the pointer, but the registry does not have the physical entry made yet). After closing SONAR manually and reopening it, the recent file option worked (issue "went away" as it were), and everything popped open onto its two monitors fine. For that one, it seems that X3 may only update the recent file listing in the registry on exit (but only speculation, of course).
 
I am laughing that I am actually "looking for bugs"... I am finding it very difficult to crash X3 (is almost like a red badge of courage in a way )

jeebustrain

mudgel
Since moving to Win8.1 x64 I haven't seen this issue. The move to new OS coincided with this new PC as well as X3.

That was exactly my experience - this was a totally new build on 8.1 x64, running X3c. It was rock solid.
 
Between then and opening this particular project, I did the following things:
Install X3d
Install Komplete9
Install Concrete Limiter PC
Install Expander/Gate PC
 
Unfortunately, I did NOT create a restore point prior to X3d, so rolling that back is impossible (short of a reinstall).
 
Also - tonight I started messing with a project that I had originally created in X2, then had already opened in X3c. I have not been able to make this particular one crash yet. The night is young, though.

I would be really really surprised that this is operating system specific.
I would lean more onto the fact it was resolved in some Sonar update (let's say X3D although it could be any update I don't know), and that projects created before this update was installed maybe still have this issue (and maybe always will unless Cakewalk has introduced some code that cleans up projects). So my perception is right now if you create a new project in X3D with a template that was made with X3D, you won't be able to reproduce this.... No doubt I will be proved wrong shortly....

Alex, I have only changed to X3, my OS is the same. Since I have not seen this, I "assumed" it was fixed, but the other folks here have me concerned as to if that is true.

Yup I still maintain an open mind as well, but so far no reproduction with X3D and new projects, hoping it will stay that way !!!!