Stuck In A Boot Cycle

[KindShrike]

Hi everyone!
So, I have a bit of a Franken-computer that I just put together and it seems to be experiencing a boot loop. It powers up, lights come on, goes through the MOBO lights, gets to boot light, the CPU red flashes briefly and it shuts down only to start back up again. It does this infinitely.
 

Specs:
B560M Pro mobo (used)
RTX 2070 (Used)
16G RAM (two cards) (New)
3TB 3.5" hard drive (New)
Intel Core i3 10100F (New)
750W Seagotep PSU (New)
 

Here is a link to the video of the EZ Debug sequence.
 

What I've tried: Reseating the RAM.
 

Any and all help is greatly appreciated. Thank you.

Notes: 
I did have the SATA cable plugged into SATA6 instead of SATA1, and plan to reseat that cable while I wait for responses. I also plan to take out and reinsert the CMOS to test that.

 

[Itnozetr3]

Try all of your components into someone’s desktop, if all of them worked, except for one, then that thing is probably the trouble. Mostly people will try to seat the processor and the ram, also the powersupply, to someone's pc. And motherboard comes into the last place.

[KindShrike]

2 minutes ago, itnomink said:

Try all of your components into someone’s desktop, if all of them worked, then the last thing you wanted to try is probably the trouble. 

I dont have anyone elses PC to plug them into. 

I am curious - the HD I have is refurbished. Since the EZDebug seems to go through everything okay until it hits BOOT and then powers down, could something on the drive be causing it? Perhaps reformatting the disk could help?

[Itnozetr3]

1 minute ago, KindShrike said:

I dont have anyone elses PC to plug them into. 

I am curious - the HD I have is refurbished. Since the EZDebug seems to go through everything okay until it hits BOOT and then powers down, could something on the drive be causing it? Perhaps reformatting the disk could help?

I don’t think drives will do a bootloop, ( correct me if im wrong ) but mostly bootloops were caused by broken motherboards or processor, you already did reseated the ram and planning to reseating the CMOS, you could try one by one.

 

Maybe going to a computer repair shop will do? But, just try reseating the CMOS first and then if the bootloop still occurs, then just take it to a computer repair shop.

[Itnozetr3]

Could be the powersupply also btw

[KindShrike]

24 minutes ago, itnomink said:

Could be the powersupply also btw

Could be, but I literally just opened it new out of the box today.

So, the CMOS didnt work. Replugging the HD cables didn't work. Only thing I haven't done is the CPU reseat.

Computer repair shop opens early tomorrow. I'll probably just take your advice and do that.

[Itnozetr3]

Just now, KindShrike said:

Could be, but I literally just opened it new out of the box today.

So, the CMOS didnt work. Replugging the HD cables didn't work. Only thing I haven't done is the CPU reseat.

Computer repair shop opens early tomorrow. I'll probably just take your advice and do that.

Alright man, goodluck

[KindShrike]

3 minutes ago, itnomink said:

Alright man, goodluck

Thanks. I'm hoping to get this thing running by Tuesday. Supposed to have this thing built so my partner and I can play a game we've been waiting over a year for. I was hoping I could throw this together and have it working but c'est la vie. Thanks for the luck!

[KindShrike]

Hey folks, so I took it to a repair shop and they're telling me that they suspect it to be the 2070 GPU because they tried two of their cards and my machine worked fine. Problem is.. they also put my GPU into another machine and it also posted just fine in that machine.

To clarify, my machine works fine with another GPU card in it. And MY graphics card works fine in another machine.

Any ideas as to what I can do?

[KindShrike]

So, since the card that doesn't work seems to work in other machines at the shop, I'm going to try to switch out the card that I am currently using in my machine out for the one that refuses to work in JUST the new machine. Wish me luck!

[KindShrike]

So, using the 2070 in my known-working machine it did the exact same thing. That makes sense considering its the exact same build. 

So, I think it's a VBIOS update that I need but I've got no idea how to do it without a screen.