So close to getting a mix finished.
 
Another BIG CRASH, SPLAT just gave me 120 error reports with 120 different dump files.
 
Then it did the 'Windows would like to shut this programme down'.
 
I just moved my Massive Passive EQ... that was all. 1 stereo bus to another stereo bus.
 
The worst thing is: even saving sessions religiously, it doesn't save the last hour or so of my work.
 
This is getting very time-consuming.
 

Sorry pwalpwal, I just read your message, after I posted my rant.
 
I have to try & get work finished for a client.
 
I will try & reproduce the crash on a new empty project next week,
 
Thank you.

Larry Pumpkin
I am experiencing crashes on every session. Usually I am just trying to move a plugin from one track to the next.
 
I get around 60 fault report windows open & only one of them sends the error report.
 
Takes me a good half hour of clicking to try and get to a point where I can close SPLAT down.
 
I haven't had any luck being able to view the mini dumps with the tools mentioned above.
 
Does anybody know how to open the SPLAT mini dump files???
 
Is there a way I can get Cakewalk to follow up on the error reports?

I have been checking on the status of theses reports for months now & it would appear they haven't been looked at.
 
Any advice would be appreciated.
 
 

I have had this problem occur too except that a fault report will never get sent as my DAW pc is offline. Rather than clicking on each instance I right click on the fault reporter icon in the taskbar and select close all windows so this at least makes them all go away at once.
 
I have wondered if it is possible to disable this fault reporter function as with an offline pc it's never going to go anywhere anyway.
 
You might also want to have a look at what your OS disk clean up reveals as I also found nearly 70GB of CW files dumped in the windows error reports which seems to happen every time it crashes. I only discovered this when I noticed that the space remaining on my OS drive had reduced considerably even though very little had been installed onto to the PC for quite some time. I would add that this issue pre-dates platinum as I was still on X3 when I discovered it. It had obviously been going on for quite some time, but I didn't notice as X3 crashed on me very occasionally and it was usually the same project that it didn't like for some reason, so it built up gradually over time. I suspect something to do with BFD3 in that case, but Plat seems to crash all the time particularly when freezing synths for some reason and sure enough run disk clean up and there will be several GB of files listed in windows error reporting.
 
 

rjeynes
+1 for the crazy behaviour of the Fault Reporter which is now adding to the horror of the all-too-frequent crashes which seem to occur around plug-in activity (moving, adding or deleting plugins etc.). The crashes now stimulate a non-stop loop of the Fault Reporter starting itself multiple times.
 
Close to despair. Has anyone found 2016.12 any better than 2016.11?
 
 

I can't speak for 2016.11 as 2016.12 was my first installation of Platinum, but I can confirm that 2016.12 crashes all the time and triggers a fault reporting frenzy. (Win7 64 if it matters.) See my previous post for how to close the fault reporter more quickly.

UAD - DAW Compatibility
 
https://help.uaudio.com/h...779-DAW-Compatibility-
 
However, due to plug-in host differences between DAWs — and our own rigorous testing standards — Universal Audio only officially tests the latest UAD software with:

• Avid Pro Tools 10*, Pro Tools 11, and Pro Tools 12
• Apple Logic Pro X
• Steinberg Cubase 8 and Cubase 8.5
• Steinberg Nuendo 7
• Ableton Live 9

Q: Does this mean that my DAW is not supported?
A: Generally any VST, RTAS, AAX 64, or Audio Units-compliant host application will work with UAD plug-ins, and any ASIO or Core Audio-compliant application will work with Apollo audio interfaces. That said, if you are experiencing issues with your UAD or Apollo on a DAW that we don't list as compatible, you can still contact UA Tech Support and log the issue with us

Not sure if this is directly related but it seems like we never heard about what was causing the problem with Sonar crashing with certain plug-ins. It seems like for some people is just magically fixed itself.

jimo
Not sure if this is directly related but it seems like we never heard about what was causing the problem with Sonar crashing with certain plug-ins. It seems like for some people is just magically fixed itself.

I'm one of the ones who's problems were magically fixed on 12/13. I feel pretty sure it was something MS did. Tuesdays are the days they do updates. IN my situation the only explanation anyone has come up with is there must have been a silent update or something similar that MS did without my permission that may have seemed harmless to them, but affected this strange timing issue bug with plugins. Since then all has been well for me and I used 2016.12 and now am using 2017.01.
 
After this debacle I found several ways I can protect my computer from MS, so I’m not caught off guard again. You can read about it in the Cakewalk computer forum

Might be a good idea to change the title of this thread to reflect the update it is talking about. It seems to get resurrected with each new release!

tenfoot
Might be a good idea to change the title of this thread to reflect the update it is talking about. It seems to get resurrected with each new release!

Changed!!

jimo
Not sure if this is directly related but it seems like we never heard about what was causing the problem with Sonar crashing with certain plug-ins. It seems like for some people is just magically fixed itself.

Read the thread in the forum stickies about problems with CA2A etc.