Jim Roseberry
 
FWIW, It's relatively easy to disable/re-enable the over-clock.  That would allow you to quickly rule it in/out as a culprit.
 
All that said, running the 3930k at 4GHz isn't much of an over-clock... so I doubt that's the issue.

Thanks, Jim - I'll have a look whether I can located the switch where I could do this (might come back with questions, though)
 
 
BUT, I can't even reproduce that project corruption. As I tried to explain above, the project was saved at the end of the session (with playback stopped,so no CPU load), DAW shut down and when rebooted the next day, the project did no longer work.
 
When continuing off the last working project (saved about an hour prior to corrupted one), we worked an entire day without getting any issues - so no chance to reproduce on purpose; yet it's the 3rd project that doesn't open.
 
Interesting is the fact that none of the auto-saves from that one hour time period works i.e. the project may have been corrupted for a hour already but kept functioning while in memory ... boy, if I only could remember all that we did in that one hour (I remember pulling in some templates, changing some instrument tracks to audio+midi, ... but I did not focus on "tech" stuff, we're into the music ... )
 
 

Thanks...


Again please try this (even though your drivers may be up to date):
http://forum.cakewalk.com/Driver-Boost-m2928792.aspx
 
and please backup, remove and reinstall Sonar X3! I know it is a pain but you should try it :)
 
Also check this:
http://forum.cakewalk.com/Waves-Plugs-cause-error-msgs-in-Event-Viewer-m2734661.aspx
 
Bert you need to nail it down to the specifics.... My hunch is that your specific issue is when you are using Projects initially created in earlier Sonar versions.... this is really important to find out and I appreciate you cannot give an answer overnight:
 
Please can you confirm that projects created initially in Sonar X3 don't crash (that have been nowhere near earlier Sonar versions), and have you tried the cutting and pasting old projects into new projects as I explained earlier? Does this help?

if you use 32 bit auto tune with jbridge, make sure x3 didnt uncheck 'use jbridge' in the plug in properties... several corrupted files here

CakeAlexS
Again please try this (even though your drivers may be up to date):
http://forum.cakewalk.com/Driver-Boost-m2928792.aspx

 
i dont know, Alex. That looks a bit dangerous too me, until now I've known exactly when I installed what and why ... plus my DAW is not on the net ...
 

CakeAlexS 
and please backup, remove and reinstall Sonar X3! I know it is a pain but you should try it :)

 
This is a lot of work and I don't know what it does to my working version of X2a when it removes those common files ... can't try it this week anyway, next week earliest possibility - yet I need to think carefully about that ...
 

CakeAlexS
 
Also check this:
http://forum.cakewalk.com/Waves-Plugs-cause-error-msgs-in-Event-Viewer-m2734661.aspx

 
That was indeed helpful! Explaining that this message is rather irrelevant (and WAVES plug work fine) 
 

CakeAlexS
 
Bert you need to nail it down to the specifics.... My hunch is that your specific issue is when you are using Projects initially created in earlier Sonar versions.... this is really important to find out and I appreciate you cannot give an answer overnight:
 
Please can you confirm that projects created initially in Sonar X3 don't crash (that have been nowhere near earlier Sonar versions), and have you tried the cutting and pasting old projects into new projects as I explained earlier? Does this help?

 
I agree ... having similar feelings about projects (or parts of it) created in earlier Sonar versions - will try X3c only (but that will also take time ...)
 
 

> That looks a bit dangerous too me

That's what I thought initially, it isn't dangerous at all if you follow my specific instructions on that post, I've got it on all my windows machines. You can remove it if you like afterwards.


I did soooo many checks in the recent 2 weeks (drivers, updates for 3rd party software, memory, disk integrity, power options, viruses, malware, ... the list goes on). I can't think of anything else to check.


And you are off the net eh? When was the last time you ran Windows update or did a virus scan with latest engine and signatures? (Sorry just checking !!!). Suggest you get on the net LOL :).

Cheers...

For whatever its worth, I had a tune with a corruption. It would function, but with clicks and stops and starts, and the soft synths would be all crazy.
 
I tried all kinds of trouble shooting, including deleting plugs and clips and tracks one by one to see if I could locate the problem. The problem would not isolate. The backup copy had the same issues, it think because the problem existed when I backed up.
 
I ended up setting up a clean new project, and then I copied the audio tracks one by one, and then the MIDI tracks. Then I installed all the plugs again. This new version happily functions just like it should. I was a little angry I had to take this step, but in reality it went pretty fast.
 
But in the original somehow there is a built in problem that is unshakable.
 
I wish Sonar had the ability to make each track have a bounce to clips option that would have an event at the beginning of the song (especially MIDI tracks), so each track has a single full length clip, and then save the pristine audio and MIDI data as a very safe backup, with no other complexities.
 
Good luck with your problem.

Hay there...I tweaked my os to lean, and updated all my hardware drivers (as requested) in troubleshooting technique...and while in sonar x2a,b, then 3xb...I seen in them, while idle, with nothing on any tracks , no plugins, other than what gets loaded in sonar...spiking of cpu meters periodically...which was getting onto recorded tracks, and so the hunt for that buggy problem began...over 6 months!!
 
Now if you are overclocking...turning off "speedstep" In bois will not effect that overclocking processes of your setup!....if C1E is stated problematic, and VT on the cpu with audio/video software (specified by technicians of the higher ordered standard ilk) ...Then it is in your best interests to at least check that out, so it can be addressed before moving on in trouble shooting solutions/progressions...and running round in circles will not solve for....if it is not the cause, and the problem persist once turned off....you can turn them back on.....Never overlook variables I say!...and always check twice / thrice..and then recheck them settings over time to make sure ...I'm sure it will reduce cpu interrupts, and windows app that monitors the levels in which speed step is implemented to nil...gains better performance..as it has for me, and others who have done so... and all who use intel cpus with audio/ video software...should consider doing if it does cause problems....cost?...$0.00 + time
 
Blessings
Sir Les

Yup I don't recommend overclocking at all unless your PC is a dedicated Quake workstation, that's asking for trouble regardless who who might do it (unless that person can mind meld with chips like Spock with carbon silicon based lifeforms).

CakeAlexS
Yup I don't recommend overclocking at all unless your PC is a dedicated Quake workstation, that's asking for trouble regardless who who might do it (unless that person can mind meld with chips like Spock with carbon silicon based lifeforms).

Overclocking is an interesting topic.
 
Various studies by Microsoft (https://research.microsoft.com/pubs/144888/eurosys84-nightingale.pdf) have shown that overclocking is prone to errors.
 
It follows from common sense and all that, but I have a different opinion.
 
Every CPU has a tolerance, and the unlocked CPUs need to be tested to find their limits.
 
When I built my system I overclocked it to 4.8 GHz and ran various tests. The common ones are Prime95, Linnpack, Intel Burnin tools, and so on.
 
There were also stress tests by the motherboard manufacturer (ASUS) that were helpful.
 
Of course the cooling system is the most important thing here, so do the homework.
 
After several hours of test, and periodic tests over time, I concluded that 4.8 GHz was a bit too high. I never had errors, but the CPU temperature reached 80C. Supposedly, the Sandy Bridge would limit at 72C, but mine didn't seem to do that.
 
So from the start I chose 4.4 GHz as a compromise, and recently I backed it down to 4.3 GHz. (The BCLK overclock was 103% and I changed it to 100%, CPU clock unchanged). This was to remove a possible problem I was looking at. CPU temp of 70C is my limit.
 
As I write this, I am stress testing with 8 instances of Reaktor running a very complex ensemble. The CPU temp is 57C, and GUI performance is fine with no delays. I'm doing this test to verify some possible hardware problem. I will run this overnight. I see no delays or problems as I compose this posting.
 

 
Notice that all 8 cores are running evenly. In Windows 7 this was not so. In Windows 8 it was much better, more even, but still CPU 1 got hit the most.
In Windows 8.1 the thread and process distribution was very even, and everything seems to respond much smoother.
 
I am very impressed with 8.1 and wonder why so few others seem to jump on-board.
 
There are a few things that I find stressful. If I run Acronis image backup with maximum compression, I see very extreme temperatures when I do terabytes of backup.
 
But they work. I've restored several times due to inevitable problems and difficulties in debugging software issue.
 
I have never, ever, so far, "knock on wood", seen any hardware problems or things related to overclocking. But I do expect that someday, before its time, my system will die, so I am always vigilant.
 
But why overclock audio system? Most overclockers are gamers who want that extra detail.
 
For me it is Reaktor. I make a lot of Reaktor ensembles and use many long chains of processing elements. These take up enormous amounts of CPU.
 
Reaktor is not multiprocessor aware, so I have to split the processing among DAW tracks so that the other CPUs help out.
 
A while back I used Live as my DAW. I had Live 4, 5, 6, 7 and 8. Eventually, I needed 64-bit processing as my samples were needing more than the 32-bit address space allowed. Live 8 - 64-bit took a long time to happen with many, many bugs along the way.
 
So I went back to Cakewalk, the tool I used to use back in the DOS and Window 3.1 era.
 
It has a few MIDI channel assignment flaws that I overcome with Plogue Bidule.
 
Sonar X3c is very nice, but I think it still has a few thread flaws that cause problems.
 
We will see how this evolves.
 
 
 
 
 

Which proves my point really, if you are into tweaking sure give it a try. Do it yourself and be prepared to make adjustments yourself over time as you go along. If your friend overclocks your pc disable it, do it yourself. Or save yourself the agro.