Windows 10: Getting BSOD on disk clone

I was trying to clone my old hdd to ssd and getting bsod

:)

 

Cloning a Hard Disk

Hi Dav,

Cloning a hard drive is way of transferring data from one hard disk to another drive to make the destination disk contain exactly the same data. You may also find additional information in this
article.

For an in-depth assistance on how to proceed with the process, we suggest that you post your query/concern on the
TechNet forum. This forum is a
community that is mainly composed of IT professionals who can cater to the complexity of your concern.

Regards.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.

 

Cloning OS disk, how to get boot records pointed to correct disk?

This video on cloning HDD with OS to a SSD using Macrium Reflect (and cloning all of the various Windows partitions) shows the last step as using Reflect's "Fix Windows boot problems" options pre-emptively. Youtube link is to the timestamp where this step is taken:

And one of the top comments to the video:
Everyone. DO NOT SKIP THE LAST STEP. Just saved hours of time for me. I had skipped it and after a few days my pc stopped booting correctly. I proceeded to pull this video back up on my phone, and follow the final instructions with the rescue disk since I still had made it during the video, and bam, problem solved. THANK YOU access random! One of the best tutorials I’ve ever seen.

Other comments say things worked fine without that last step and using the last step created boot problems. Confusing!