Conflict between ProTools and Cakewalk Sonar

The only suggestion I can think of is to change the name to CFnd.dlx before you want to use Sonar or CbB and then maybe it will be ignored. Change the name back to CFnd.dll when you want to use Pro Tools. I can't guarantee this will work but is worth a try.
 
FWIW one day, my pre-subscription version of Pro Tools was working. After a Windows update, it would no longer open. I decided I didn't need it enough to get the subscription, but I downloaded the free version so I could take some screenshots for a book. It put tons of stuff on my hard drive...I'm considering uninstalling it. I think Avid assumes that you're running a dedicated Pro Tools computer.

tnipe
I've been running both for a while now. I used to have that error or something very similar. It doesn't happen anymore, and I don't know what fixed it. But my point is that it works to have both installed. Have you tried ending the Avid application manager process before opening Sonar? Might be worth a shot.

That's a fine idea, I will try. BTW, the friends in the ProTools forum suggested I should run Cakewalk as admin. That was helpful.
But it really might be that the application manager is the thing I should prevent to be in autostart. It should only be active if I either launch it directly, or I launch any AVID application.
I will try that tomorrow.
But thankx for the cool idea. 

Hi Noel, 
that article says the conflict might be caused by Quicktime for Windows, I deinstalled all Quicktime, Apple for Windows-software which I had been running on this PC.
Tried "normal" launch of my Cakewalk project, it crashed again: not directly upon launch, but after half a minute.
When the crash occurred, I had been in playback. Even 15 seconds after the crash (Cakewalk had already disappeared from the screen) I still heard some fragments of the project I had been playing back. Weird. A ghost is playing inside my PC. ;-) Do I have to call in the "Men in Black",  or preferrably the Ghostbusters?

If you read the thread CFnd stands for Core Foundation which seems to be some cross platform abstraction layer they are using. My guess is that they are either installing a custom ASIO driver or its a shell extension or service that gets invoked during Cakewalk (and other DAW) start up.

bitflipper
Interesting that the thread is almost a year old and no resolution was ever posted.

Weird. If AVID has knowledge of the issue, how come they miss solving it?

bitflipper
It shouldn't be that difficult to find out who's calling the DLL. It's got to be something the two DAWs have in common, most likely a driver, and it most likely says "Avid" in its file properties. Avid says the ASIO driver does not load it, but they probably determined that by looking at the source code and could have missed the reference if it's an indirect dependency.
 
My understanding is that PT installs its own ASIO driver. First place I'd look is that driver's dependencies, as well as those of other audio-related drivers (there may be many). 

In my config, Cakewalk uses the ASIO driver from my soundcard.
I'd have to see which one PT is using.

bitflipper 
Afterthought: try using a different driver for SONAR/CbB. The safest one for testing would be MME. If the problem goes away, that tells you it's definitely being caused by the ASIO driver. 

Didn't I once read for some reasons I do not recall anymore, MME is not optimal choice? 
But I will give that a try tomorrow.

Thankx for coming in on that issue. Maybe by tomorrow night we will know more, when I hopefully receive the analysis of the mini dump files.

Here is what I got from the dumps you sent (thanks):
 
Unhandled exception at 0x000000000ABE5F5A (CFnd.dll) in Silkroad_07082018_070006.dmp: 0xC0000005: Access violation reading location 0x0000000000000000.
This means the DLL is accessing a null pointer.
 
The crash occurs on a thread from CFnd.dll so the crash is not in response from a direct call from Cakewalk.
15824 0 Worker Thread ntdll.dll thread CFnd.dll!000000000abe5f5a
 
I'm pretty sure that this is directly in response to the digiasio.dll being loaded because CFnd.dll is loaded soon after digiasio.dll is loaded when Cakewalk starts up. The reason the DLL is loaded is because they are exposing this as a standard ASIO DLL. If they don't want it loaded they shouldn't be exposing an ASIO device for public consumption :)
 
Below is the logged info I get from the dump. You can see that the digiasio.dll gets loaded first and several other Pro tools dll's then load as a result. Finally shortly afterwards it crashes in CFnd.dll. This is something only Avid can look into since I don't have any further info.
 
BTW you have another ASIO dll being loaded ctasio64.dll. This looks like something from Creative labs. I probably has no bearing but its best to uninstall it if you aren't using it.
 
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*c:\Windows\System32\digiasio.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\DirectIO.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\DSI.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\DigiPlatformSupport.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\DHS.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\CFnd.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded 'C:\Windows\System32\IPHLPAPI.DLL'. Cannot find or open the PDB file.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded 'C:\Windows\System32\mpr.dll'. Cannot find or open the PDB file.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded 'C:\Windows\System32\msi.dll'. Cannot find or open the PDB file.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded 'C:\Windows\System32\dbghelp.dll'. Cannot find or open the PDB file.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Windows\System32\urlmon.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Windows\System32\iertutil.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\AFnd.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\DFW.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\Avicuuc42.dll'. Module was built without symbols.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\Avicuin42.dll'. Module was built without symbols.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\DFW_KeyHook.dll'. No matching binary found.
'Silkroad_07082018_070006.dmp' (Minidump): Loaded '*C:\Program Files\Avid\Pro Tools\Avicudt42.dll'. Module was built without symbols.
 
Unhandled exception at 0x000000000ABE5F5A (CFnd.dll) in Silkroad_07082018_070006.dmp: 0xC0000005: Access violation reading location 0x0000000000000000.

Thanks for sharing, Noel.
 
Maybe PT has a nefarious internal function named KillEveryOtherDAW()?
 
OK, bear with my conspiracy-theory logic...they could have resolved the ticket in an hour, couple days, max. But no follow-up post, no announcement of a bug fix.
 
Maybe, just maybe, they found (or already knew about) the problem and just kept quiet?
 
BTW, NASA knows about this too, which is why nobody can go to the South Pole.