Question PC doesn't boot when new M.2 SSD is installed ?

darkcry411

Prominent
Sep 30, 2022
12
2
515
Hello all, I wanted to expand my storage so I installed a new HyperX Fury Renegade gen 4 1TB SSD in my system. and now my pc gets a blue screen everytime I try to boot. Moreover I’m in a loop where it first gets a blue screen, then it throws me to automatic repair. When I remove this new SSD, the system works without a problem, but the SSD works on two other systems, one of them being the same motherboard and cpu as my system.

I tried everything that’s mentioned in the following thread (except for taking out the cmos battery, because I don’t wanna mess with that yet):

With the fact that it works in other systems and that my bios and drivers are up to date it means there is some bios setting or I don’t know what that is causing problems, but I can’t figure it out at all, so please can someone help me who is more knowledgeable.

My specs:
CPU: Ryzen 5 5600x
Motherboard: Gigabyte B550 gaming x(bios version f17c)
RAM: hyperx fury 3000mhz 2x 4gb
corsair vengeance 3000mhz 2x4gb
GPU: Radeon 6650XT
SSD: samsung 970 evo plus gen 3 500GB(boot drive)
HDD:Seagate barracuda 1TB
old 320 gb maxtor drive
PSU: Seasonic G12 GM-550
(I know ram isn’t ideal bit there haven’t been problems with that)
PS: sorry for bad formatting, typed this on my phone
 
Install the drive in your other system and clean the drive.
Use diskpart clean method.
Cleaning removes all data and partitioning from the drive. Don't clean the wrong drive.

ka03A000000mKf2QAE__11.jpg
 

darkcry411

Prominent
Sep 30, 2022
12
2
515
I’ll try that, but the other system is elsewhere so that will take some time, will update when that’s done.
 

darkcry411

Prominent
Sep 30, 2022
12
2
515
On second thoughts, what would that even do, that is just a fancy way of resetting it back to factory settings, and it didn’t work out of the box for me, but did in two other systems, the problem is with my pc not the ssd. I have changed boot order, put it in different slots, disabled/enabled fast boot/secure boot. At this point I just want other stuff that I can check in bios, or in windows or wherever on my system.
 
On second thoughts, what would that even do, that is just a fancy way of resetting it back to factory settings, and it didn’t work out of the box for me, but did in two other systems, the problem is with my pc not the ssd. I have changed boot order, put it in different slots, disabled/enabled fast boot/secure boot. At this point I just want other stuff that I can check in bios, or in windows or wherever on my system.
Just a test.......unplug both hdd's.
 
On second thoughts, what would that even do
There are couple of situations, that can cause problems.
1. I suspect your new drive has bootloader partition on it.
When you install new drive, system tries to boot from it and fails.
2. There is partition identifier string conflict with one of your existing drives and new drive.
This can be resolved by cleaning the new drive.

Can you show screenshot from Disk Management? - with only old drives installed.
(to check, if bootloader is on same drive with windows)
 

darkcry411

Prominent
Sep 30, 2022
12
2
515
There are couple of situations, that can cause problems.
1. I suspect your new drive has bootloader partition on it.
When you install new drive, system tries to boot from it and fails.
2. There is partition identifier string conflict with one of your existing drives and new drive.
This can be resolved by cleaning the new drive.
Alright, there could be something in cleaning it, but I don't think it has any bootloader shenanigans, even forcing a load in to my actual boot drive results the same, and even before it got formatted it was throwing the same errors. Also it works flawlessly on other systems, so I guess the only thing here that could be it is the conflicting identifier idea. I'll have an update on this in an hour or so.
 

darkcry411

Prominent
Sep 30, 2022
12
2
515
There are couple of situations, that can cause problems.
1. I suspect your new drive has bootloader partition on it.
When you install new drive, system tries to boot from it and fails.
2. There is partition identifier string conflict with one of your existing drives and new drive.
This can be resolved by cleaning the new drive.

Can you show screenshot from Disk Management? - with only old drives installed.
(to check, if bootloader is on same drive with windows)
using disk part didn't help, still is the same, also here is a screenshot of the disk management tool:
View: https://imgur.com/a/htYibOm