SCS crash on opening [and SOLVED - sort of]

General topics regarding SCS
Post Reply
David Longmuir
Posts: 3
Joined: Sat Oct 11, 2008 4:38 pm
Location: Coramba, Australia

SCS crash on opening [and SOLVED - sort of]

Post by David Longmuir » Wed Feb 14, 2018 2:57 pm

I have just installed SCS (11.7.0 RC6) on my brand new computer. When I tried to run SCS for the first time I was surprised to find that it crashed, just after loading the splash screen. Surprising because it had never happened before and I have always found SCS to to be very stable.

Checking the fault log, the faulting module name is C:\Program Files\Avid\Pro Tools\CFnd.dll

Looking around the webs, it seems that a similar problem can occur in Wavelab and Vegas (I don't have either). I tried the Vegas solution which is to rename CFnd.dll so as to "hide" it from SCS. And it works! With no CFnd.dll around, SCS now runs just fine. If I want to use Pro Tools I, obviously, have to re-name the DLL to make it available once more.

I suspect that there might be a deeper problem at work and will continue to try and work out what might be wrong with the way my computer is set up.

In the meantime I hope this might be of interest/use...

Kindest regards,

David


SCS Event Log.PNG
SCS Event Log.PNG (24.17 KiB) Viewed 377 times

Mike Daniell
Site Admin
Posts: 3630
Joined: Sun Jul 24, 2005 8:58 am
Location: Brisbane, Queensland, Australia. TZ:GMT+10
Contact:

Re: SCS crash on opening [and SOLVED - sort of]

Post by Mike Daniell » Wed Feb 14, 2018 7:53 pm

SCS does not directly call CFnd.dll and I'm not aware of any subsidiary process that would do so. However, I suspect the fail is occurring on trying to initialize an ASIO driver. I tried to email you with details of a tracing version to run, but the email bounced.
Mike Daniell
Show Cue Systems Pty Ltd
mike@showcuesystems.com
Image

David Longmuir
Posts: 3
Joined: Sat Oct 11, 2008 4:38 pm
Location: Coramba, Australia

Re: SCS crash on opening [and SOLVED - sort of]

Post by David Longmuir » Sat Mar 02, 2019 2:14 pm

Just following up on this I think I might have come across a more permananent solution at https://www.steinberg.net/forums/viewtopic.php?t=119096

I have used HomePlayer's procedure and removed digiasio.dll from the \System32 folder and kept the file of the same name in the \SysWOW64 folder.

"I guess I have found a solution (at least a workaround).
As was mentioned by MadMusicologist the problem seems to be the digiasio.dll file.
I followed his hints but it didn't help.
What I did:
I renamed the digiasio.dll in the System32-folder to digiasio.dll.orig (just to have it available in case anything goes wrong) but let the one in SysWOW64 untouched (this is the version with the 2015 datestamp).
Now wavelab does not crash anymore when I close it and ProTools 2018.10 is also working .
Hope this helps.amed OLD file has been replaced by a copy of the newer digiasio.dll file from WINDOWS\SYSTEM32\"

In my case, I can now either open SCS or Pro Tools (v 12.7.0) without having to first disable/enable any DLLs - yay!

(And CFnd.dll can stay untouched in the C:\Program Files\Avid\Pro Tools\ folder.)

:D

Post Reply