PC won't start after replacing graphics card

[SuperDJD]

So I recently put my new evga GeForce 1050ti into my pc which has a gigabyte motherboard and a amd 5600 processor. My pc doesn't boot up now, it just stays on the bios screen which I can't navigate using f keys, it also makes that booting beep sound every now and then. I took out ram cards(16gb) and put them back but no improvement, I have enough power minimum 300W for card I have about 400 from psu.

 

[DRagor]

Might be that BIOS on your motherboard is unable to recognize GPU.

 

[SuperDJD]

Any way of getting it to recognise? Do I need to uninstall drivers from previous card?

 

[DRagor]

Check if there's any newer version of BIOS for your motherboard that lists improved GPU compatibility as its feature.
Since you can't even get to BIOS, old drivers are irrelevant.

 

[LinuxDevice]

New drivers won't help within that stage of boot...however, motherboard firmware updates might. Firmware should support basic video functions compatible with most any video card, it isn't like this stage of boot needs to support anything proprietary.

It is also possible that the video card is bad, or that BIOS/UEFI settings corrupted. When was the last time you replaced that button battery on the board? Replacing that and using whatever jumper instructions there are for resetting BIOS/UEFI could help if something corrupted.

Also as a test you might try to boot with only one memory DIMM installed...be sure to use whatever slot the motherboard recommends for single slot memory use. If that DIMM doesn't work, try another, one at a time. This way you depend only on a single DIMM being functional.

FYI, if power is insufficient it will stop the BIOS/UEFI from functioning correctly, but the 1050ti does not take much power and BIOS/UEFI always runs at slow clock speeds, so it seems unlikely. The button battery seems much more likely if it is old.

 

[ttharp]

Ive had this issue too many times. After a day of trying to figure out what was wrong I went and breadboarded the PC and that still didn't fix it. I ended up concluding that it had to do with my RAM. Messed with it for a while and I finally got it to work. I don't know why my PC does it (And every time the RAM is to blame for whatever reason). Give that a try.