Hi everyone, I have been reading a number of threads on this forum in regard to the infamous "Image File is Corrupt" problem. In my case I have been having no success in getting a good backup of my system. I would almost always get the corrupt image file message when performing a verify on the backup. This corruption problem was not limited to TrueImage either. I changed to Acronis from another image backup solution that was also failing with corrupt image files. Initially I concentrated my fault diagnosis on my external USB hard drives onto which the images were being written, because many of the threads on the image file corruption problem suggest that there are serious issues with some USB implementations when using external disk drives, and/or large files on external disk drives. In the end I removed the external enclosures altogether and installed a Lian-li RH-58 Drive Caddy rack which allowed me to have 'removable' drives that were directly connected to an IDE controller on the system. However, nothing I did fixed the problem. The backups still failed, even on the 'internal' hard drives! So I then concentrated on the memory in my system. Many threads suggest that memory can be a factor in the corrupt file problem. I ran MEMTEST86 extensively on my system and it reported NO ERRORS. However, when I looked at my BIOS settings I noticed that in the memory timings area of the BIOS there was an item called "Aggressive Timing", which was enabled. So I disabled it as a test. I then ran a TrueImage backup using the Resue Disk (ie from Linux) which would ALWAYS fail previously, and it worked first time. The image file verified without error! I then reset the "Aggressive Timing" option to enabled, and ran the backup again, after which the verify failed. The image file was corrupt! I have now disabled the "Aggressive Timing" option on my system. This has resulted in a slight drop in memory throughput, but that is a small price to pay. Clearly there is more to this than meets the eye. Whatever TrueImage is doing in its processing must stress the memory subsystem well beyond even what MEMTEST86 does, because as I have said, I have never had a failure with memtest. Anyway, the moral of this essay is, if you are having problems with getting a good backup where the image file is being reported as corrupt, check the memory timings on your system. It could be that you need to relax the timings even if Memtest reports no errors! I now get successful backups every time. TrueImage creates a 110GB backup image file using normal compression in just under two hours, and verifies the image file in just under one hour. Outstanding! My System: MSI K8N-Neo2 (nForce3-250) Athlon64 3500+ 2GB Corsair Low Latency (CAS2) DDR running at 200Mhz dual channel ATI XT800-XE Graphics Card 40GB Western Digital Raptor SATA (System drive) 480GB Promise SX4000 RAID5 array Lian-Li RH-58 removable drive caddy etc. Good Luck to you all.