Solved Unable to boot with USB to fix Corrupted SSD Drive.

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  • Hello everyone We want to personally apologize to everyone for the downtime that we've experienced. We are working to get everything back up as quickly as possible. Due to the issues we've had, your password will need to be reset. Please click the button that says "Forgot Your Password" and change it. We are working to have things back to normal. Emails are fixed and should now send properly. Thank you all for your patience. Thanks, PCHF Management
Status
Not open for further replies.

GLA2

PCHF Member
Nov 13, 2022
3
0
39
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?
 
Was the drive that you put into the laptop a replacement?

After cloning a drive with bad sectors onto brand new 970 SSD
When you clone a drive with bad sectors it never copies correctly. Once the drive starts to fail it will continue to fail the more it is accessed.

Best thing to do is preform a clean fresh install.

and loading it onto brand new laptop
If you loaded the image refer to above and if this is a brand-new laptop, they previous OS had different drives and hardware and software and firmware that is needed to run the 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.
 
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.
 
Status
Not open for further replies.