Video help please

Here's the problem I'm having - recently my computer has stopped using the video card and only uses the on-board video for the primary display. :( Since there is only one monitor this really sucks. :mad: The card is a GEForce 8400GS yeah I know not great but vastly better than on-board. I've done a system restore, re-installed the driver, un-installed both and re-installed again. Primary display in bios is set to pci but even the diagnostic boot screen only show on the on-board. It shows the card as installed with no problems. With the cards output set to the secondary display I can manually change the input on my monitor and it displays just fine. I don't game much but the on-board video is so bad it won't run anything. I've tried everything that I could think of or look up :think: except ask here, so now I'm asking.

Thanks in advance for the help.

Bueller? Anyone?

Check your BIOS for the primary/default video device. If the onboard is set for primary, it might be interfering with the OS trying to use the add-in as primary.

Already done.

So it lets you set monitors hooked up to the add-in as secondary displays? What happens when you tell Windows to make that monitor the primary?

Quote:

---

Originally Posted by x88x

So it lets you set monitors hooked up to the add-in as secondary displays? What happens when you tell Windows to make that monitor the primary?

---

I only have one monitor. That's the problem exactly, it won't let me select the add -in as primary. If I just disable the on-board in windows it will either have no display or it will display give a 16 bit display. With the monitors digital input hooked to the add-in and analog hooked to the on-board I can see both by manually switching the monitor.

sounds dumb, but have you checked with another vga or dvi cable. ive have a cheap cord quit working out of the blue.

Thanks for the help guys. I don't know what finally did it but re-installed the driver again and poof it works. :think:
I hate it when that happens, :facepalm: well not really but I'd rather find out what the issue was in the first place.

Weird...maybe a corrupted file somewhere that got purged with the latest driver update?