Cloning a windows10 sata ssd to a nvme ssd -> BSOD?

Off-Topic
1

Hi,

nothing related to xojo, but I’m scratching my head for quite some times now, and may be someone here knows how to proceed.
I have a 2 years old windows 10 PC with a sata ssd inside.
I installed a nvme ssd as there is a m2 slot available.
the disk seems fine, a fresh windows 10 install boots fine.
but
I tried almost every known (free) cloning apps like macrium acronis easepm
and the clone of the disk has no error but I get a bluescreen of death on the nvme boot no matter how.
looking inside the nvme disk everything seems fine, but no boot.
if I clone on another sata drive I don’t have this BSOD

if anyone can help ?
thanks.

2

Did the cloning work on a file by file basis or did it duplicate the drive structure. You could need to duplicate the whole drive including the partition structures in order to end up with a bootable system.

3

I had a machine with a NVMe 256GB and a sata 512GB, I made a NVMee upgrade to 1TB.

Few caveats to observe:

The compatibility of your NVMe unity and your computer.
My DELL manual says their controller supports units no more than 2TB for example.
During the cloning the Tool said the unit was encrypted and should use decryption on the fly, and later I could ask to re-encrypt it. I guess it would crash if I had some kind of 1:1 sector by sector of an encrypted unit to another unit, I guess that data would work only for that unit. I used Macrium Reflect for cloning and Minitool for partition reorganization and expansion.

Maybe there is something else.

4

the sata ssd and the nvme are both 500GB in size
I cloned the drive structure of course

5

It was worth checking the blindly obvious :wink:

Does Windows 10 support NVMe out of the box, if not it perhaps requires drivers to support booting from it.

6

NVMe is just direct PCI. No drivers needed. Its in generally easier to boot from NVMe than Sata.

7

I noted in my first post that I installed a fresh windows 10 on the nvme drive and it went fine, no bsod.

8

Which would suggest the some sort of NVMe support is missing from your SATA install. Does it boot in safe mode?

It’s been so long I can’t remember what happens if you reinstall windows over an existing installation. Does it repair it or wipe out the existing install.

This promises a solution.

9

it moves all files in a folder “windows.old” and you have to reinstall everything by hand…

10

already tried macrium, and it fails. and both drives are GPT.

11

Is there perhaps a way of testing the difference between a clean install and the original SATA.

12

Have you tried Clonezilla? It usually works for me. Sometimes I get a blue screen on the first boot but Windows seems to repair itself if you simply allow it to restart.

13

clonezilla is the only one I did not try…

14

If latest Macrium Reflect does not solve it, Clonezilla won’t.

Is it MBR or GPT ? Encrypted or not? I think you still have space for more research on the real problem and tool options for fixing it.

https://knowledgebase.macrium.com/display/KNOW80/Fixing+Windows+boot+problems

Also you could disconnect the second drive and boot just the active NVMe one on the first boot.

All this maintenance is done with battery disconnected and reconnected after the hardware changes.

15

all drives are GPT. they are not encrypted.
and it is a desktop PC so no battery.

edit: tried your macrium link, still bsod…

16

I use Minitool partition wizard from a bootable USB to clone SATA drives to NVME all the time with out problems, BUT, have you tried to at least look for the BSOD code and see if it is related to the cloning or to some UEFI setting?

17

yes I’ve googled the error codes, and all of them lead to some command line sfc or dism, I tried them and it did not fix anything…

18

Can you share the error code? Maybe we can guess from this information.

19

many different ones: 8 or 1 or 91…
each time it goes to (try to) fixing it with sfc /scannow in the command line, or dism
but none of them recover the boot process.

20