Brando
 
Considering the sheer number of combinations possible, even a well built system can have conflicting issues and odd problems like this.  I do not experience problems in other DAW's on my PC and this one in Sonar occurs half the time and NEVER when loading in safemode.  It's also rock solid during operation.  I will never understand the software as well as Cakewalk and support from them is critical.  I've done a ton of troubleshooting before this point and rarely bother them.  
 
Was your last comment suggesting that cakewalk support should push back on me - maybe I misunderstood you.

I managed to pull an analysis of a sonar crash using OSR Online.  I thought the image and module name would provide a clue as to the crashing but its pointing to a *.tmp file that isn't there anymore.  I noticed the other crash dumps had similar messaged.  Can anyone / Cakewalk determine what the cause might be based on the below.
 

Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS
kernel32.dll version: 6.1.7601.19110 (win7sp1_gdr.151230-0600)
Machine Name:
Debug session time: Sat Jan 21 15:57:38.000 2017 (UTC - 5:00)
System Uptime: not available
Process Uptime: 0 days 0:01:25.000
  Kernel time: 0 days 0:00:07.000
  User time: 0 days 0:00:35.000
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2
TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2
*** WARNING: Unable to verify timestamp for Boost11_64.dll
*** ERROR: Module load completed but symbols could not be loaded for Boost11_64.dll
*** WARNING: Unable to verify timestamp for SONAR.exe
*** ERROR: Module load completed but symbols could not be loaded for SONAR.exe
*** WARNING: Unable to verify timestamp for AvidMbox_Asio64.dll
*** ERROR: Module load completed but symbols could not be loaded for AvidMbox_Asio64.dll
*** WARNING: Unable to verify timestamp for DeviceInterface.dll
*** ERROR: Module load completed but symbols could not be loaded for DeviceInterface.dll
*** WARNING: Unable to verify timestamp for mfc140u.dll
*** ERROR: Module load completed but symbols could not be loaded for mfc140u.dll
*** WARNING: Unable to verify timestamp for CWVideoEngine.dll
*** ERROR: Module load completed but symbols could not be loaded for CWVideoEngine.dll
*** WARNING: Unable to verify timestamp for play_VST_x64.dll
*** ERROR: Module load completed but symbols could not be loaded for play_VST_x64.dll
*** WARNING: Unable to verify timestamp for Ivory VST.dll
*** ERROR: Module load completed but symbols could not be loaded for Ivory VST.dll
*** WARNING: Unable to verify timestamp for Kontakt 5.dll
*** ERROR: Module load completed but symbols could not be loaded for Kontakt 5.dll
*** WARNING: Unable to verify timestamp for TDR Kotelnikov.dll
*** ERROR: Module load completed but symbols could not be loaded for TDR Kotelnikov.dll
*** WARNING: Unable to verify timestamp for iZotope Ozone 7.vst3
*** ERROR: Module load completed but symbols could not be loaded for iZotope Ozone 7.vst3
*** WARNING: Unable to verify timestamp for iZOzone7.dll
*** ERROR: Module load completed but symbols could not be loaded for iZOzone7.dll
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP: 
wwf6854+42166
00000003`006d2166 e8591aba27      call    00000003`28273bc4

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000003006d2166 (<unloaded_wwf6854.tmp>+0x0000000000042166)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 00000003006d2166
Attempt to execute non-executable address 00000003006d2166

DEFAULT_BUCKET_ID:  BAD_INSTRUCTION_PTR

PROCESS_NAME:  SONAR.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  00000003006d2166

WRITE_ADDRESS:  00000003006d2166 

FOLLOWUP_IP: 
wwf6854+42166
00000003`006d2166 e8591aba27      call    00000003`28273bc4

FAILED_INSTRUCTION_ADDRESS: 
wwf6854+42166
00000003`006d2166 e8591aba27      call    00000003`28273bc4

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

IP_MODULE_UNLOADED: 
wwf6854+42166
00000003`006d2166 e8591aba27      call    00000003`28273bc4

FAULTING_THREAD:  0000000000001268

PRIMARY_PROBLEM_CLASS:  BAD_INSTRUCTION_PTR

BUGCHECK_STR:  APPLICATION_FAULT_BAD_INSTRUCTION_PTR_SOFTWARE_NX_FAULT

LAST_CONTROL_TRANSFER:  from 0000000077200000 to 00000003006d2166

STACK_TEXT:  
00000002`64b5e460 00000000`77200000 : 00000000`00000000 00000000`00000000 00000000`00000004 00000000`000038ac : <unloaded_wwf6854.tmp>+0x42166
00000002`64b5e468 00000000`00000000 : 00000000`00000000 00000000`00000004 00000000`000038ac 00000003`006d2201 : kernel32!TestResourceDataMatchEntry  (kernel32+0x0)


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  wwf6854+42166

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: wwf6854

IMAGE_NAME:  wwf6854.tmp

DEBUG_FLR_IMAGE_TIMESTAMP:  56f912b0

STACK_COMMAND:  ~154s; .ecxr ; kb

FAILURE_BUCKET_ID:  BAD_INSTRUCTION_PTR_c0000005_wwf6854.tmp!Unloaded

BUCKET_ID:  X64_APPLICATION_FAULT_BAD_INSTRUCTION_PTR_SOFTWARE_NX_FAULT_BAD_IP_wwf6854+42166

Followup: MachineOwner

John
 
Is there a time I can schedule a call with support or a time to review this issue?  I have a lot of crashes logged and they all seemed to point to an access violation and that temp file referenced earlier.  Please advise if you can assist.
 
 
 
 

PMFJI, but I have just had a similar crash experience, that started out as screenery weirdness.
 
(I will say that except years ago, I have not had trouble with support. I am sorry you have. On the idea that CW should push back because people need to take more responsibility for their systems, I _sort of_ agree, but if the echoing silence is the response, that is wrong.)
 
I tried updating drivers one by one and the first I did was the video card's. The screenery went away, but SONAR kept crashing whenever I tried to _close_ it...ironic huh?
 
I asked for support and had a quick reply with some SONAR-based suggestions. I actually caved in and vented at Daniel in support about going back to an older version etc.
 
Then I found that with the new drivers, another video-heavy programme was also having trouble, crashing when I tried to close it.
 
I changed my video card and everything is fine.
 
I think my point is that it's far more likely to be drivers, that are often generically rude (they basically have to be), or other things like services running on your machine, than it is to be SONAR: as someone said, there are lots of combo's of gear and software and many thousand of people get on fine with SONAR. I would be looking at updating all drivers...one by one and trialing at each update. Then maybe disabling virus software and other background tasks. The fact that SONAR has always done this means that something in your system disagrees with SONAR.
 

Try opening in safe mode.
This is the first thing I tell anyone who is experiencing a crash of any kind.
If it is a plug in, you can eliminate the process by loading one at a time.
 
If doesn't open in safe mode, its either:
 
A- Bad soundcard
B- Driver conflict
C- Bad hardware.
 
 

I would suggest that you reset and rescan your vsts. The dump lists many plugs that can't load. This will rebuild sonar's plug database. 
 
Close sonar, shut down, cold boot. 

John
 
Please advise if you or someone from cakewalk can be available for a support call in the future on my crashing issue.  I have done a lot of the L2 type support but considering the random nature of my crashing on loading I will probably will need a subject matter expert to resolve this issue.
 
Thanks,

Why not simply try to work it out here ?
Don't get me wrong this forum is no substitute for support.
But your chances of getting a resolution here is possibly better than waiting for support to contact you.
 
As I mentioned in my previous post. try opening the project in "Safe mode".
This will give you a pretty clear indication if the problem is plug in related.
 
If the project wont open in safe mode, this is a pretty clear indication it might be your device / and or hardware related.
 
I understand your frustration but if you want help, we are here to try and assist you.
 

Well - it looked like an access violation from what I saw in the snippet of dump analysis pasted a couple of posts earlier. It showed this for the Exception Record:
 
ExceptionCode: c0000005 (Access violation)
 
And, as far as the observation that someone posted about a number of modules that couldn't load - the messages in the dump analysis text were talking about the series of PDB symbol files for the listed modules that it didn't have those symbol libraries available for the dump analysis program to use.
 
PDB symbol files, are used for mapoing the identifiers that you create in source files for classes, methods, and other code to the identifiers that are used in the compiled executables of the program - in this case the missing files listed in the dump analysis text are several from the various routines used in the source code for Sonar, and then there are also missing PDB files for various listed plugins.
 
IF one were to have those symbol files and provide the path to them to the dump analysis program, it could then give back more usable information on where the errors map back to in the source code.
 
NONE of those PDB files would be available to someone outside of technical support folks at Cakewalk, or the various makers of the plugins listed there, but the Sonar support folks would certainly have all of the ones needed to analyze a Sonar dump.
 
So anyways - there IS an Access Violation present, as shown in the exception record for the dump at hand, and an error like that used to a fairly common thing - when folks didn't have Windows maintenance up to date and were missing some set of C++ Run-Time Redistributable routines.  Other times, access violations could be caused by some sub-component needing to either be installed with, OR required to have Sonar launched with - the explicit Run As Administrator execution option.  PLEASE NOTE that Run As Administrator is NOT the same as running something using a Windows Account that is of type Adminitrator.  
 
So - somebody isn't happy with the ability to access instructions at the memory address listed in the dump.  Even without assistance from the Sonar folks - you could start reviewing exactly which plugins are loaded in the failing project, then load in Safe Mode and load one of those plugins at a time, until you see which one is loaded last when it fails again.  Then, look for any published info on that module and access violations and such - and MAYBE you can work past this.
 
If I can help you, I would be happy to try.
 
Bob Bone
 

Bob
 
Totally awesome, you confirmed what I thought.  I couldn't get the right analysis because only cakewalk (and the other companies) have the symbols.  I need them to analyze the dump fully (or give me the symbol library for my debugger).  Single process elimination would be the most logical way to solve a problem except mine doesn't give me the easy way out.  
 
All of my projects load in safe mode without issues 100% of the time!  When I first boot my PC for the day projects load without issue I'd say like 80% of the time normally, and then if I close and reopen any project, they tend to fail 50% of the time.  If I load in the same project that failed right afterwards in safemode, tabbing through the plugins it works without issue.  With this scenario, there's no way to point to anything specifically.  Part me wonders if the hardware is holding onto something causing these issues (mbox3, yamaha NU1, impulse novation, ilok are my usb devices) but I can't be sure.  When sonar crashes SONARPRO.EXE hangs around in the process manager for a few minutes.  No amount of command line process ending works to kill it or its child processes. On the bright side, the system runs rock solid for 12+ hour straight with a project open pushing my skylake i7 to its limit with the process of occupying 50 of 64GB of active RAM.  PC doesn't BSOD for issues either, it's just a crash to the desktop.
 
At this point I'd have to eliminate every dll one by one, then go through track instances (since without a reliable crash point I can reproduce, I can't eliminate anything), then the hardware. At that point its almost easier to rebuild the entire box from scratch. You know how much it takes to set one of these up even if done in an organized logical way. 
 
My system runs without issue when up and considering I don't switch between projects that often, do I risk messing the whole thing up to fix this problem?  I was hoping Cakewalk could do a dump analysis and maybe give me some indication (could be something stupid like the USB port fighting with Sonar, or some 3rd party DLL I thought I removed somewhere) of where this issue is.
 
I still hope I get that dump analysis, but until then I keep looking.  Given this situation I'm open to alternative approaches, any other thoughts would be appreciated!