Windows 10: NVMe M.2 1TB boot drive goes into Bios, no errors, no boot.

I just had this happen, It doesn't give me errors on boot just does not boot into windows, just goes right into the bios where I can see the drive. I have never experienced this before. Been out of the building/fixing PC game for 5-6 years so...

I got a "ran into a problem" windows notice while playing a game right before and it shut down. I have tried everything I can think of including using the Microsoft Install media to fix, nothing works. All options just come back with "We can't install/fix" yadda yadda

I have an older SSD that was on this computer 4 years ago, connected it, booted. Can see the Samsung NVME M.2 drive and I can look at it's contents. It doesn't seem dead or anything. It has 4 partitions. Recovery 500mb, System 100mb, (unsupported)16mb, Windows 1.8 TB.

I have no idea how to get into recovery even if it were a thing. The system came from CyberpowerPC 3 years ago (first time not building my own). I assume they have some type of recovery I did not pay for or something.

I downloaded Samsung Magician and it says "critical" at 87TB written (doubt that means anything here). My motherboard is a Aorus ultra z390. Windows 10 kept updated. Didn't install anything recently, no drivers, no programs, if anything was installed it was a silent windows update or one I did not notice.

I assume this is a corrupted boot issue or something (but why no error?) but do not know how to fix.

I also cannot get into the User folder or change permissions to do so on that drive due to write protection. I would like to fix this, but would settle for just getting my data out of the User folder.

submitted by /u/ObiWanCanShowMe
[link] [comments]

:)

 

M.2 SATA to NVME clone: Windows 10 won't boot

Problem: Windows partition won't boot after cloning M.2 SATA drive to M.2 NVME. Simply returns to BIOS splash screen are restarts boot sequence.

Background: Cloning process was simple raw dd copy. Drive had EFI, Windows 10, and Linux partitions. Cloning preserved exact partition sequence, sizes, and UUIDs.

Linux partition needed minor tweaks to /etc/fstab due to the device names being different (/dev/nvme0n1px vs. /dev/sdax), but boots fine.

The disk is GPT, and I believe the original Windows 10 was UEFI - the Linux installation definitely was.

Boot sequence brings up Linux 'grub' menu first. Choosing the EFI partition then brings up Windows EFI boot menu. Fresh Windows install (see below) boots fine from here, old install fails.

Attempts at solution: I did a fresh Windows install in a spare partition and it boots fine. Using the new Windows installation, I've edited the BCD entry for my original Win 10 install. I have
the correct BCD device, osdevice, and path.

Questions:

• What else needs to be done to make Windows boot again?
• Are there any config file or registry changes that need to be made to account for the SATA to NVME move?
• How do I see boot error messages for a UEFI boot failure? No errors displayed and no log files that I can find in Windows or EFI partitions...

 

Thinking about getting a 1TB m.2

My first thought was that using a 1TB SSD in what is basically a caching scheme is crazy.

On further thought, it's crazy.*Smile

I'd suggest getting this Sabrent Rocket Q 1TB NVMe PCIe M.2 2280 Internal SSD High Performance Solid State Drive R/W 3200/2000 MB/s (SB-RKTQ-1TB) - Newegg.com or this Sabrent 1TB Rocket NVMe PCIe M.2 2280 Internal SSD High Performance Solid State Drive (SB-ROCKET-1TB) - Newegg.com as an alterative to Samsung. If you had a PCI-E 4.0 CPU + motherboard (you do not, at least in your My Computer listing), I'd suggest this: Sabrent 1TB Rocket Nvme PCIe 4.0 M.2 2280 Internal SSD Maximum Performance Solid State Drive With Heatsink (SB-ROCKET-NVMe4-HTSK-1TB) - Newegg.com.

 

cloning hdd to NVMe m.2

Hi Crocodile_aligator

Yes, Windows will load the correct driver for the NVMe M.2. the first time you boot up Windows 10 from that drive after cloning your drive . . .