There are 1 replies, with the last one on October 08 2014 at 13:30:51 by Seekforever
Quote:
When the image is verified it is read into RAM and checksums for the numerous blocks in the image are calculated and compared to the ones that were created and stored in the image file when it was created. Anything that can cause this to go wrong can be at fault. It can be the RAM, the device storing the archive, the subystem responsible for the archive storing device, etc.
Have a look at:
http://kb.macrium.com/KnowledgebaseArticle50048.aspx
Since you don't appear to have problems during the imaging process itself such as source disk read errors and you can verify other archives which indicates the RAM may not be the problem, I'd run chkdsk /r on the partition/device storing the image.
If you have the disk space, you could try creating the image on another disk and see if it works.
Quote:
When the image is verified it is read into RAM and checksums for the numerous blocks in the image are calculated and compared to the ones that were created and stored in the image file when it was created. Anything that can cause this to go wrong can be at fault. It can be the RAM, the device storing the archive, the subystem responsible for the archive storing device, etc.
Have a look at:
http://kb.macrium.com/KnowledgebaseArticle50048.aspx
Since you don't appear to have problems during the imaging process itself such as source disk read errors and you can verify other archives which indicates the RAM may not be the problem, I'd run chkdsk /r on the partition/device storing the image.
If you have the disk space, you could try creating the image on another disk and see if it works.