There's no such thing as "erroneous bytes that will cause it not to be accessable". A file copy program doesn't care about the contents of a file. It just reads one stream of bytes and writes to another.
You can, however, easily check to see if two files match with the md5sum command.
itsme@itsme:~/C$ md5sum help.c
Then, after I copy the file I can run md5sum on the new file and make sure the sums match.
I'm not sure why your copy operation is freezing up, but it shouldn't have anything to do with the contents of the file itself. Maybe a device became unavailable?