- #Protools 12 shutdown drivers#
- #Protools 12 shutdown driver#
- #Protools 12 shutdown pro#
- #Protools 12 shutdown code#
I probably has no bearing but its best to uninstall it if you aren't using it. This looks like something from Creative labs. BTW you have another ASIO dll being loaded ctasio64.dll. This is something only Avid can look into since I don't have any further info. Finally shortly afterwards it crashes in CFnd.dll.
#Protools 12 shutdown pro#
You can see that the digiasio.dll gets loaded first and several other Pro tools dll's then load as a result. 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. The reason the DLL is loaded is because they are exposing this as a standard ASIO DLL. 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 crash occurs on a thread from CFnd.dll so the crash is not in response from a direct call from Cakewalk. This means the DLL is accessing a null pointer. Maybe by tomorrow night we will know more, when I hopefully receive the analysis of the mini dump files. 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. If the problem goes away, that tells you it's definitely being caused by the ASIO driver.
#Protools 12 shutdown driver#
bitflipper Afterthought: try using a different driver for SONAR/CbB. In my config, Cakewalk uses the ASIO driver from my soundcard.
#Protools 12 shutdown drivers#
First place I'd look is that driver's dependencies, as well as those of other audio-related drivers (there may be many). My understanding is that PT installs its own ASIO driver.
#Protools 12 shutdown code#
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. 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. 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. Please, I'd love so much to have both DAWs on one computer.īitflipper Interesting that the thread is almost a year old and no resolution was ever posted. Since this does not seem to be the case with my system, the cause for the issue must be somewhere else. I saw there is a thread with complaints that ProTools Ultimate 2018.4 (which I am running without problems) was crashing upon launch. I have contacted of course both Cakewalk support and AVID support, sent the mini dump file to them, but might not have an answer before Monday evening. Strange is that I NEVER run ProTools and Cakewalk simultaneously.īut they share some plugins (which have, for ProTools. I notice that the causing file is a core file for AVID applications, so I better do not mess around with it.
Please see the screenshot, then you'll change your mind. Up to here, ProTools readers might say I am wrong in this forum. Then I have a pop up telling me something about an unforeseen error which caused Cakewalk to shut down. When I launch a project in Cakewalk Sonar (either "old" version or "new" by Bandlab), the DAW shuts down before I can really do something. Conflict between ProTools and Cakewalk Sonar