joyof60
I've never used anything but th X3c, and yes it's new projects. Usually playing with session drummer or SI drs when it stops responding. I really hate to keep bothering y'all with this problem. I might get something from cakewalk tech that may help. If so I'll post it here for others! Thanks guys so much!!

20.0.1.209 is not the X3c patch. 
 
You'll need to apply X3c separately:  http://www.cakewalk.com/Support/kb/reader.aspx/2007013331

Ok, now I'm really puzzled, on my initial install I went through the process of downloading and installing a,b, and c in that order and with the recent uninstall and reinstall I did the same. My help/about states X3c. I never used a orb, frankly didn't see the sense when c was available. So if I got a patch that is not X3c what does that mean. Sorry but I've been away at work and am not at my DAW now. But I'll quadruple check. (Already triple checked)

You don't need any other patches. Just install X3C straight away.
Just reinstall X3C and see what happens (don't worry about it).
After that RESET your VST plugins then scan.
 
Cheers...
 

[image]C:\Users\Jams\Pictures[/image]
I will reintsall

Hope I'm doing this right. Things have been functional for some time now, occasional crashes continued but nothing I couldn't grin and bear. Alas, now sonar crashes each time I simply try to organize a template. I copied the application error, kinda fuzzy on exactly which one gave anybody information needed to assist.
any ideas again would be great!
 
Thanks in advance for any help!
 
 
 
Log Name:      Application
Source:        Application Error
Date:          8/29/2014 6:43:12 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Jams-PC
Description:
Faulting application name: SONARX3.exe, version: 20.0.5.244, time stamp: 0x5314d61d
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace4e7
Exception code: 0xc0000417
Fault offset: 0x00000000000552d4
Faulting process id: 0x1fa4
Faulting application start time: 0x01cfc3e0fed47a85
Faulting application path: C:\Program Files\Cakewalk\SONAR X3\SONARX3.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll
Report Id: 3c745de3-2fd6-11e4-8174-3085a98e9788
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="2014-08-29T23:43:12.000000000Z" />
    <EventRecordID>23891</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Jams-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SONARX3.exe</Data>
    <Data>20.0.5.244</Data>
    <Data>5314d61d</Data>
    <Data>MSVCR90.dll</Data>
    <Data>9.0.30729.6161</Data>
    <Data>4dace4e7</Data>
    <Data>c0000417</Data>
    <Data>00000000000552d4</Data>
    <Data>1fa4</Data>
    <Data>01cfc3e0fed47a85</Data>
    <Data>C:\Program Files\Cakewalk\SONAR X3\SONARX3.exe</Data>
    <Data>C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll</Data>
    <Data>3c745de3-2fd6-11e4-8174-3085a98e9788</Data>
  </EventData>
</Event>

I can't tell if build 244 is X3e. The build number seems low for X3e compared to Producer. If not, apply the X3e update. To determine if build 244 is X3e, open the about screen, midway in the screen should be an indication of the update and build.

It is indeed X3e, I have updated any item that I can find, Not much was out of date, all the drivers proclaim to be the most recent available as well.....I thought something might show up in the event log. I dunno what all that means. Maybe I'll try the Bakers line in the morning. Thanks so much for the reply. really do 'preciate ya!

I have not gone through this whole thread - it is 4 pages, and started in 2013.  I WILL do so, just have not done so as of yet.
 
I DID do a quick search on the following Google terms: 
 
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace4e7
Exception code: 0xc0000417
Fault offset: 0x00000000000552d4
 
Just to see if there were other applications reporting this same error, and YES there were.
 
I suggest you search using the above terms, and wade through some of the results, to see if anything rings a bell.
 
The first link I looked at suggested some kind of issue with multiple things going after the same drivers, and this can happen in Sonar if you are using ASIO driver mode and the Windows Default Audio Device is also set to the same ASIO drivers, AND something in Windows outside of Sonar initiates a call to the ASIO drivers in Windows - like Windows sounds, or starting Windows Media Player, that kind of thing.
 
Anyways, take a look through those search results, and please post back - I wil try to find some more time in an hour or two to do the same.  I have to chase down a different issue at the moment, first.
 
Bob Bone
 
 

Thanks Bob,
I have waded through a google search of the above stated terms and really don't see any thing that is common other than the module being at 'fault'.  Last time this resolved to an extent with a reinstall of sonar. Thus resulting in sonar becoming intermittently 'non-responsive' from time to time but not totally crashing and losing my work which is the case now.
This thread is indeed beleaguered with discussion and rants about non related issues, and I do apologize for that but alas, not of my doing.
Thanks so much for any help at all in resolving this issue.
Keith

Do a search on MSVCR90.dll, and you'll find plenty of problems that sound like yours. Maybe it's a Visual C++ component issue?
 
This thread is interesting because it relates to audio file conflicts - the problem was resolved for one person by uninstalling QuickTime. Go to the end of this thread, and it covers dealing with C++ issues. There were some other threads that mentioned incompatible plug-ins. I don't know enough to comment on any of the solutions that were presented, but it seems you are not alone in the world of "Faulting module name: MSVCR90.dll."
 
I can't help but wonder if problems that are solved by re-installing Sonar don't have to do with Sonar, but with re-installing the files that are installed with Sonar.