Unfortunately, no. The error message is as much information as SQL Server will give you.
To discover what values in what columns of which rows are at fault, you need to analyze the data. A common approach to discovering this sort of issue is to perform binary chops - remove half of the data or half of the columns, attempt the insert again (possibly into a temp table with the same structure as the real table) and see if the error recurs.
If it does, great, at least one problem is in the data that remains. If not, then you've eliminated half of the data as not causing a problem.