artzig

The file/s look suspect even just down to their pathname. If it was me I'd run a simple disk check first with a 'no fix' option to see if there's signs of hard disk corruption (the echoing pathname is sometimes a sign of this) without changing anything. If that is clear try renaming the DLLs and see what happens. Have a look at the old sysinternals.com tools now under the umbrella of MS for some simple but effective tools to try to see what's going on. Virsustotal is a useful site but I have known it generate false positives for some benign files. I got a JPG file, copied and pasted in about 200bytes of a benign EXE file into the front of it and sent it to VT to see what it would make of it. It came up 4/45 infected and with differing names. Obviously if there's enough 'random' data there if going to be able to make something out of it at some point.