MME isn’t optimal for latency (quite the opposite), but switching to it as a fault-finding measure might indicate if the problem is somewhere in the ASIO side of things. If switching Sonar to MME makes the crash go away then that points to the offending .dll being something accessed by Sonar as part of the ASIO environment.

It might be worth trying Sonar in wasapi driver mode as well, if preferences includes that option. If that makes the problem go away then wasapi can produce latency results very similar to ASIO and using it might just solve the problem.

Renaming the offending .dll as has been suggested is definitely worth a try. If Sonar loads and functions correctly then other than changing the dll’s name back to run PT the problem is as solved as it can be unless a permanent fix comes along. Then again, that might just result in Sonar complaining if can’t find the dll.....

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.

I bet renaming digiasio.dll will mask the problem.
 

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.

Noel Borthwick [Cakewalk]
I bet renaming digiasio.dll will mask the problem.
 

Thanks for your posts, Noel, brillant.
I shall put that all in the thread I have with AVID.
Of course I can try out renaming that digiasio.dll, first I'd have to see the properties:
Years ago, when ProTools was made by Digidesign, I had an LE version which I abandoned (Cakewalk Sonar was way better then!) but never deinstalled from my PC. 
I turned back to PT as alternative DAW when there was the "Gibson Crash" and it was unclear what youd happen to Cakewalk after that. At that time of course I deinstalled the old PT version. But I am not sure if I did that only after installing the new PT version and some how that old dll "survived" on my PC. I'll check that tonight...
If that dll is older than2 years, I will even try to delete it, start PT, and if that works, I will shred it from my bin.
Sure I will tell here, and there. 
Thankx again.
 
(in the evening...)
Searching my PC for that file, I found 2 of them with identical name but different ages (one of 2015, the other one from April 2018), and in different locations.
I deleted the older one and first tried to open ProTools, and a session there. No problem encountered. 
Now I opened Cakewalk, NOT as admin, - - - NO PROBLEMS ANYMORE! Yay! 
But I shall watch this....
Posted the result in the quoted Steinberg thread, maybe that helps.
Now I am going to shred that bad file from my bin. Rest in pieces.