Blue screen of death after cloning hdd to ssd and wiping hdd

[andrew_schn]

I have an hp pavillion 15-cx0056wm laptop with a 1tb hard drive that i decided to upgrade by adding a 500gb ssd boot drive, specifically an intel 660p. I made a backup of my whole drive and put it on an external storage device before i started the process. I used aomei backupper for the backup and then used it to clone my hdd to my ssd successfully. After that, i went into my bios/UEFI (not sure of nomenclature) and choose my ssd as the boot drive. I booted from the ssd successfully and wiped my hard drive using CMD and the commands: diskpart, select disk 0 (the hdd), clean. This wiped the hard drive and left it completely unallocated, after which i used disk management to create a new simple volume on it. I decide to restart my computer and get hit with a blue screen of death with the error code 0xC000000E.

Tried a few things from around the internet before deciding to just start from scratch using my hdd backup. I went through the entire process again, omiting making a new back up, this time using easeUS todo backup. Success again and this time i tried rebooting before wiping the hard drive. No issues. Wipe the hard drive and blue screen of death with the same error. Any ideas would be much appreciated.

[Enderman]

This is why you do a clean install.

Never clone an HDD to an SSD.

https://www.howtogeek.com/224342/how-to-clean-install-windows-10/

[andrew_schn]

3 minutes ago, Enderman said:

This is why you do a clean install.

Never clone an HDD to an SSD.

https://www.howtogeek.com/224342/how-to-clean-install-windows-10/

Why specifically should i not clone an hdd to an ssd? Both pieces of software that i used have explicit options for just that use case. And I would rather not reinstall all my applications and such if it's possible another solution exists.

Edited December 13, 2019 by andrew_schn
wrong punctuation

[Enderman]

Just now, andrew_schn said:

Why specifically should i not clone an hdd to an ssd? Both pieces of software that i used have explicit options for just that use case? And I would rather not reinstall all my applications and such if it's possible another solution exists.

Well because of issues like this, as well as many others.

Stuff like failing windows updates, programs or windows hanging, high disk usage, etc.

All kinds of windows problems that either happen immediately or some time in the future.

[BigRom]

SATA HDD to SATA SSD (2.5" or M.2 SATA) works fine, and vice-versa. 

 

What you did was clone it from SATA HDD to an NVMe (Intel 660p), NVMe works differently to traditional SATA HDD/SSD in that its using the PCIe lanes. I tried the same, cloning from a SATA SSSD to NVMe and everything went to **** so I ended having to reinstall Windows anyway and copy out the files I needed from the old SSD.

[Lady Fitzgerald]

44 minutes ago, Enderman said:

This is why you do a clean install.

Never clone an HDD to an SSD.

https://www.howtogeek.com/224342/how-to-clean-install-windows-10/

 

38 minutes ago, Enderman said:

Well because of issues like this, as well as many others.

Stuff like failing windows updates, programs or windows hanging, high disk usage, etc.

All kinds of windows problems that either happen immediately or some time in the future.

Horse feathers! I've cloned from SATA HDD to SATA SSD many times with no problems whatsoever. The computer I'm typing on right now was cloned from an HDD to an SSD several years ago and it's working just fine. The problem in this case was the OP tried to go from SATA to NVMe, then, before testing the clone, wiped his HDD.

[andrew_schn]

16 minutes ago, Lady Fitzgerald said:

 

Horse feathers! I've cloned from SATA HDD to SATA SSD many times with no problems whatsoever. The computer I'm typing on right now was cloned from an HDD to an SSD several years ago and it's working just fine. The problem in this case was the OP tried to go from SATA to NVMe, then, before testing the clone, wiped his HDD.

OP would like to make note that he took the proper preparations by making a backup and all of his data is safe and sound

[Enderman]

16 minutes ago, Lady Fitzgerald said:

Horse feathers! I've cloned from SATA HDD to SATA SSD many times with no problems whatsoever. The computer I'm typing on right now was cloned from an HDD to an SSD several years ago and it's working just fine. The problem in this case was the OP tried to go from SATA to NVMe, then, before testing the clone, wiped his HDD.

Clearly you haven't seen the hundreds of people come to this forum and other forums with issues from cloning their OS.

[Dedayog]

1 hour ago, Enderman said:

This is why you do a clean install.

Never clone an HDD to an SSD.

https://www.howtogeek.com/224342/how-to-clean-install-windows-10/

Incorrect.  

 

Haven't seen hundreds claim that.  Tho I have seen many posts about NVMe not booting.

 

 

 

[Enderman]

1 minute ago, jstudrawa said:

Incorrect.  

 

Haven't seen hundreds claim that.  Tho I have seen many posts about NVMe not booting.

I certainly have seen several hundred posts about problems after cloning on this forum alone.

So imagine the thousands of people if you include other forums, reddit, and people who don't post online.

[Lady Fitzgerald]

1 hour ago, Enderman said:

Clearly you haven't seen the hundreds of people come to this forum and other forums with issues from cloning their OS.

I don't know about hundreds (methinks you exaggerate a wee bit) but I have seen quite a few, here and elsewhere. Usually, it boils down to people trying to clone from MBR to GPT, SATA to NVMe, or just using the wrong software. I've used Macrium Reflect for years for cloning dozens of times and the only time I ever had a problem was once when the source disk was corrupted (even though I could still access all the files). That was a data only disk so I just copied the data over (using FreeFileSync), then reformatted the corrupted disk and cloned the data back.

[Lady Fitzgerald]

1 hour ago, andrew_schn said:

OP would like to make note that he took the proper preparations by making a backup and all of his data is safe and sound

Wise man! 

[BigRom]

3 hours ago, Enderman said:

I certainly have seen several hundred posts about problems after cloning on this forum alone.

So imagine the thousands of people if you include other forums, reddit, and people who don't post online.

If they are cloning the HDD/SSD on a source drive that was configured on another set of hardware, yes there is the potential of issues arising from that cloned copy as Windows might crap itself as it encounters a different hardware spec to what it had supposedly "learned"

 

Chipset drivers, other drivers etc. might cause errors and blue screens. I have made many cloning attempts at work, and not really had an issue apart from when a source drive was wrongly configured in the first place.

 

Also pro-tip to anyone planning to clone their drives, shrink the partition on the source drive before cloning, it makes the cloning process so much faster.

[Enderman]

2 hours ago, Lady Fitzgerald said:

I don't know about hundreds (methinks you exaggerate a wee bit)

I've been here a while........

 

6 minutes ago, BigRom said:

If they are cloning the HDD/SSD on a source drive that was configured on another set of hardware

Oh moving OSes to different motherboards is another completely separate issue, I have also seen hundreds of posts with problems caused by that. Probably like double the amount.

 

But no, I was referring to posts I saw with issues just from cloning, no motherboard change.