Question Drive cloning success led to failure.

[Quickless]

Hello, I have recently cloned my SSD 500GB drive (which had my windows installation on it) to my brand new M.2 NVMe 1Tb drive. After multiple tries, I finally got the clone to successfully boot up without a BSOD after turning off bios settings like secure boot and memory fast boot. And after the second restart, I went back into BIOS to switch back on fast boot and secure boot, and when I booted up, I got a new BSOD for "KMODE_EXCEPTION_NOT_HANDLED." After undoing these bios changes it still hasnt fixed this problem and every time I startup my pc it gets stuck in the following loop: Boot up>BSOD for kmode exception not handled> automatic restart> System wont post and CPU light on debug LEDs stays lit(Which according to my manual, it means CPU not detected or failed, but I dont think this is the issue as I can restart my system just fine and get into bios/ other bootable softwares) After the debug CPU LED comes on, I must hard shut down my computer by holding the power button or pressing the restart button, then the loop continues from the beginning. The thing that I find weird is that I actually can not boot into the windows media creation tool unless I physically remove my NVMe card, even if I put the USB first on the sequence and FORCE boot off that drive thru bios it still gives me that KMODE exception not handled error until I remove the NVMe and try again. At any rate, I am trying my best not to just completely reinstall windows as I did have stuff I wanted to keep that was on my C: drive such as windows settings, configuration, etc. But alas, if it is the only solution to my cluster of problems I guess I will have to resort to it; I would like to try all other options first. I didn't want to create a whole dissertation paper explaining my problem but I wanted to be as specific as possible, don't hesitate to ask questions telling me to be more specific; I am more than happy to provide deeper specifications on my problem.

Build: https://pcpartpicker.com/list/sr9T4s

 

[Darkbreeze]

Did you change ANY hardware between the time you were running the SATA SSD and the beginning of the problems with the cloned NVME SSD?

What did you use to clone the drive and did you clone ALL of the partitions, including the hidden EFI/Boot/System/Recovery partitions?

HAVE you checked to make sure you have the MOST current motherboard BIOS version installed?

 

[Quickless]

Did you change ANY hardware between the time you were running the SATA SSD and the beginning of the problems with the cloned NVME SSD?

What did you use to clone the drive and did you clone ALL of the partitions, including the hidden EFI/Boot/System/Recovery partitions?

HAVE you checked to make sure you have the MOST current motherboard BIOS version installed?

I did not change any hardware after i concluded that the NVMe was booting up into windows successfully

I cloned it with Macrium Reflect and I did make sure to clone all partitions.

And yes, after one of the previous clones, I had to clear my cmos by shorting and by removing the battery for 15 minutes, after this, I flashed the newest bios with USB flash and booted back up and cloned again, and thats when it worked for the 2 boots that it did before my problems arised

Edit: Something weird that did happen was that after a few boots seeing it the error would eventually go away with bios changes, my bios seemed all messed up with a mismatched GUI, everything was messed up appearance wise and the language was even set to chinese. But after another restart it fixed itself. I dont know if that shows that there is BIOS corruption, but if it does, let me know

 

[USAFRet]

At the end of the clone process, did you...

Power off
disconnect the old C drive
power with only the new drive connected?

 

[Quickless]

At the end of the clone process, did you...

Power off
disconnect the old C drive
power with only the new drive connected?

Yes, I did exactly that and thats when it booted up

I went in and ran DISM checks, sfc scans, and chkdsk commands to ensure that everything was in order and then after that I turned back on fast boot and secure boot in bios and poof, now im only getting the kmode exception not handled bsod and changing the setting back did nothing

 

[Quickless]

At the end of the clone process, did you...

Power off
disconnect the old C drive
power with only the new drive connected?

System just randomly stopped having the error, im booted up into safe mode with networking; what can i do to prevent this in the future

 

[Darkbreeze]

So, I'm betting that AFTER you updated the BIOS, you did not clear the CMOS again like you did PRIOR to updating the BIOS, by unplugging the PSU or flipping it's power switch off, then removing the CMOS battery for five minutes during which time you should press the power button continuously for about 20-30 seconds, then put it all back together and restart into the BIOS and set the optimal default values. After which you could configure your custom settings.

What it does when you fully reset in this way is force the BIOS to reconfigure the hardware tables. SOMETIMES if you don't do this, the BIOS will continue to think it's still running a previous hardware configuration and won't work properly.

Additionally, after a few boots into the BIOS or a few restarts, when you have NOT done this, it will sometimes finally figure out that things have changed and re-train itself with new configuration data. I'm guessing this is what probably eventually happened with yours. However, if it happens again, then I'd start sending some serious stink eye in the motherboard's direction.

Also of note, while the power supply you have isn't complete garbage, it also isn't very good. In fact, it's a fairly dated platform that was never really terrific to begin with and IF you've had it for a while, it's probably not a bad idea to send some stink eye that way as well. Particularly since at 550w you are technically below the recommended capacity for a system running a 3060 TI by about 25w. Not that that would LIKELY be a problem with a better unit, but, it MIGHT be with a CX model, especially if it has some miles on it already. Just a thought, because, you know, power issues can cause absolutely EVERY other problem that can happen with ANY piece of hardware, because if there is any lack of adequate and clean power, at all, then the hardware can't work correctly either.