My Google friend knows nothing of the file name of this dll, either. The only hits were to this thread.
It's likely to be a leftover reg entry that is attempting to get the (now nonexistent) file to run. It seems likely your AV quarantined the file/s (looked in the quarantine?) but without tidying up the leftover, and in this case probably malicious, reg entry. The main point would seem to be that the file is now absent, the trojan cannot run without it. (Probably.)
Ccleaner has a reg cleaner that might find it, or if you know how to search the registry you could find it yourself.