Here is one approach I would do on your source machine. I ran into it in the past and it helped me. The machine I was trying to P2V had a lot of things running in the background. Also disable AV if possible prior to P2V.
This is from
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006559
To recover from data corruption with a new conversion:
1.If possible, run the chkdsk utility on the source server before attempting to convert again.
a.Open a command prompt. For more information, see Opening a command or shell prompt (1003892).
b.Type chkdsk c: /f and press Enter.
Note: To complete this command you must restart the server. press y when prompted to schedule the check on restart.
c.Repeat step b, substituting c: for any other local drive letters that must be captured by the conversion.
2.If the server is running any database applications, Active Directory, or Microsoft Exchange, shut down the services prior to conversion to ensure a proper copy. If this is not possible, you must re-index the database tables in the virtual machine after conversion is completed to ensure data integrity.
Note: If the source server is running Active Directory, start up the server in "Directory Service Restore Mode" to prevent the services from starting.
3.Perform another conversion with VMware Converter and specify that the disk sizes be adjusted even by a small amount. This forces a file system only clone and may avoid copying corrupted blocks from the source hard drive.