//flex table opened by JP

Click to See Complete Forum and Search --> : Help! Emergency! New V5 crashes every minute!


racer2c
12-30-2000, 09:40 AM
Woe is me! I got a V5 5500 and a Celery 566 (hoping to get 850 from it)
Before installing the cpu I flashed my bios (ABIT BH6 v1.01) with the latest version. That was successful. I installed the cpu, no problem. I uninstalled my V3 Tools and removed it from Windows. Then plugged the new V5 in. Plugged the power supply into it. Everything booted fine and I installed the newest drivers, 1.04.01 BETA. I bought this card OEM, it didn't come with a CD.
About five minutes into playing Q3, I lost video. The OS didn't crash, the monitor self test came on. Upon reboot I get one long beep and three short ones. I let it sit for a few minutes and it boots up!
Could this be, 1) a bad V5?, 2) a bad bios flash?, 3) a bad CPU?) I doubt that it's the cpu. I plugged my v3 back in and it's holding video.
This blows. I've done everything I can think of besides reformatting, which is next unless someone has some suggestion. I did reflash my bios a couple of times more. It is successful every time.
Please help!
Thanks.

Dputiger
12-30-2000, 10:40 AM
Check your power cables. The V5 uses an external power cable and is sensitive--I had a similar problem to the one your describing.

Mykex
12-31-2000, 01:32 PM
Also that is a hot running card you may try running it with the case open and a desk fan on it to check for heat related prob,you could also install the overclocking utility and try underclocking it. Then there is the option to run it with one vsa chip see what happens there....Best of luck

racer2c
12-31-2000, 04:13 PM
Thanks for the help guys.

I tried everything I know and did as you gguys recommended. Still nothing. I installed it in my second PC and get the exact same results, I lose video after a couple of minutes. Very strange. I'm shipping it back. Maybe I'll go for the a Ge-Force 2 and cut my losses!]
Thanks again.

Dputiger
01-01-2001, 01:14 AM
Try older V5 drivers--I just realized, the only time I saw this problem was with the new Beta drivers.