My system has been running solid for a while now, but the last few nights I've run into a new problem. When I open the project I'm currently working on from my D: drive (SSD), the project won't open. I get the "Sonar has to close" box. However, if I open the same exact project from my external E: drive, where I have my backups, the project opens normally.
 
Upon opening, I immediately Saved As to a new folder/project on my D: drive. Close out everything, and the project will open fine from the D: drive. However.....when I begin a session the following day, I run into the same exact problem. Seems to be something happening when I shut down/restart the computer.
 
I installed the latest Platinum update last night before bed, so I haven't tried opening with the latest update yet. Hopefully that will solve any issues, but I'm not really holding my breath.
 
Any thoughts? Thanks so much.
 
~Jeff
 
[SOLVED] Edit: After updating to the latest Platinum, the previous night, turned on my system with fingers crossed. The project from my D: drive opened perfectly with no issues! Didn't have to do anything.....it just worked as it should. System running rock solid again. Very happy camper here!
 
~Jeff

Since the following issue is timing-related, it could account for what you're seeing if one of the referenced plugins is in the project:
 
     http://forum.cakewalk.com/UPDATED-Instability-with-certain-Cakewalk-plugins-after-recent-Windows-10-updates-m3526221.aspx
 
Try enabling one of the Windows Compatibility Modes as suggested.

brundlefly
Since the following issue is timing-related, it could account for what you're seeing if one of the referenced plugins is in the project:
 
     http://forum.cakewalk.com/UPDATED-Instability-with-certain-Cakewalk-plugins-after-recent-Windows-10-updates-m3526221.aspx
 
Try enabling one of the Windows Compatibility Modes as suggested.

Aaah. The Zeta! I do have that in my project. Thanks Fly. Hopefully the update will have fixed this.

Jeffiphone

brundlefly
Since the following issue is timing-related, it could account for what you're seeing if one of the referenced plugins is in the project:
 
     http://forum.cakewalk.com/UPDATED-Instability-with-certain-Cakewalk-plugins-after-recent-Windows-10-updates-m3526221.aspx
 
Try enabling one of the Windows Compatibility Modes as suggested.

Aaah. The Zeta! I do have that in my project. Thanks Fly. Hopefully the update will have fixed this.

As far as I can see, the update does not address the timing issue.  However the workaround (Windows Compatibility Mode) posted in the linked thread does address it .

abacab

Jeffiphone

brundlefly
Since the following issue is timing-related, it could account for what you're seeing if one of the referenced plugins is in the project:
 
     http://forum.cakewalk.com/UPDATED-Instability-with-certain-Cakewalk-plugins-after-recent-Windows-10-updates-m3526221.aspx
 
Try enabling one of the Windows Compatibility Modes as suggested.

Aaah. The Zeta! I do have that in my project. Thanks Fly. Hopefully the update will have fixed this.

As far as I can see, the update does not address the timing issue.  However the workaround (Windows Compatibility Mode) posted in the linked thread does address it .

I'll try, but why would the backup project file from my external E:drive open without issue? The project on the main drive (SSD D:drive) is the one that won't open.

The root cause of the problem is apparently a 'race' condition that's been triggered by a change to thread initializaiton timing in Windows 10. The outcome of a race condition can depend on microsecond-differences in event timing. So  you can get a different result after restarting SONAR, re-launching the project, rebooting, loading from a different drive, etc. in an unpredictable way.
 
 

brundlefly
The root cause of the problem is apparently a 'race' condition that's been triggered by a change to thread initializaiton timing in Windows 10. The outcome of a race condition can depend on microsecond-differences in event timing. So  you can get a different result after restarting SONAR, re-launching the project, rebooting, loading from a different drive, etc. in an unpredictable way.
 
 

Okay.....so what do I do? The compatibility mode thing says choose Windows 7 and 8. I'm running Windows 10.
 
I just hoping that the latest update will make all this go away.

Jeffiphone

brundlefly
The root cause of the problem is apparently a 'race' condition that's been triggered by a change to thread initializaiton timing in Windows 10. The outcome of a race condition can depend on microsecond-differences in event timing. So  you can get a different result after restarting SONAR, re-launching the project, rebooting, loading from a different drive, etc. in an unpredictable way.
 
 

Okay.....so what do I do? The compatibility mode thing says choose Windows 7 and 8. I'm running Windows 10.
 
I just hoping that the latest update will make all this go away.

"Compatibility mode runs the program using settings from a previous version of Windows. Try this setting if you know the program is designed for (or worked in) a specific version of Windows."
 
https://support.microsoft.com/en-us/help/15078/windows-make-older-programs-compatible
 
It was recently discovered that telling Sonar it was running on an older version of Windows somehow bypassed the issue in Windows 10.
 
They are working on a fix, but it was not released in the latest Sonar update.  They have provided this workaround in the meantime.  Try it, cant hurt!

abacab

Jeffiphone

brundlefly
The root cause of the problem is apparently a 'race' condition that's been triggered by a change to thread initializaiton timing in Windows 10. The outcome of a race condition can depend on microsecond-differences in event timing. So  you can get a different result after restarting SONAR, re-launching the project, rebooting, loading from a different drive, etc. in an unpredictable way.
 
 

Okay.....so what do I do? The compatibility mode thing says choose Windows 7 and 8. I'm running Windows 10.
 
I just hoping that the latest update will make all this go away.

"Compatibility mode runs the program using settings from a previous version of Windows. Try this setting if you know the program is designed for (or worked in) a specific version of Windows."
 
https://support.microsoft.com/en-us/help/15078/windows-make-older-programs-compatible
 
It was recently discovered that telling Sonar it was running on an older version of Windows somehow bypassed the issue in Windows 10.
 
They are working on a fix, but it was not released in the latest Sonar update.  They have provided this workaround in the meantime.  Try it, cant hurt!

Gotcha. Thanks Cab.

[SOLVED] After updating to the latest Platinum, the previous night, turned on my system with fingers crossed last night. The project from my D: drive opened perfectly with no issues! Didn't have to do anything.....it just worked as it should. System running rock solid again. Very happy camper here!
 
~Jeff