06-22-2018 11:45 PM
I just installed a brand new MX500 1TB SSD (purchased directly from Crucial) to replace my laptop's aging 750GB HDD. This was my first direct experience with an SSD, and some things occurred during the clone and after the install that make me somewhat hesitant to trust the new drive. So, I'm wondering if these anomalies are considered normal, or if I should be worried. I am using a ASUS G75VW laptop running 64-bit Windows 8.1 Pro with all the latest updates.
Here are the concerning events:
After it restarted itself, I used the system for about an hour without incident. I then installed Crucial Storage Executive, and all looked well there. New firmware was available (I had M3CR020, and the new version was M3CR022), so I updated the firmware using the reboot method, without incident. I then enabled Momentum Cache, rebooted, and all seems well.
Is this level of disconcerting behavior normal for these SSDs and associated cloning software? Or should I be worried that all is not well, and I should be worried.
06-23-2018 12:27 AM
I'd have given up after my second attempt and just clean installed it.
The two entries in your BIOS are not a partitioning error so you don't need to worry about that. It'll be the same partition listed in windows boot manager twice for some reason. It's harmless.
The reboot is obviously of more concern but your best bet is probably just to continue using the system as normal and see if it was a one off, since the SMART data thinks the drive is physically fine. Modern copies of Windows spontaneously restart instead of showing blue screens. But you will be able to see the error in event viewer after the fact. It will be under the system log and the source will be bugcheck.
Have you done a chkdisk after the clone? And/or an sfc /scannow
There are things you can do to combat issues where a drive is fine but the system is misbehaving with it such as:
i) setting the power plan to high performance (I'd recommend doing this anyway)
ii) setting the drives sata port to hotswap (I'd also recommend doing this as a matter of course)
iii) changing the sata driver between the microsoft one and your chipset one or vicae versa. And even different versions of your chipset driver (I wouldn't necasarily recommend this until deciding you actually have an issue since this recommendation is BECAUSE some drivers and versions are problematic on some systems so, whilst unlikley, you may be introducing an issue where you don't have one!)
iv) and ofc the firmware update you've already done.
06-23-2018 01:46 AM
Thanks so much for your prompt reply.
The only thing I can find in the event log around the time of the spontaneous reboot was from Kernel-Power: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." I hunted around for anything that looked like a crash before that, but didn't find anything. It hasn't occurred since.
I have done a check disk, and it turned up no issues.
I also did an sfc /scannow, and it reported: "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios." I don't know if these issues were already present. I'll investigate each one, and may go back to the original HDD to see if the issues were there before.
So far, since my post, I have been using the system without any other unusual behavior.
I am already running with a high performance power plan, and will consider each of your other recommendations.
06-23-2018 03:22 AM
If you run the DISM command documented here: https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-o...
Then scannow will be able to do whatever fixes it needs to.
06-23-2018 07:48 AM
Thanks for the pointer to DSIM.
I ran it and got:
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see
I am now looking at setting up a local network repair source. Need to do some reading. Everything becomes a career...
06-23-2018 09:53 AM
Yeah the first time I did this, it took me a while to get my head around it.
And unfortuantely I can't remember much about it!
06-23-2018 10:57 AM
@kgcode, My guess is one of your original hard drives may be failing and Acronis was having trouble due to the errors. In my experience most cloning software has trouble when the source drive is slow or failing, but if the other hard drive is failing it can cause interference on the SATA controller causing issues you described. You should be able to see if this was the case by checking both hard drive's SMART Attributes. You can use GSmartControl to check it and they have a portable version so you don't have to actually install anything. You should be able to check your original boot drive by connecting it externally with your USB to SATA cable, although some USB controllers & adapters may block access to SMART. Check that the RAW value for the following SMART Attributes is zero:
5 Reallocated Sector Count
187 Reported Uncorrectable Errors
196 Reallocated Event Count
197 Current Pending Sector Count
198 Uncorrectable Sector Count
188 Command Timeout
199 UltraDMA CRC Error Count (usually indicates a cable issue)
Sometimes SMART errors may be listed below the SMART Attribute table (some GUI's don't include them though) which may not always be reflected in the attributes I listed.
FYI to everyone, if your system is slow or you suspect your hard drive is failing you need to be very careful. The more you keep trying things, the more likely the failing hard drive will get worse to the point where your data will not be recoverable even with professional data recovery services (most people I find don't have any backups). The best free tool I've ever used to clone a failing hard drive is the Linux gddrescue command line tool. Here is a nice overview of the process. In addition to the gddrescue options listed in the link, I would add the following "--ask" so it gives you one chance to make sure you got the source & destination correct.
06-23-2018 09:29 PM
Thanks for your recommendations and for the pointer to the GSmartControl utility.
It's disconcerting that the HDD might have been failing. I ran SMART health checks on it at least monthly using the manufacturer's utility. The HDD didn't seem to slow down. I opted to replace it with the SSD to improve boot time and to reduce noise during recording sessions. (The HDD wasn't particularly noisy, but high-quality recording equipment would pick up the faint "whir" of the drive motor, and I wanted to eliminate that completely.
Using the portable version of GSmartControl, I looked at the attributes of the HDD, connected to a USB adapter:
5 Reallocated Sector Count reported 0
187 Reported Uncorrectable Errors did not appear in the attributes table
196 Reallocated Event Count reported 0
197 Current Pending Sector Count reported 0
198 Uncorrectable Sector Count reported 0
188 Command Timeout did not appear in the attributes table
199 UltraDMA CRC Error Count reported 0
I'm not sure why two of the attributes didn't appear in the table, but the ones that did look ok.
While I was at it, I ran an extended self test on the HDD, and it reported no problems.
Again, thanks for the recommendations and pointer.
06-25-2018 08:35 AM
It would be worth running a chkdsk /r on your old HDD, then attempt cloning again. Typically cloning issues are a result of one of two things, physically errors and problems with the source drive, or more likely simply errors with the data on the drive.
A chkdsk /r will try to address any errors with the data on the drive itself. If this does not resolve the cloning problems you'll need to start looking at alternatives. You could try a different free cloning program like: Macrium Reflect, HD Clone, Clonezilla, but you may need to start think about using a 3rd backup drive to make an image backup through windows then restore it to the SSD, or a clean install of Windows as the final option. Making a backup image is typically more forgiving than cloning; cloning is bit for bit, so if there are any errors with the data on the drive a cloning process is going to have lots of issues.
06-25-2018 11:16 AM
@kgcode, Check your other hard drive for errors as well. If it is having issues, it can affect the cloning process. Not all drives have each of those attributes, but if they exist and are non-zero it could be the reason for the cloning issues or even rebooting issues. Unfortunately not all hard drive issues are reflected in the SMART Attributes.
Is there a BIOS/UEFI firmware update available for your system/motherboard?
If you decide to make another clone, I would suggest performing a clean install of Windows 8.1 first and see if it resolves your problems (make sure to install the system/motherboard chipset & SATA drivers and possibly Intel drivers). You can download the Windows installer direct from Microsoft. Depending on your system, it may even be possible to reinstall Windows over top of itself without affecting your data. Microsoft is very particular in the rules for this for some reason, so most likely the option won't be available to you.
Just on the off chance your new SSD is having issues, you may want to post a screenshot of the SMART Attributes for the MX500. If your laptop uses a SATA cable, then it may need replaced. The reinstall Windows option is a good way to narrow down the possible failure points.