- Apr 17, 2003
- 1,326
- 0
- 0
I got a GF3 from a friend and it has developed the strangest problem. When I turn on my computer, the monitor never wakes from its power saving mode and if I turn the monitor on manually there is no signal from the card, so the monitor just shuts itself off again. I bought the card a few months ago, and it was working fine at the time.
I finally got the card working - well, sort of - by the following process. I removed the GF3, swapped in an old PCI video card, powered on, went into the BIOS and changed the primary video card setting (I forget what it's called exactly) to PCI instead of AGP. Then I left the old PCI video card in and installed the GF3 in the AGP slot just beside it.
Here's the strange part. I booted up and let Windows XP detect the old PCI card, then I was able to go to Display properties and enable the option to extend my desktop on the GF3! Both cards appeared to be working fine, so in Windows XP I set the GF3 to be the primary card and disabled the old PCI video card. The card works fine now and plays 3D games for hours without a single problem.
However, if I set the GF3 as the primary display adapter in the BIOS setup, the card fails to produce a signal again. I have to have the PCI card set as the primary display adapter in the BIOS and the GF3 set as the primary display adapter in Windows in order to have the GF3 produce a signal as the primary card.
Have you ever heard of a problem like this before, and if so what might I do to fix it? I contacted Visiontek, and I was pleasantly surprised when they responded to me after a few weeks. Yes, I did say weeks. I only had to send them the same email every day for...how many days? I lost count. Anyway, they just sent me a canned reply about upgrading to DirectX 8 and to make sure that the AGP slot was compatible.
I have a FIC AD11 with an Athlon XP 1600+, so I have no idea why the board wouldn't be compatible. I also have no idea why having DirectX 9.0 installed on my Windows XP machine would cause the video card to fail to produce a signal even at the BIOS POST screen. Oh, and yes, I did make sure that the computer is not just locked up; the startup beep occurs and then the hard drive churns like usual as XP starts up.
So...any ideas?
I finally got the card working - well, sort of - by the following process. I removed the GF3, swapped in an old PCI video card, powered on, went into the BIOS and changed the primary video card setting (I forget what it's called exactly) to PCI instead of AGP. Then I left the old PCI video card in and installed the GF3 in the AGP slot just beside it.
Here's the strange part. I booted up and let Windows XP detect the old PCI card, then I was able to go to Display properties and enable the option to extend my desktop on the GF3! Both cards appeared to be working fine, so in Windows XP I set the GF3 to be the primary card and disabled the old PCI video card. The card works fine now and plays 3D games for hours without a single problem.
However, if I set the GF3 as the primary display adapter in the BIOS setup, the card fails to produce a signal again. I have to have the PCI card set as the primary display adapter in the BIOS and the GF3 set as the primary display adapter in Windows in order to have the GF3 produce a signal as the primary card.
Have you ever heard of a problem like this before, and if so what might I do to fix it? I contacted Visiontek, and I was pleasantly surprised when they responded to me after a few weeks. Yes, I did say weeks. I only had to send them the same email every day for...how many days? I lost count. Anyway, they just sent me a canned reply about upgrading to DirectX 8 and to make sure that the AGP slot was compatible.
I have a FIC AD11 with an Athlon XP 1600+, so I have no idea why the board wouldn't be compatible. I also have no idea why having DirectX 9.0 installed on my Windows XP machine would cause the video card to fail to produce a signal even at the BIOS POST screen. Oh, and yes, I did make sure that the computer is not just locked up; the startup beep occurs and then the hard drive churns like usual as XP starts up.
So...any ideas?