Just got off the the phone with Cakewalk tech. He had me uninstall and re-install visual C++ 2005,2008,2012. Nope. Didn't work. This is what Windows event viewer is giving me.
 
Faulting Application Path:    C:\Program Files\Cakewalk\SONAR X3 Producer\SONARPDR.exe

Problem signature
Problem Event Name:    BEX64
Application Name:    SONARPDR.exe
Application Version:    20.0.3.239
Application Timestamp:    526fbabb
Fault Module Name:    SONARPDR.exe
Fault Module Version:    20.0.3.239
Fault Module Timestamp:    526fbabb
Exception Offset:    0000000000de4898
Exception Code:    c0000005
Exception Data:    0000000000000008
OS Version:    6.1.7601.2.1.0.768.3
Locale ID:    1033
Additional Information 1:    bfd5
Additional Information 2:    bfd560a1aee3deef206ac7cdd904d7d7
Additional Information 3:    4cd9
Additional Information 4:    4cd97ef635cb8d5281d38a578ffff5cc

I believe that error is an access violation.
 
Are you launching Sonar with explicit Run as Administrator?
 
And, did you also do the original installation of Sonar the same way?
 
it is not enough just to BE an administrator, you must explicitly launch the installer with Run
As Administrator, to get elevated privileges/permissions.
 
And for whatever the worth, if any, I always have Sonar running with Run As Administrator, and modified the Properties of the Sonar icon (under advanced) to set that option.
 
Bob Bone

EppOobe.etl rename or deletion doesn't work either.
The mystery continues.

I still have x2 on  my computer and have no problems saving files. Never had to run the program as Administrator before. I've tried running X3 as administrator and that doesn't fix the problem either.

Another option I would try first is to re-apply the X3c patch and see if that helps.
 
Based on this "just happening," a "short term" solution is to back Windows to a point when you know X3c was working fine (i.e. doing a system restore of your machine prior to that set of MS updates would remove them). Start-> and type "System Restore" in the search area. Then you can choose a "restore point" back to when you know X3c was working fine. Also... that list (after you hit the "Next" button) will show what system level installations occurred and when (may provide more insight). You can also select a restore point and "Scan affected programs" to see what will change from doing the restore.
 
Actually, just knowing what is in the restore point list in the past few days might help.
 
 
 
 

So I run X2 as a test everything saves fine. So I thought, it's most likely not drivers, permissions, firewalls, etc. While I'm pondering my bleak Cakewalk recording future, I notice my X3c patch sitting on my desktop, and I'm thinking, my troubles didn't start till installed that little bastard. I realize I most likely can't downgrade to X3b without a lot of hassle so I thought about something that I hadn't considered doing and that no one had suggested...what would happen if I ran the X3c patch again? What do I have to lose at this point? So I ran the patch again, successfully annnnnddd....EVERYTHING'S FINE AGAIN! Are you kidding me? Good Lord. Thanks everyone for your suggestions. We'll see how long this one lasts....at least if I get the error, I'll know what to do.

The error post you made (#21 above) pointed pretty much straight to "SONARPDR.exe" so it is possible it was corrupted somehow. The patch file contains that file so was the quickest way to test. I am actually glad it was that simple.

Don't know if this would have solved your problem, but before I install anything, I turn off any virus protection software. Sometimes it flips out if your installation is trying to do something to the system.

> I've completed all the above steps up to full virus scan.
> "SONARPDR.exe" so it is possible it was corrupted somehow.
 
Hence the idea to run chkdsk earlier. Glad you got it fixed, but I would still run chkdsk now on your hard drives if you haven't done it yet (regardless of it being fixed or not) just in case there still is corruption somewhere.

robert_e_bone
I saw in a couple of web threads that deleting/renaming one file seemed to clear it up for some folks.
 
Might be worth trying.
 
Here is the snippet from one of the threads:
 
"Problem 2: “Microsoft Security Client OOBE” stopped due to the following error: 0xC000000D
It looks like this is caused by some kind of corruption in the AV Client, anyways simply rename the following file and reboot:
C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl (add .old or something)
Fixed!"
 
Please note that the above path is in a hidden folder (ProgramData), so you might need to enable viewing of hidden folders.
 
Hope that works for you, 
 
Bob Bone
 

I think #16 would have been by far and the best way to resolve this, ZoneAlarm Free + security essentials = not good and reinstalling should have cleared any legacy issues in the event viewer. Just deleting the .etl has had mixed results apparently.