Failing to Run monitor On Graphics Card

Qustom

Honorable
Dec 17, 2013
7
0
10,510
Hello, I recently decided to add another monitor to my setup, since I don't have the correct adapter (DVI-I or something), I decided to just check if my VGA cable worked by plugging the 2nd monitor into my motherboard rather than my graphics card.

When I did this, my original monitor turned off, and could no longer recieve a signal from my graphics card.

My Graphics card: Nvidia GTX 650
My motherboard: ixtreme M3720

I spent a while browsing around looking for solutions, and I can't seem to find any that work.

I tried to reinstall the drivers, but cannot get a signal on my monitor
I tried to reset the BIOS settings to default
I disabled intergrated graphics, which actually did nothing.

I don't know what else to do, can anyone suggest anything to help it?
 

Bigeye6

Reputable
Jun 30, 2014
42
0
4,560
Have you unplugged your VGA cable from your motherboard.? It may be prioritising the motherboard output. You should run them off your graphics card because it is a better experience. Your outputs should all come off one device.
 

ust4ever

Honorable
Jun 24, 2013
274
0
10,860
By activating the VGA output on your motherboard, you basically disabled the Graphics Card. The PC prioritizes the motherboard output and turns on IGraphics. Essentially, you can't use both at the same time.

You'll need to purchase the adapter or another Graphics Card if you wish to run two monitors.
 

Qustom

Honorable
Dec 17, 2013
7
0
10,510


I am aware of that now, but I am unable to de-prioritize my motherboard output. After disconnecting my VGA output from both monitors, my monitor will not work with just my monitor plugged into my graphics card any more. Do you know how to solve it?
 

Qustom

Honorable
Dec 17, 2013
7
0
10,510


The fan runs fine, and the only beep I get is when I start up my computer, which is standard.
 

Qustom

Honorable
Dec 17, 2013
7
0
10,510
Unfortunately, I did not find the cause to this problem, as for the solution, I ended up restoring my computer system to a week ago, and that seemed to fix the problem. Thanks for those who contributed, though.