• SONAR
  • Isolating causes for Sonar Crashes
2014/10/16 08:25:41
ReTracer
Hi,
 
I wondered if there's a checklist/procedure for discovering the cause of random crashes that have started to occur in my version of Sonar? It's doing my head in. I've got a project at the moment which involves playing a very exhausting classical work which takes a lot out of me, and once I get back to the computer it's a crushing blow to find that Sonar has frozen and lost everything. It's been happening for a couple of weeks and now I'm finding the stress of it is affecting my ability to play.
 
I've found that it sometimes crashes even when sitting there doing nothing, and I have a managed to grab one minidump that was saved on one crash by Sonar. Most of the time it crashes without any recourse for further information.
 
As I'm using Sonar 8.5 still, the current 'support' from Cakewalk is non-existent (it's not an option on their support form).
 
Any advice gratefully received.
 
Sonar 8.5 Producer
Windows 7 Home Premium
Intel(R) Core(TM) i7-3630QM CPU @ 2.40 Ghz
RAM: 16 GB
64-bit Operating System
 
K
2014/10/16 08:32:45
FastBikerBoy
Random crashes are always hard to pin down. If you have a lot of FX in it, especially third party, I would start by loading the project in "Safe Mode" (Hold down the shift key while opening). If it then loads and runs okay at least you then know it is an FX of some sort.
 
The trick is then to work out which one and that is a matter or trial and error. Perhaps load half of them and see what happens. The problem will either be in the first half of the FX or not. Doesn't matter if it is or isn't you've halved the search area already. Repeat that process with half of the suspect half (i.e. 25% of the plugins). Keep repeating that process until you've narrowed it down to one.
 
Of course if it isn't a plugin at least you've eliminated those but in my experience that's where I'd start.
2014/10/16 08:38:45
ReTracer
Thanks FBB, no, it's not plugins - this is a straight MIDI recording using a Roland V-Piano. There are thousands of notes, and the pedal pumps in a lot of data too. But it should be a doddle for Sonar to handle.
 
I will try the safe mode tip, thanks for that!
2014/10/16 08:39:22
Splat
Have you checked the windows event viewer?
Might be good to paste the error here.
 
Also in case you are considering upgrading:
http://www.store.cakewalk.com/b2cus/category.aspx?categoryID=9
 
In general it is good to get up to a base system then resume further troubleshooting:
 
1) Update the chipset drivers and firmware of your motherboard. Google Intel driver update utility.
2) Update the display drivers of your display adapter from their third party site (what is the make and model?).
3) Update the firmware and driver of your audio interface (please supply details here).
4) Run windows update several times, and check the optional updates.
5) Make sure Sonar is on 8.5.3
6) Defrag.
7) After that check latencymon for further clues.
 
Also look out for per project crashes (i.e. plugin issues)...
 
Cheers...
2014/10/16 08:53:28
Wookiee
The other thought that springs to mind is "What was the last thing I changed before this started happening" undo that change and work back from there.  Hope you resolve your problem soon.
2014/10/16 09:01:36
ReTracer
Thanks Alex, lots to follow up here.
The motherboard chipset reports no updates
Graphics NVIDIA GeForce GTX 670MX 9.18.13.4411 - possible update required there although this one is September 9
 
Audio interface - currently connecting straight from the piano through to the computer via the piano's USB. My external soundcard (M-Audio Firewire 410) is not connected. Onboard audio is
 
Realtek High Definition Audio
Driver 6.0.1.6662
Date 19/06/2012
 
Windows reports that it is 'up to date' though I'll browse for the manufacturer's site.
 
Now I have to get my head around the event viewer.
 
Thank you.
 
K
 
2014/10/16 09:05:05
ReTracer
Wookiee - wish I knew. It happened once, I was away from the studio on other projects for several days, it didn't happen, then it did. Hard to pinpoint by memory what aspect was changed in the periods inbetween. Windows update? The V-Piano's USB? I can try using my other set up for a while (same computer) and see if the crashes continue - if not, it's the V-Piano.
 
2014/10/16 09:07:41
Beagle
ReTracer
Thanks Alex, lots to follow up here.
The motherboard chipset reports no updates
Graphics NVIDIA GeForce GTX 670MX 9.18.13.4411 - possible update required there although this one is September 9
 
Audio interface - currently connecting straight from the piano through to the computer via the piano's USB. My external soundcard (M-Audio Firewire 410) is not connected. Onboard audio is
 
Realtek High Definition Audio
Driver 6.0.1.6662
Date 19/06/2012
 
Windows reports that it is 'up to date' though I'll browse for the manufacturer's site.
 
Now I have to get my head around the event viewer.
 
Thank you.
 
K
 


It might be the soundcard drivers causing your problem.  try using the M-audio FW410 instead.
2014/10/16 09:16:13
ReTracer
Would that be the case? As i'm not using any audio data on the project - I can run it even with the audio engine switched off - would it matter at all which soundcard is being used? Or does Sonar use the audio card for other tasks, such as timecode etc. Sorry for my ignorance here.
2014/10/16 09:17:05
Brando
ReTracer
Audio interface - currently connecting straight from the piano through to the computer via the piano's USB. My external soundcard (M-Audio Firewire 410) is not connected. Onboard audio is
 
Realtek High Definition Audio
Driver 6.0.1.6662
Date 19/06/2012
 
Windows reports that it is 'up to date' though I'll browse for the manufacturer's site.

Your Realtek is definitely the weakest link. What drivers? Why not hook up the m audio? I would deselect Realtek in sonar, use the m audio and make sure  you don't have asio4all installed etc
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account