Aller au contenu principal

Disks Cloned in Acronis TrueImage(2010) failing...

Thread needs solution

Hello acronis forums, first time I've had a major issue with the sofware, hence only just signing up now...
A few months ago I got a brand new SSD for my laptop (Toshiba Satellite P-750) and was forced to clone the OEM OS off the original hard drive, as half the drivers for all the fancy features on this laptop don't seem to be available anywhere, and Toshiba refuse to give me an installation disk for this laptop's specific OS.
Due to a few known issues with my version of the software, I had to use the boot application from the disk to clone them, and they cloned sucessfully. The entire system was then on the SSD, which I promptly popped into my PC and was off.
A few months later, I experienced a fatal error out of the blue with the system. The dreaded Error: eX0000000c. System32 had corrupted itself.
Didn't think much of it at first, just a random crash. Luckily I held onto the old copy of the OEM on the old hard disk.
Then it happened again, and I decided to start routinely making system images.
Just today, it happened again, less that a month after the last crash. I was able to quickly recover from it, but it's starting to get tedious, not knowing when my drive may spontaneously die on me.
I read up on the internet, and it seems many more people are getting this problem with the same software...

In short, I have reason to believe that system disks cloned with TrueImage 2010 are getting corrupted somehow.
Is this an actual issue with a solution?
And is it spontaneous or brought about by something specific?
Or is my product simply out of date? I've been fine with the one I'm using and would rather not have to replace it.
Thanks in advance for anyone willing to aid me.

0 Users found this helpful

If the system hard disk you cloned from had no problems, maybe the SSD is having issues. I've never had a clone created by Acronis True Image work any differently than the original disk. In addition, 4 months with no problems indicates the problems developed on your system after the cloned drive had been working fine for quite some time. Have you performed any hardware diagnostics on your system (RAM, CPU, System board, Video, SSD, etc.)?

There error number you are referencing does not seem to be common as you say, are you sure that is the error you are receiving?

Since you cloned to an SSD drive, have you checked to be sure the partition alignment is correct, and performed any tweaks to help with performance and reliability of the SSD?

Thanks for the quick response,
That wasn't the exact error code it gave me, I simply didn't think to write it down when it happened.
But when I googled it during the first crash about two and a half months ago, I noticed quite a few other people had that problem with acronis-cloned drives as well. (I'm being generous when I say quite a few mind you, but still...)
I have gone through the motions of switching my system over to a SSD, as instructed by the almighty internet, however no massive changes.
Haven't used the old drive for more than a few hours, and I can't exactly put my old drive to the test either, as then my laptop will be SOL.
CPU-Z seems to be registering all my system components as they should, but I don't really have any other diagnostic programs on this PC. RAM, CPU, Video, and mobo (obviously) are all stock, so no real variables there.
Not sure what you mean by partition alignment, I know that I only use one real partition, with two small hidden patitions that I have no control over; they seem to be part of the OEM.
If it happens again, I'll be sure to grab that error code for future reference. Also it seems that the sysrep disk doesn't seem capable of repairing the OS, making it only really useful for running the full system restore from an image.
Also the usual repair procedures with chkdsk utility don't seem to want to help either, if that helps.