Cloned HDD to SSD; Issues with flickering screen, frozen taskbar

jbxdavis

Reputable
Dec 16, 2015
1
0
4,510
Hi all,

Today I set out to transfer my existing OS and all accompanying data from my 1TB hard drive to a new 500GB SSD. I want to keep my old hard drive as storage, like many others have. I downloaded the cloning software provided by the SSD manufacturer, and cloned over the data. Space was not an issue -- the HDD only had about 200GB of data on it in the first place, so copying everything over is fine.

It all seemed to go well, but when I try to boot from the SSD, things get weird. A couple different things have happened, and there doesn't seem to be a consistent pattern. In each situation I can get to the lock screen and log in, but then once I log in, either: A) the screen flickers constantly, and the taskbar never completes loading, though I can access the task manager through ctrl+alt+del or ctrl+alt+esc, B) the screen doesn't flicker, but I still can't access the toolbar. When I mouse over it the mouse changes to a loading wheel, and clicking does nothing, or C) the screen is black, aside from my mouse cursor. I can still use shortcuts to pull up the task manager, and if I run explorer.exe the desktop wallpaper will load, though the taskbar is still unresponsive.

I have my old HDD still connected, and can boot from there no problem. When I do, the system recognizes both drives and all the files on the SSD are in place. Disk Management lists the old HDD as (C) while the new SSD is (F). I've thought about trying to switch them, but I'm not sure how I would do that without causing other issues.

I've also tried swapping the SATA cables, but that didn't seem to have any effect. Furthermore, I found some random tidbits online suggesting fixes, so I've tried disabling certain services but there doesn't seem to be any change.

I'm wondering what to try next. I have a USB with Windows 10 that I could clean install from, but I'd like to retain the data. I'm also unsure how the Windows 10 license key will work, as it seems to be working (to some extent) on both drives at the moment. It could also be a video driver issue, but the new drive has all the same drivers so I'm not convinced on that front.

What I'd like to do is get the SSD up and running normally, and from there I can think about formatting the old HDD to be storage rather than OS-enabled and boot-ready.

Please let me know if you need any more information. I'm usually good at troubleshooting these things on my own, but I'm having no luck right now.

Computer is self-built a couple years ago. ASUS motherboard, NVIDIA graphics card. Old hard drive is 1TB Western Digital Blue, new is 500GB Crucial BX100. Cloned the drive using Acronis's software with a serial key included with the SSD. Windows 10.
 
Solution
1. First of all, test your Crucial SSD with the Crucial test program - http://www.crucial.com/usa/en/support-storage-executive

2. On the face of it the problem sounds like a disk-cloning operation that went awry. It happens with some frequency I fear. Did you try a repeat with the same results?

3. I trust you've since returned the OS's services to its default status. There's far too much nonsense promulgated on the net re canceling this or that service to presumably speed up system actions or correct some problem. In too many instances user canceling/disabling a started service plays havoc with the system.

4. Assuming no problem with the SSD (the likelihood I think), give the disk-cloning operation another go. You might want to try...
1. First of all, test your Crucial SSD with the Crucial test program - http://www.crucial.com/usa/en/support-storage-executive

2. On the face of it the problem sounds like a disk-cloning operation that went awry. It happens with some frequency I fear. Did you try a repeat with the same results?

3. I trust you've since returned the OS's services to its default status. There's far too much nonsense promulgated on the net re canceling this or that service to presumably speed up system actions or correct some problem. In too many instances user canceling/disabling a started service plays havoc with the system.

4. Assuming no problem with the SSD (the likelihood I think), give the disk-cloning operation another go. You might want to try another disk-cloning program - the one I routinely use is the Casper program. It's a commercial program that sells for $49.99, however there is a 30-day trial version you might want to try. It's a very straightforward, easy-to-use program that's quite effective. It can be obtained from... https://www.fssdev.com/products/casper/trial/
The trial edition is slightly crippled as compared with the commercial version, but quite usable in your situation.

There are quite a few freely available disk-cloning programs available on the net as well. Here's a couple...
EaseUS Todo Backup Free
http://www.todo-backup.com/products/home/free-backup-software.htm

Macrium Reflect Free
http://www.macrium.com/reflectfree.aspx

5. Following the (hopefully!) successful disk-cloning operation ensure that your SSD is connected to the first SATA connector/port on your motherboard - designated either SATA 0 or SATA 1.

6. Disconnect the source disk (the old HDD) as well as any other drives that may have been previously connected in the system before booting to the SSD. If any boot problems check the BIOS to determine the SSD is first in boot priority order.
 
Solution