So I upgraded to X3d about a week ago. I had this old project (from X2a producer) that I tried to open. I'm using mostly ProChannel modules for effects. For some reason, whenever I click any of the buses (whether they be master or otherwise) in console view, Sonar crashes. According to the log, it's usually a couple different PC modules (either the concrete limiter or the expander/gate usually). I've tried removing various modules and re-adding them. I've also tried re-loading the project in safe mode and excluding all of them, it still seems to crash.
 
The weird thing is that I can manipulate anything from the track view or the single channel strip without issue. But even if I just try to move a fader or hit solo or mute on the console, it crashes.
 
I'm not sure if this is related to X3d (I had X3c before) or that this is a project pulled in from X2. I no longer have X2 loaded as I did before (I wiped/rebuilt the box). I thought I had read someplace about people having certain problems with plugins when coming from X2. So far, I've been working with at least 5-6 other projects from X2 without any issues whatsoever.

Has anyone seen this?

So in a nutshell this just happens for one project?
 
Please could you check the windows event viewer for Sonar crashes and paste the text here.
Find the error under Custom Views -> Administrative Events.
 
To Copy, right click the red icon -> Copy -> Copy Details as Text.
Then paste here...
 
p.s.
 
Could you please reset and rescan your plugins.... Thanks... 

to answer your first question - yes, so far this seems to be isolated to a single project. I was messing around tonight and actually thought I had it solved. I realized there were some VST plugins loaded on some of the buses (but disabled). They were from a long time ago, before I was totally comfortable using the PC modules. They'd long since been disabled, but I never actually deleted them. Once I deleted/saved, it seemed to work. But I just tried again before and it crashed. So I reset/rescanned all plugins. I went back into the project and made sure that every disabled vst was deleted out of every track. I saved and closed and reopened. If I click in the track view, then click anywhere on the Master channel (or any other bus) in the console, it still crashes. Here are the 2 windows evt log messages. The first is an error, the 2nd is informational.
 
1st:

Log Name:      Application
Source:        Application Error
Date:          12/24/2013 22:59:46
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      lamia
Description:
Faulting application name: SONARPDR.exe, version: 20.0.4.278, time stamp: 0x52abb061
Faulting module name: ProChannelConcreteLimiter_64.dll, version: 1.0.1.64, time stamp: 0x4f1de4ce
Exception code: 0xc0000005
Fault offset: 0x000000000002bea4
Faulting process id: 0xe8c
Faulting application start time: 0x01cf012e0eff1d92
Faulting application path: C:\Program Files\Cakewalk\SONAR X3 Producer\SONARPDR.exe
Faulting module path: c:\program files\cakewalk\shared utilities\internal\ProChannelConcreteLimiter\ProChannelConcreteLimiter_64.dll
Report Id: 5f9a9b8b-6d21-11e3-826b-3085a99dee16
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-12-25T04:59:46.000000000Z" />
    <EventRecordID>3326</EventRecordID>
    <Channel>Application</Channel>
    <Computer>lamia</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SONARPDR.exe</Data>
    <Data>20.0.4.278</Data>
    <Data>52abb061</Data>
    <Data>ProChannelConcreteLimiter_64.dll</Data>
    <Data>1.0.1.64</Data>
    <Data>4f1de4ce</Data>
    <Data>c0000005</Data>
    <Data>000000000002bea4</Data>
    <Data>e8c</Data>
    <Data>01cf012e0eff1d92</Data>
    <Data>C:\Program Files\Cakewalk\SONAR X3 Producer\SONARPDR.exe</Data>
    <Data>c:\program files\cakewalk\shared utilities\internal\ProChannelConcreteLimiter\ProChannelConcreteLimiter_64.dll</Data>
    <Data>5f9a9b8b-6d21-11e3-826b-3085a99dee16</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 
2nd:

Log Name:      Application
Source:        Windows Error Reporting
Date:          12/24/2013 22:59:51
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      lamia
Description:
Fault bucket 150795621, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: SONARPDR.exe
P2: 20.0.4.278
P3: 52abb061
P4: ProChannelConcreteLimiter_64.dll
P5: 1.0.1.64
P6: 4f1de4ce
P7: c0000005
P8: 000000000002bea4
P9: 
P10: 

Attached files:
C:\Users\brainstem\AppData\Local\Temp\WERA238.tmp.WERInternalMetadata.xml
C:\Users\brainstem\AppData\Local\Temp\WERAE01.tmp.appcompat.txt
triagedump.dmp
C:\Users\brainstem\AppData\Local\Temp\WERB074.tmp.WERDataCollectionFailure.txt

These files may be available here:
C:\Users\brainstem\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_SONARPDR.exe_96b698c4796ca208db24b37a6cad3f090d2e1bd_dacac975_0e30b5d0

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5f9a9b8b-6d21-11e3-826b-3085a99dee16
Report Status: 4104
Hashed bucket: 6b648f92c147738836119391d6a72e7f
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-12-25T04:59:51.000000000Z" />
    <EventRecordID>3327</EventRecordID>
    <Channel>Application</Channel>
    <Computer>lamia</Computer>
    <Security />
  </System>
  <EventData>
    <Data>150795621</Data>
    <Data>4</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>SONARPDR.exe</Data>
    <Data>20.0.4.278</Data>
    <Data>52abb061</Data>
    <Data>ProChannelConcreteLimiter_64.dll</Data>
    <Data>1.0.1.64</Data>
    <Data>4f1de4ce</Data>
    <Data>c0000005</Data>
    <Data>000000000002bea4</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
C:\Users\brainstem\AppData\Local\Temp\WERA238.tmp.WERInternalMetadata.xml
C:\Users\brainstem\AppData\Local\Temp\WERAE01.tmp.appcompat.txt
triagedump.dmp
C:\Users\brainstem\AppData\Local\Temp\WERB074.tmp.WERDataCollectionFailure.txt</Data>
    <Data>C:\Users\brainstem\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_SONARPDR.exe_96b698c4796ca208db24b37a6cad3f090d2e1bd_dacac975_0e30b5d0</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>5f9a9b8b-6d21-11e3-826b-3085a99dee16</Data>
    <Data>4104</Data>
    <Data>6b648f92c147738836119391d6a72e7f</Data>
  </EventData>
</Event>

ok - more data. I opened up another one of my projects that used to run in X2. Since the fault specifically mentions the concrete limiter (which I did not own until X3), I went ahead and added it to the master bus (just like I had on this failing project. I saved it, then closed and re-opened it. I clicked in the track window, then on a bus in the console and BOOM, crash.
 
But this time, the fault reporter actually popped up and asked to submit to cakewalk. I let it do that and pointed to this forum thread in the notes.
 
http://www.cakewalk.com/S...er=brainstem@gmail.com

So here is your smoking gun....
 
<Data>c:\program files\cakewalk\shared utilities\internal\ProChannelConcreteLimiter\ProChannelConcreteLimiter_64.dll</Data>
 
Same version as me...
 
Suggest deleting the concrete limiter in the tracks, bounce the tracks, delete the original tracks, saving project as a bundle file, closing, opening sonar, open bundle, save project, carry on.... And hope :)... 
 
Cheers...

I've had this issue too on X3c, for me it was the Console Emulator causing it. It seems a project can become "corrupted" this way. I had to remove all CE instances, save and then reopen the project. After that I could add them back. Which is ridiculous and completely unacceptable of course.
Yet another reason to avoid ProChannel.

Forum error / double post, but I'll say this before people jump in and defend Cake again; in my case it was just the CE and, since I mostly stay away from the level controls, removing those had just a small impact on my mix. So even though it took me a while to figure out was wrong and try to fix it, that was the only time I lost and could have been making music or mixing. This was thankfully a private project but I do do this for a living. In Jeebus' case, if the recommendation/solution is to remove all Concrete Limiters and PC4K gates, he can very nearly restart his mix.

Yes, I did send my own error report with notes (the one time out of five the error reporter actually worked) and even contacted Noel who was on vacation.

Just out of curiosity.....is your console  view undocked and floated to a second video screen?

Well the event viewer says it's the concrete limiter loud and clear.... and there must be a particular set of conditions causing it to crash looking at what already has been tried... ta

cuitlahac
Just out of curiosity.....is your console  view undocked and floated to a second video screen?

yes it is. I have it running in a dual monitor. When I get back from all the holiday festivities tonight, I will repeat my tests with it combined in the main window. Good test.
 
Just to make sure this thread doesn't go down that road, I'm not out to vilify cakewalk or **** and moan about things. I'm just trying to solve a problem. I've worked in IT for almost 15 years on some pretty huge, multi-million dollar software projects and have seen bugs and "necessary" workarounds that would make you want to vomit. This is relatively minor (albeit annoying) and I am able to get the job done, if necessary (save early, save often!).
 
I appreciate anyone's help.