Many of the A/V companies share a reporting mechanism, and some, naming scheme. When one hits, the name/defs are shared with other A/V vendors. And it can take a little while for the FP to propagate back.
The Gen.Variant.Barys.2012 reported by Emisoft, BitDefender, F-Secure, and GData seems like a case for the shared FP, and was probably heuristically detected.
The Ikrarus Win32.SuspectCrc might yield a clue that the file's CRC matched a currently suspected file, so a simple change of the file will produce a new (and likely safe) CRC. Panda may be detecting the same way.
I don't know what Symantec's "WS.Reputation.1" means, other than the file was flagged as suspect, and JRiver may not have a reputation in Symtantec's database (they probably use a point scoring system in their heuristics). This is why a vendor doing its own reporting is useful in the long run - you build up a reputation.
I know nothing about Bkav.
McAfee, Trend, and Panda obviously are using their own naming and heuristics, so probably they should be reported as FP's to each site.
I'll report as FPs a few now.