taccess

It looks like a platinum BUG, your audio interface is not responsible.

I'd like to know how you get to this conclusion. He's using a 5 year old driver which is rated for Windows 7 on a Windows 10 system and as MSorrels points out there is a known bug with the version of Play he is using - That he doesn't want to roll back from.
If it were my system I'd explore other causes well before I leaped to the conclusion that this is somehow a PLATINUM issue.

Brando

taccess

It looks like a platinum BUG, your audio interface is not responsible.

I'd like to know how you get to this conclusion. He's using a 5 year old driver which is rated for Windows 7 on a Windows 10 system and as MSorrels points out there is a known bug with the version of Play he is using - That he doesn't want to roll back from.
If it were my system I'd explore other causes well before I leaped to the conclusion that this is somehow a PLATINUM issue.

If it were a driver or audio interface issue he would be experiencing it everywhere randomly, because he can repo at the same location it is in my opinion more towards a BUG ( inside : PLATINUM related to a instrument or routing or something he has that exposes this crash ).
 
I could be wrong and i encourage rolling back and eliminating a Audio driver as a possible cause and any other suggestions that may help locate the cause of this crash, but i am confident that he may be able to remove the crash/bug by switching off instruments or at least know for sure its not a particular type of instrument causing the crash !
 
The only way he will solve this is by elimination, if he skips anything he may skip solving the problem !
 

nonw of this is Kontakt. I can't figure that beast out. I'm only using EW Play.
 
So, I have multiple issues going on, and unfrotunately they've all gotten mushed into a single thread, mostly because I haven't been able to tell what's related and what isn't.
 
1) The crash I could repro by moving the now time to 18 minutes was indeed solved by splitting the project into two. I can no longer repro that particular issue.
2) The System and compressed memory spike in Task Manager which always portends an upcoming Sonar crash was made less frequent by going from 8 to 12 Gb RAM, but it still happens. I have learned that doing nothing but leaving the project open for a time is enough to cause the spike. (meaning: I can open this project, walk away, come back hours later, and will see SACM way up around 2-3 Gb, after which I will get a crash.) I am this morning in the process of freezing every EW Play track to see if Play is the culprit. Note: This issue was present prior to upgrading to Play 5.
3) My bassoon no longer loads - Play support sent me a new Bassoon folder, which fixed that problem. (Man, the EW support was responsive and helpful. Great experience there.)
4) The non-playing trails is still an issue, now that I know I should downgrad again to 4.3.5, I'll try that.
5) TTS crashes Sonar. After all the helpful comments here, I decided to avoid TTS entirely. I switched to Dim Pro's acoustic bass (thanks @Cactus Music!), but decided I liked the more orchestral-sounding Bass Violin in Play anyway, so I'm back to that. My harmonica was just a reference track prior to my recording live harmonica, so I'm living without it, maybe that will urge me on to get that track recorded sooner :-)
 
And to think in college I just needed to learn things like how to write a deceptive cadence in E flat....

Hi. Regarding the spikes. Do you have Wi-Fi, or a wireless mouse? That could cause these spikes.
Did you try LatencyMon from http://www.resplendence.com/downloads ?
I'm sorry if this has been asked before, but what kind of AV program do you use? Have you excluded SONAR from beeing scanned?
All the best.

Zargg
Hi. Regarding the spikes. Do you have Wi-Fi, or a wireless mouse? That could cause these spikes.
Did you try LatencyMon from http://www.resplendence.com/downloads ?
I'm sorry if this has been asked before, but what kind of AV program do you use? Have you excluded SONAR from beeing scanned?
All the best.

No wireless mouse, but a wireless solar keyboard, which has been giving me issues (duplicated keystrokes) the past few weeks. Swapped it out just now, rebooted, we'll see.
 
I don't run antivirus software typically. I have one but I only run it manually every once in a while, like after I've downloaded something I'm not entirely comfortable with.
 
OK, so after rebooting, I have my big Sonar project open, with every Play track frozen, and a wired keyboard, and i'm just going to let it stew for a while and see what happens. In a couple hours I'll check back and see if SACM crops up, and then I'll try adding things back in slowly to see what happens. I feel like I'm on the trail. If this were a binge-worthy Netflix show, I feel like I'm about 2 episodes from the end of the season. Let's hope there's no cliffhanger.

Update: After all this hassle, it looks like the problem may have boiled down to my wireless keyboard, of all things. Thanks to @Zargg! I played the project looped with all the tracks frozen and the SACM stayed low. So I un-froze everything and have been letting it play for an hour or two, it's higher than it was (300 Mb), but it hasn't spiked like it did.
 
I'm not totally convinced it's not going to spike up again at any moment, so I'm keeping an eye on it for a while, but so far so good.
 
Now if only I had a job...

All hail Zargg! FWIW when you isolate a problem to a hardware component, it's likely that it's also causing other issues that you just haven't identified yet. Now I know why I used wired stuff as much as possible...

Spoke too soon. While the keyboard might be related, who knows, the SACM spike is still happening. It's definitely the EW Play instruments causing the trouble. I'm going to see if I can isolate it to a specific instrument, maybe there's something buggy with it, rather than it being a Play problem all up. Stay tuned.

jkoseattle
 
1) The crash I could repro by moving the now time to 18 minutes was indeed solved by splitting the project into two. I can no longer repro that particular issue.

 
Can u Please elaborate on exactly what you did to split your project in two, so we can understand the workaround properly.
 

jkoseattle
Update: After all this hassle, it looks like the problem may have boiled down to my wireless keyboard, of all things. Thanks to @Zargg! I played the project looped with all the tracks frozen and the SACM stayed low. So I un-froze everything and have been letting it play for an hour or two, it's higher than it was (300 Mb), but it hasn't spiked like it did.
 
I'm not totally convinced it's not going to spike up again at any moment, so I'm keeping an eye on it for a while, but so far so good.
 
Now if only I had a job...

You do have a job........its to hunt this down properly and know for sure whats causing this to happen!

I still think you should take Zarggz advice. This is a powerful accurate tool that will let you know if you have PC problems that need attention.
A) Run  LatencyMon for 1 hour with just the PC on nothing else: Results should be under "800us highest"
 If its not the case let us know OR  If and when that is the case !
 
B) Run LatencyMon for another hour with your project on loop and everything Unfrozen : Results should be under 800us highest.  
If its not the case let us know OR  If and when that is the case !
 
C) If everything is still sweet and you want to be sure its the keyboard!
Run latencyMon again for another hour with your project on loop and everything Unfrozen this time with the keyboard plugged into the same USB port ?
 
Also if its your wireless keyboard maybe you have an IRQ conflict, which you can eliminate easily also !
 
 

I'll run this LatencyMon thing as well.
 
Sigh... if I ever get this solved, I think my piece is going to be really cool.