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 ... )
 
 

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

> 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...

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

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.
 
 
 
 
 

Thermal degradation is a reality, plain and simple. High heat flux can delaminate layers, and this heat must travel to the surface edge of the core to dissipate. Overclocking is akin to throwing nitrous and supercharger on a 4-banger and wondering why it always needs maintenance.

This would be my system overclocked (a bit of a dog):

Nice one, Alex.

Hello - long time Cakewalk user here. I am hoping I still will be after this.....  I upgraded to the New version of SONAR X3 - Awesome!  then the couple upgrades since its release. I thinks its C now?  Anyways - everything worked great. Well Sunday Morning I also did a Windows update as I do not have it update automatically - I will manually do the update. Anyway, said there were a couple Important updates so I updated.  Well Sunday night I had my bass player over and I went to pull up some older recorded tracks that I recorded on SONAR X1 / SONAR X2.  Anyways,  I tried to open them in SONAR X3 (latest version) and it came up with an error and then SONAR was forced to shut down.  I think I saw a couple times saying somthing about corrupted files?  WHAT!?  This concerns me - there better not be any corrupted files - as they were not corrupted before.... I can not loose any of these files/tracks/songs. I am currently working on a project - well a couple projects.... and another project from a band. These files are not corrupted (atleast they better not be now!!!! - because they were not before,.... )  as I have opened them before many times never having any issue. The only thing that changed was the new SONAR X3 update and I did the Windows Update. So I thought - maybe its something wiggy with the new version of SONAR X3. I jumped on the Cakewalk forums lastnight and found other people having similar problems. However, it sounded like it was not clear if it was the new version of SONAR X3 or the New Windows updates.  Well,  I think it is the Windows updates.... Here is why,....  I still have SONAR X2 version on my computer - and I know I could open the files/songs in Sonar X2 as I had recorded them in that version and have opened them before with no problem.  Well,  guess what?   Same thing CRASH - SONAR X2  forced to close... So,  I am thinking it is not the new version of SONAR X3 with the issue as SONAR X2 should of opened the files with no problem. But, since SONAR X2 crashed also - I am thinking it is something to do with the new Windows updates....  Anybody else know - or have any news on this? CAKEWALK!?
 
P.S. I also started a new thread about this.

mettelus
LOL... I had liquid cooling... and it ruptured and blew the coolant all over the inside of my machine!! Rained all over my ASUS GTX580 dcii... but I am glad I bought a higher end 580 when I built the machine. I am also VERY glad I was sitting here when it happened... the computer started squealing but wouldn't shut itself off. Vacuumed and blew all the coolant out, waited 24 hours and brought it back online with copper pipes!
 
When I googled that coolant system, it had already been pulled because they were prone to ruptures... but most they ruptured on lost their machines.

This was one reason I did not go the liquid route. Even if the liquid caused no damage, there's very little thermal mass on the CPU if the pump fails. If the fan stops, at least there is still a massive copper heatsink attached.
 
But fans can have issues, too.
My wife had a graphics card that was mid-priced and had a small fan. One day the fan blades spun off the card and gouged out the motherboard!
 
 

Yup - there was NO need for the liquid cooling.  I just tossed it on in a flurry of giddy spending, as this was the most extreme computer I had ever built.
 
I do like how cool it does run, nonetheless, but for anybody considering a new computer, I would say get it if you have money left over and want it, but make sure you get all of the other stuff you want first, including things like upgrades to Melodyne, pizza, that new batch of Pineapple Express, whatever.  :)
 
Bob Bone
 

Now, I NEVER said I didn't LIKE it :)  I only said I didn't need it.
 
Now I got to get me a truck load of those fancy led case lights, and maybe some hydraulics, some new rims, and some fuzzy dice...
 
Bob Bone
 

i don't mind that you guys hijacked my thread as it makes really interesting reading :-)
 
as regards the original problem: cakewalk meanwhile contacted me to provide the crashing project, which i uploaded a few days ago - will keep you guys posted when I get a reply ...
 
meanwhile i will refrain from any further changes to the system because

• (A) there's a new thread almost every day now about a corrupted project or not functioning project in X3 (some of which were created with X2) and
• (B) my system has been really stable since X3c (no crashes while working) - there's just the fear that remains that the project won't open next time ...

 

(A) there's a new thread almost every day now about a corrupted project or not functioning project in X3 (some of which were created with X2)
 
And it's always a different reason, often away from Sonar.
 
There's just the fear that remains that the project won't open next time ...
 
That's why you should always keep up to date everytime you install new software (drivers http://forum.cakewalk.com..ver-Boost-m2928792.aspx
 firmware, windows update, sonar itself). Software by definition is unstable. 99% of the time updates make your system more stable (nowadays), and when (in the extreme occasion) it makes it worse you should always be in a position to roll back from a backup.
 
Glad it's working for you, if it happens again and Sonar does not find a reason please please disable your overclocking if only for a few months to see what happens...
 
Cheers...

OK rather than update your system and drivers etc I suggest mind melding with the CPU and software ;). Best do nothing! If it's broke don't fix it :)
I mean you can backup and roll back right?

The same things BTW have happened to me (often in fact) and I have always found solutions. And where upon I could recreate an issue ruling out third party possibilities I would log the issue with Cakewalk. Once (with X1C) I had to wait for X1D, after I could clearly reproduce an issue.
 
Actually I spent a whole day fixing instability with X3 when I installed it, it turned out to be third party drivers (something that wasn't happening with X2). You don't seem to even want to explore this possibility.


YES - I have dealt with corrupt projects and crashing in the past.
But what do I know :) I must be lazy ;)
 
(the reason why I have a stable system is because I get my hands dirty).