Here's another example from my own experience.  For the last two or three days I've been pulling my hair out because Sonar suddenly required 2, 3 & sometimes 4 tries to get it started.  I'm thinking WTF?!
 
Then I remember I had been trying to get my Peavey AT200 to work with the MIDI interface in the 16x08.  I unplugged the AT200 and Sonar is back to normal, screaming right along.
 
I like the new Sonar (X3e & up) much, much better than other DAWs I've used/tried out, but Sonar has always been more sensitive to its hardware environment that any other DAW I've used.
 
That's the reason I always think hardware when Sonar problems pop up, or even when they first appear with a new version of Sonar.  That might sound like a problem, but right now S-PlatD is a screaming, rock solid monster for me.
I've never had a DAW that performed this well.  So much so that I'm feeling pretty spoiled at the moment  :)
 
 

Doktor Avalanche

tenfoot
I am having the exact same experience with Platinum. Loads of wsod crashes when moving notes in midi intensive projects - once I render to audio solid as a rock. It seems to play particularly poorly with Sample Tank 3. I have reverted to working in X3 until all tracks are audio now. Fingers crossed for the next update!

Just because it works in X3 doesn't mean we can assume it is a Platinum issue. Software is based on dependencies you are dealing with a moving target. Please try the following (at each stage test to see if it is working or not):
 
1) Update the plugin to the very latest version. Make sure you are running 64 bit.
2) Perform a VST reset.
3) Run Sonar as Administrator
4) Run windows update several times.
5) Update your device drivers and firmware everywhere, esp your audio interface.
 
I suggest a new thread if that doesn't sort it. Everybody has a specific issue, it generally isn't useful to taint all issues under the same umbrella.

Thanks for the suggestions Doktor. All of my drivers and firmware are up to date, as is Windows. I use exclusively 64bit plugins. I will try a VST reset and running as administrator and see how it goes. 
I am slightly perplexed as to how it is not a Platinum issue when exactly the same project and plugins run on the same system in X3 without issue so I will have to take your word on that.
I know that in years past I have spent many hours troubleshooting problems that I was told were not Sonar issues only to have them dissappear with a further update, so I tend to find a workaround and wait patiently in my old age:)

> I am slightly perplexed as to how it is not a Platinum issue when exactly the same project and plugins run on the same system in X3 without issue so I will have to take your word on that.
 
It's a common misconception. Often it's down to DLL libraries being incompatible with each other, but here's a simple example. Pretend Sonar X3 had a bug that Plugin X worked around with it's own code. Then Platinum fixed that bug, however Plugin X hasn't been updated to reflect the fact. That workaround code still in Plugin X could cause it to crash in Platinum until it gets stripped out. Throw it back into X3 though and it's business as usual. Just one example I stress.

If I understand that correctly, there was crashes inside a project with MIDI tracks only going to external HW Synth. That exclude VSTs from possible problem origin. Audio is also not in use. Leaving Sonar itself + Control Surfaces + MIDI drivers. But MIDI drivers can be excluded by crash with just TTS1 only. And so, in case Control Surfaces are not connected (which I have asked already), the problem is somewhere in Sonar...
 

azslow3
If I understand that correctly, there was crashes inside a project with MIDI tracks only going to external HW Synth. That exclude VSTs from possible problem origin. Audio is also not in use. Leaving Sonar itself + Control Surfaces + MIDI drivers. But MIDI drivers can be excluded by crash with just TTS1 only. And so, in case Control Surfaces are not connected (which I have asked already), the problem is somewhere in Sonar...

 
To be clear I was previously responding to tenfoot's issue who has a completely different issue with Sample Tank 3. I've asked him to create a new thread if the issue persists.
 
With hardware there are other dependencies to look at. For instance is there are services running (NI for instance has and Native Instruments hardware service). It could be that the firmware and drivers of the hardware is not up to date. It could be that the motherboard BIOS and chipset drivers aren't up to date either. Check Intel driver update website for instance.
 
Assuming this is all ruled out (apparently it has been looking at quote above?) I would check the Windows Event Viewer. Has Windows update been run recently? I also notice Trillian hasn't been ruled out (is that up to date?). Has a VST reset taken place recently? (see my previous post). Is it project specific... Does it happen with new projects? etc

Doktor Avalanche
> I am slightly perplexed as to how it is not a Platinum issue when exactly the same project and plugins run on the same system in X3 without issue so I will have to take your word on that.
 
It's a common misconception. Often it's down to DLL libraries being incompatible with each other, but here's a simple example. Pretend Sonar X3 had a bug that Plugin X worked around with it's own code. Then Platinum fixed that bug, however Plugin X hasn't been updated to reflect the fact. That workaround code still in Plugin X could cause it to crash in Platinum until it gets stripped out. Throw it back into X3 though and it's business as usual. Just one example I stress.

Thanks Doktor - that's good to know. When you think of all of the variables we should be grateful anything works I guess!

Doktor Avalanche
To be clear I was previously responding to tenfoot's issue who has a completely different issue with Sample Tank 3. I've asked him to create a new thread if the issue persists.

Ups... It sometimes hard to remember who has which problem, especially when the result is WSOD in both cases

Yup I end up confusing myself many times, and with a thread with multiple issues - it becomes a never ending feedback loop....

This may be unrelated, but worth mentioning. Markyzno dropped a nice tidbit in a video thread about K-Lite codecs. I installed these and the installation scoured my machine and removed 5 or so bad codecs (most were DirectShow, IIRC), replaced them, and removed all the bad reg entries calling them (close to 20).
 
As you mentioned TTS-1 (which is DirectX) installing that codec pack is an idea. It definitely will not hurt, but will also get the crap off your machine (you may not even know about). Here is a link to their download page (I got the "mega" pack (11MB or so), and did the most advanced install option just to watch the installer run).

azslow3
If I understand that correctly, there was crashes inside a project with MIDI tracks only going to external HW Synth. That exclude VSTs from possible problem origin. Audio is also not in use. Leaving Sonar itself + Control Surfaces + MIDI drivers. But MIDI drivers can be excluded by crash with just TTS1 only. And so, in case Control Surfaces are not connected (which I have asked already), the problem is somewhere in Sonar...
 

Yes, I've eliminated almost everything, including hardware. I'll see if I can reproduce it without the control surface. I'll let you know later tonight.
Thanks