There's something wrong with my voodoo5 5500 agp - it lock-ups when i try to run any 3d on it. I can run some or only one test (but WITHOUT any glitches) in 3dmark2000/2001 before it happens. Quake3 seems to be the fastest way to lock-up - i even can't past the menu.
Also i noticed that if i set single-chip mode in 3dfxtools then everything is ok.
The above has been tested on two completely different systems, I even replaced original cooling with two 5x5x2cm heatsinks + fans. Agp settings also seem to have no impact (AGP speed, driving, aperture size)
Any ideas?
try disabling agp command fifo in the 3dfx tools (if present)
(http://www.3dfx.cz/voodoo4/v4_agp_ogl.png)
checked:
- AGP Command FIFO
- VIA Chipset settings
- Lowering chip frequencies
- AGP Side Band Addresing
still no clue..
btw i noticed strange thing, using 4xAA i can run a bit q3 while using other AA settings there lock-up is at main menu.
have you tried running in single chip?
sounds like your drivers are not loaded up corectly. this will happen in XP if you don't install them with a few tweaks to XP. especially SP1. can you run the Winblows DXdiag at all? I had to rename the drivers.cab file in winblows to drivers.txt (or anything else) to get the first few drivers that were created for XP/3dfx to install at all.
@ps47: as i said in beginning - single chip mode runs ok.
@bloodworm: it's not the drivers, trust me.
seems there's problem in this card, tough i can't find any burned resistors/capacitors/etc. I guess power stabilizers for second chip are damaged, because for a short moment second chip works without any problems. I might start testing with multimeter, only it's hard without any circuit scheme, is something like that available for voodoo5?
ah,yes I see you did mention it,I have skipped it somehow.Doom has exactly the same problem with his voodoo5,and its caused by bad memory..
memory? hm, usually memory poblems doesn't cause lock-ups but only screen corruption.
Command FIFO is in the Frame Buffer memory, if you get a single bit error in the command FIFO region, you will lock up.
Both chips have a lower 1MB of Frame Buffer memory reserved for command FIFO. The FIFOs in both chips have identical command information. If one chip stalls (locks) both will stop and machine will freeze.
Hank
How can i test this then? Any low level apps?