Umm... how did the OP comment of "While rendering, sample converting or a few other operations, if the software has to 'think' or work to hard, it freezes (not responding) never to return...I have waited literally for hours. Not the computer, just the software, all other functions of the PC are stable and functioning during these episodes." lead here?
 
Unless I misconstrued the OP, I read that as X3c is hanging (not the entire machine) during rendering operations and "browsing through the drum samples." An interface issue should affect the entire machine, and a hang like this is easily replicated with extreme adjustments to buffers.
 
It would help the OP a lot more to provide feedback to their issue as directly as possible.

Yup totally agree mettelus. The operating system was not crashing.
 
Check Event viewer and what you say about the buffers is entirely valid as well.
 
Updating drivers (and even firmware) could be valid as well but would be nice to get feedback first.

Sonar X3c crashing...was the title of the thread I posted in here...no?
 

Why is wait state in progress?= hanging command or poll to process...not implemented right? or is waiting for something to stop using the cpu....something holding on to cpu cycles?...and then the path widens to this...thought.... without X..... takes many forms to address!....agree or disagree on what it could be...when what it is is held out of view.....one thing is for certain...it ain't working right..

What is happening?...Software, hardward, and system, are being used...One of these things is failing to do something the other wants done...is it software, hardware, driver, system?....
 
Proper installation of Sonar software, and others request to my knowledge = "turn off virus protection"  if being used when doing so, so as to not corrupt the installation....MOSTLY the reasons for the misdirection of the thread to security software UAC being turned off...all of it might be extreme, but also might be a overlooked path to a corruption....remove Sonar software that may have been affected if it was installed while virus scanner were running....IF it was ....,uninstall, reinstall SONAR without virus protection or any other security protection programs running.....and see what happens.
Just a guess....this could also include Drivers and bug fixes...turning off the security protection when installing from known distributors...is usually safe enough....
So turn them all off...When installing ...Scan them first...if you need to...but turn them off when installing....MS essential, Defender, and or others...which I include UAC....SO it could be corruption of the software,...and it could be Buffers...could be a lot of things...Not saying no to anything...but I will not overlook anything until we have X info from the Joyof60
 
And so that is how it comes to this....without X it is a crap shoot.
 Some call it brain storming....before the sun comes up.
 
Wink.
 
 

Oh and also if security software is on when using Sonar.. "Rendering" is a write function to a drive...Security will detect it...and could cause issues.
 
So...it comes to this because it is mentioned in the OP...and so the thought process on it  is mead....LOL
 
Just trying to keep things in good spirits...
 
Sir Les

A simple fix to a few little problems has been to delete (or rename) the existing Aud.ini file
 
Sonar will build a new one the next time the program is launched.

 Hay Bristol Jonesey,  Where is that Aud.ini file located?...and what is written poorly in the original one, and or why, to need to renew it?..or can you explain more as to why one would or should...
 
I was unaware of this work around....and I still got issues...and have sent several reports now.
 
Thanks

Hi Les.
 
You'll find it here:
 
C:\Users\Your User Name\AppData\Roaming\Cakewalk\SONAR X3 Producer
 
You might need to ensure that hidden and/or system files are visible in Windows Explorer
 
 

AUD.INI is where your Sonar settings are kept.
Bare in mind you should keep a record of your Sonar settings in preferences, or better still just rename the file to keep a record.
 
Four reasons to do this:
 
* File got corrupted.
* Your cakewalk settings are invalid (maybe down to an upgrade script going wrong or something) and it's best to start again.
* You wanna see if it makes any difference in a crashing app scenario.
* Fancy a cleanup.
 
So yes a dodgy AUD.INI could be the cause of crashes as well, nicely pointed out...