Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Xenocrates

Member
  • Content Count

    5
  • Joined

  • Last visited

Awards


This user doesn't have any awards

About Xenocrates

  • Title
    Newbie
  1. Solved. Super rusty on solving these types of problems so I left out what was probably the biggest clue. Cloning the one drive to the other was one of the first things I tried, but the software I tried (from memory, Acronis, Macrium and Easus To-Do) failed because the bytes/sector were incompatible (512 on old vs 4096 on the new) - and I assumed that problem was insurmountable. Then I go spend 15 hours trying to tackle the problem in different ways. No luck from all of the above attempts. Then I realize it the cloning isn't insurmountable, so I find a free software called HDClone that advertised itself as being able to clone in spite of the byte/sector issue. After about 3 hours the cloning was complete. Tested it a few different ways - once without the original SSD, then with the original SSD but a new file on the desktop - but this nightmare is finally over. I'd still be curious for a deeper "why" simply installing Windows itself wasn't working, but I'm content with this, even if I have a lot of cleaning to do.
  2. Started attempting that recently, it'll take about two hours so here's hoping! It was one of the first things I tried, but the bytes/sector sizes are different (512 vs 4096), so most software was failing me because of that but I'm in the process of one that says it can surmount that problem. Won't know for sure until it completes, but fingers crossed!
  3. That's pretty much the gist of it. I did find a decent write up here - but had no luck as the issue seemed similar (that is, Windows might have detected the original drive during some installations, and that was screwing me up) but doing it properly didn't result in a win. I wonder if I need to just return it.
  4. Sorry, should have added more details. I have gone back and forth between legacy/uefi settings. I'll edit that in in a moment. No error codes are shown. No error codes, I'll briefly see a black screen then I'm sent right back into the bios.
  5. Hey guys. I'll try to be thorough but concise. My lone goal is to boot windows 10 off a new SSD. I have a currently working older SSD that runs windows fine (Crucial BX100). Important specs - SSD: Crucial MX500 2 TB MOBO: Sabertooth Z87 CPU: Intel i7-4790k As far as I can see, they should be compatible. I have installed Windows 10 to two separate flash drives. One using the Windows 10 Media Creation tool by itself, the other using Rufus. The SSD seems to work fine in every way except for booting. I can see it in BIOS, device manager, disk manager and even file explorer. I have tested it by installing several programs to it, trying them, then uninstalling them. I can move files to the drive and access them. I can "see" the windows installation on the SSD. But can't boot to it. Going slightly insane trying to get this to work. Here's what I've tried so far as far as I can remember. 2 different installations of Windows. See the rufus/media creation comment. Multiple cables/sata ports. Trying with all other drives unplugged, then again with them back in, then without them etc. Rolling back to previous bios version, testing, then updating to most recent bios version and testing. Read that bios can be "corrupted" and this worked for at least one person. Resetting CMOS by pin connections. Running the Windows repair tool on the flash drives. Setting new SSD as boot drive in priorities. Converting the drive to MBR/GPT, and using Rufus for the respective installation. Alternating legacy/uefi boot settings in the bios. I'll leave this as is-for now and try to edit things in as I go. There have been a lot more attempts, but they've blurred together a bit.
×