Only 1 Processor Core working since Win auto update

Some time last month my PC did some sort of auto update on Windows 10. I have been on 10 for a while but about 2 weeks or so ago I noticed things were different on both my desktop and laptop. Last night was the first time I really did anything with Sonar since. While constructing a drum track w/SSD play back was glitchy. I noticed that only 1 Core in the monitor was registering, I made sure multicore was checked in preferences but still only showing 1 processor working. Any tips or ideas? As far as I could tell system info says all 4 Cores are working. I am still running x3 Producer because since purchasing lifetime SPLAT in August I can run it for more that 30 seconds with out crashing.

Perf meter options are new to the latest release of 2016. OP is reporting this against X3.
 
For X3, make sure CPUMeterMode=2 in Cakewalk.ini ( I don't recall if this was accessible via Preferences in X3 as it is now).

X3 is out of support. Maybe more details about the Platinum issue would be helpful. There is not much in your other post http://forum.cakewalk.com/FindPost/3472260. When did you open your case with support? Did you file a problem report with a crash dump? If so, do you have a CWBRN?

brundlefly
Perf meter options are new to the latest release of 2016. OP is reporting this against X3.
 
For X3, make sure CPUMeterMode=2 in Cakewalk.ini ( I don't recall if this was accessible via Preferences in X3 as it is now).

I missed the "still running X3" sentence 

stm113cw
The issue with Platinum is that it crashes in less that a minute no matter what I do. I have opened projects normally, in safe mode, create new projects, all the same. I screen shot the error and sent it in with my support request. I sent that during the time of that last thread. It's been frustrating to say the least. I have very limited time these days to work on projects and I'm not happy about having to spend that time troubleshooting.

bitflipper
If all you've got in your project is a MIDI track and a drum synth, then it's likely that only one core is working, and that would be normal. 

don't know what MIDI setup (external synths?, drum modules?, digi mixer?) you are using, but check for MIDI loops that might fill up some buffer ... had to happen once and it crashed every exactly 58 seconds, was hard to track down and was caused by sending the MIDI clock to a device that didn't need, but echoed it back and got it send again ... exponential meltdown lasting 58 seconds ...

Is all of your Windows maintenance up to date?  How about maintenance for any drivers or for Sonar?
 
Have you 'tweaked' anything in either Windows or Sonar?  If so, please list the tweaks you have applied - perhaps one of those doesn't play well with Sonar.
 
Do you happen to use any 32-bit plugins in a 64-bit Sonar?  Even with the supplied BitBridge or the commercially available JBridge, things frequently get flaky when 32-bit plugins are used in projects in a 64-bit Sonar.
 
I would add that since most folks are not reporting such crashes, your particular crash frequency is likely due to one or more things local to YOUR system or its configuration.  I only say this because I believe that to be a far better situation than if LOTS of folks were having frequent crashes, because that WOULD more likely be a Windows or Sonar problem.  SOOOOO - if we keep digging into YOUR system setup and configuration, a solution is quite likely.
 
Bob Bone

While you're waiting for support to get back to you, have a look at your Windows Event Log. The answer you seek might be in there.

Hey Keith is this what you're asking me about? CWBRN-55497. Thank you by the way.