Next, he located the smartkey.dll file itself in the Windows System32 folder, where the error log indicated the conflict was sourcing from. It was an older version of the file, likely left over from a previous update. It was arguing with the newer runtime libraries.
Exception EAccessViolation in module smartkey.dll at 000A3B2F. Access violation at address 00456712. Read of address 00000000. ecm titanium smartkey.dll error windows 10
Search for a clean copy of smartkey.dll from your original installation media. Next, he located the smartkey