After cloning a drive with bad sectors onto brand new 970 SSD and loading it onto brand new laptop I got BSOD at startup at first but somehow windows seemed to to startup normally after that. After restart i keep getting continuous BSOD (KMODE_EXCEPTION_NOT_HANDLED) on startup. It doesnβt make it to advanced startup options before BSOD. All this is somewhat unsurprising since old drive had bad sectors. However I now find I canβt even access a USB recovery drive on startup if the SSD is installed. (BIOS set to boot from USB of course) if I switch out the drive the laptop and the USB installation drive works just fine. I donβt have an external NVME enclosure so at the moment I canβt even figure out a way to access the SSD at all (otherwise I would just reinstall windows on it). Whatβs happening here?
Unable to boot with USB to fix Corrupted SSD Drive.
Collapse
X
-
Was the drive that you put into the laptop a replacement?
Originally posted by GLA2After cloning a drive with bad sectors onto brand new 970 SSD
Best thing to do is preform a clean fresh install.
Originally posted by GLA2and loading it onto brand new laptop
You will have to perform a fresh install of the OS and drivers installing them in the proper order. -
Sorry for not being clear here.
The Drive in question is Brand new it is simply cloned from a working but bad drive (old drive seems fine until you try to copy it) my plan was to reinstall fresh windows once i had all my programs/files/preferences setup on the new PC. The Pcs are nearly identical and will run on the same software.
It did actually boot once successfully from the drive and loaded all the correct drivers on its own. Seems like its the Boot sector thats bad.
None of this is critical though, my main problem is not being to access USB installation media (I have multiple working windows USBs) if this particular drive (the cloned copy) is mounted in the system. I got BSOD even if USB is chosen to boot in BIOS. As soon as I remove the problem drive (the new cloned copy) The USB works as intended with or without a working version of windows otherwise installed in the system. At the moment I do not even have a way to access the problem drive at all. This was completely unexpected to me I have never seen a corrupted Boot drive prevent access even to USB installation. Having nothing else to go by I am guessing that the preliminary check on the drive is already causing the BSOD. Googling around so far I cannot find such an possibility mentioned anywhere though.Comment
-
Solved: I accessed the drive by connecting externally to another windows PC. Moved around some partitions and Voila I was able to access the RE drive when installed in system and cleaned it up with CMD (Bootrec/BCD). Everything working fine now.
I moved recovery partition to the end of the drive and extended the volume of main partition. I have absolutely no idea why that allowed me to access what was earlier inaccessible.Comment
Comment