• SONAR
  • How would you troubleshoot this crash?
2018/01/31 22:18:55
jimo
I have a project that, if it is the first project I open for day it opens fine, if I try to open it AFTER working on another project it crashes with C000005 error. If I close SPLAT completely after the crash I am able to open it fine. Would you start by disabling plugins to see if that makes a difference? And even if I did narrow it down to a specific plugin problem what would be the cause. thanks for the help. -Jim
2018/01/31 22:25:26
CakeAlexSHere
Post the full error from the windows event viewer.
Ta.
2018/01/31 22:28:27
jimo
OK I will have to do it later when I get home. When I looked at it before it pointed to TH3 but I removed that and it still happened. 
2018/01/31 22:42:47
CakeAlexSHere
If it pointed to TH3 and you removed it.. and still happened.. either it does not point to TH3 or TH3 is still there. Regardless make sure you are on latest TH3 version..

In case you aren't aware...
https://overloud.com/news...mes-cakewalk-customers
2018/02/02 18:34:00
jimo
The last time this happened (yesterday) there was no error in the event viewer. I just have a screenshot of the C000005 error window and the minidump file. Anything else to check? thanks
2018/02/02 18:35:57
sharke
I have a similar (but opposite) problem with a few projects - they always crash if it's the first project I try to load after booting my computer. I've kind of gotten used to the routine - load the project fully expecting it to crash, close down Sonar, load again successfully. Never worked out what causes it. 
2018/02/02 19:03:31
jimo
Interesting. One thing I also noticed (which won't really help with your problem unfortunately) is that if I am working on a project and then want to work on the project that I know will crash - if I close Sonar completely and then open it back up and open the offending project, it will open fine without crashing. As if there was something being held in memory that conflicts with the "problem" project. 
2018/02/02 19:10:22
SonicExplorer
That's an access violation error code.  Often due to bad pointer programming, internal to some piece of software.  Finding the cause can be very difficult without an in-depth understanding of things and a kernel debugger.  From the typical user perspective it really comes down to trial and error, and investigation to narrow down what piece of software/driver/plug-in, etc may be the cause, or what sequence is causing the issue.  Sadly, most of the time these errors are not "fixable" per-se, rather can often only be 'resolved' by eliminating or updating the problematic component, or by changing the sequence of events that caused the problem. 

Sonic
2018/02/03 01:39:07
fitzj
Go to windows  folder  and  look for the folder Minidumps.
Inside look for the latest.dmp
Upload to the following website and it should tell you which driver or module failed.
http://www.osronline.com/page.cfm?name=Analyze
2018/02/04 02:51:12
e0012455
A way to check the plug-ins is to hold down the shift key and then open the project. It will cycle through each plug-in, once you know the plugin name answer no to loading it.
12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account