Reinstalled windows, no video output from graphics card or igpu

Brandon2016

Commendable
Aug 11, 2016
11
0
1,510
I recently reinstalled windows on my machine, and during the first time boot with my gpu installed (xfx rs Rx 480) I wasn't getting any output. No problem, I took out my graphics card and used the integrated graphics of the CPU. This worked fine, and I was able to get into bios and windows.

However, after installing windows, I wanted to get both monitors set up so I re installed the gpu, plugged in 1 monitor, and booted back up again. No graphics this time once again, however fans were spinning and lights were blinking on the gpu, but a black screen on the monitor.

To troubleshoot, I took out the gpu again, hoping to look for driver issues or something, and plugged my monitor back into the motherboard. Now, black screen on the monitor again. No combination of resetting the cmos, leaving the gpu in while using igpu, just gpu, or just igpu has worked.

Any help is appreciated, and I apologize for the long winded post.
 
Solution
can you get into bios before this happens?

i have built more desktops than i can count for my friends and many people i know and whenever i get no output on screen i always suspect the rams are not seated well in the socket and 90% of the time i am correct it happens to alot of people so just give it a go
take out the rams make sure its not dusty and install it again.
not saying this is your issue but i have seen it happen to people who swore they never moved their desktops so there was no way for the ram seating to be the issue.
can you get into bios before this happens?

i have built more desktops than i can count for my friends and many people i know and whenever i get no output on screen i always suspect the rams are not seated well in the socket and 90% of the time i am correct it happens to alot of people so just give it a go
take out the rams make sure its not dusty and install it again.
not saying this is your issue but i have seen it happen to people who swore they never moved their desktops so there was no way for the ram seating to be the issue.
 
Solution