Solved sfc /scannow corrupt files unable to fix - Log attached

[quick215]

Hi (tom982 or anyone else that can help),

So amidst some recent BSOD problems that were resolved with uninstalling BitDefender AV, I had run the sfc check and had it fail. As I fixed the BSOD, I let the sfc fail slide. Well, now I am trying to install a Samsung EVO 840 SSD, and the clone migration failed. "If the system of original disk has some problems or bad sectors, it may not be duplicated."

Some screenshots:

http://i140.photobucket.com/albums/r34/quick215/Samsung%20Data%20Migration%20Fail/cloningfailed_zpse0dbc6ea.jpg
http://i140.photobucket.com/albums/...igration Fail/Ifthefilesystem_zpsddde3287.jpg

Now, there may be other cloning software I can use to force it, but I would like to resolve these sfc problems. I've attached the most recent log.

In addition, I ran checkdisk on boot. I did this a few weeks ago and it took HOURS. Last night I did it, and it only took a few minutes. I have attached the log of the last 30 days, which includes 3 separate check disk scans. The very rough one from November, and two more recent ones. I notice that sometimes checkdisk ran 5 stages, other times it ran only 3 stages. Last night was only 3.

Thank you for assistance in advance. Would be really unfortunate if I wasted $120 on an SSD that I can't use. See attached CBS and Checkdisk Logs.

In the meantime, I am downloading SURT and will run a scan and post that log when available.

 

[quick215]

Attached is the CheckSUR.log as well as the CheckSUR.persist.log. I didn't realize at first that it ran, as there was no notification other than the update completed. I ran it again, and while doing that found the logs with CBS, and cancelled it after it seemed to not be doing anything.

The CheckSUR.persist.log summary:

Summary:
Seconds executed: 725
Found 2 errors
Fixed 1 errors
CSI Manifest Failed Catalog Check Total count: 1
CBS Catalog Corrupt Total count: 1
Fixed: CBS Catalog Corrupt. Total count: 1
Fixed: CBS Paired File. Total count: 1

Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_11.2.9600.17126_none_3b3c2ea0336221d5.manifest


Edit 12-18-14: As I've heard that running sfc many times can help, I've run it again and posted both the SURT and CBS logs in the "new" folder. Again, any help would be very appreciated, especially if you can tell me that this is "the reason" my Samsung SSD clone failed.