VOGONS


Voodoo 3 2000 Artifacts and noisy video.

Topic actions

Reply 41 of 48, by Zerthimon

User metadata
Rank Member
Rank
Member

Yeah, these and the others (i counted 7 ?, same type) all over the board.

Edit: Before you recap the card, try running it with another mobo.

Reply 42 of 48, by _StIwY_

User metadata
Rank Member
Rank
Member
Zerthimon wrote on 2023-10-16, 12:21:

Yeah, these and the others (i counted 7 ?, same type) all over the board.

Edit: Before you recap the card, try running it with another mobo.

I have a news....i tried the card on another PC with WIndows 7 and........no noisy images anymore....... °L_°

I was sure the card was broken, because i never seen such a problem before. I'll keep you updated, i'm talking with a guy which should be able to explain / fix the thing.

Reply 43 of 48, by SaxxonPike

User metadata
Rank Member
Rank
Member

I understand that this thread is a few months old, but I have some new and relevant information to add.

I experienced this issue with multiple later Voodoo cards on my Athlon-XP machine, using the KT133A chipset. Today, I read through the datasheet and discovered this PCI register:

Device 1 Offset 40 - CPU-to-AGP Flow Control 1 (00h)RW
7 CPU-AGP Post Write

With my 5500, there is no replacement BIOS that I have found to solve the issue. However! By using PCISET I was able to disable this register:

PCISET 8305 1106 40 10000000 00000000

And now there is no flickering on the 5500 in the Duke3D title screen. Something to try if you don't fancy flashing a BIOS.

Sound device guides:
Sound Blaster
Aztech
OPL3-SA

Reply 44 of 48, by _StIwY_

User metadata
Rank Member
Rank
Member

Hello, sorry for the late reply. The problem was.....my damn LCD monitor. For some reasons, he might not "digest" the signal properly, and made me think the problem was elsewhere! It's already happened with other video cards too

Reply 45 of 48, by d909

User metadata
Rank Newbie
Rank
Newbie
SaxxonPike wrote on 2024-04-05, 03:28:
I understand that this thread is a few months old, but I have some new and relevant information to add. […]
Show full quote

I understand that this thread is a few months old, but I have some new and relevant information to add.

I experienced this issue with multiple later Voodoo cards on my Athlon-XP machine, using the KT133A chipset. Today, I read through the datasheet and discovered this PCI register:

Device 1 Offset 40 - CPU-to-AGP Flow Control 1 (00h)RW
7 CPU-AGP Post Write

With my 5500, there is no replacement BIOS that I have found to solve the issue. However! By using PCISET I was able to disable this register:

PCISET 8305 1106 40 10000000 00000000

And now there is no flickering on the 5500 in the Duke3D title screen. Something to try if you don't fancy flashing a BIOS.

This worked for me. Same setup as you. Thanks.

Reply 46 of 48, by nvllsvm

User metadata
Rank Newbie
Rank
Newbie

I had issues with my Voodoo 5500 (PCI) on my Abit AV8 (K8T800 Pro) w/ AMD FX-60. Disabling PCI post writes did fix the issue, but resulted in poor performance - particularly noticeable in 3D titles like Midtown Madness 2 and Unreal Tournament. I confirmed this with 3dmark99.

However - keeping post writes enabled, but underclocking my CPU to 1.3ghz also eliminates the artifacts I was seeing (eg. the menus in Unreal) without such a drastic hit to performance.

The attachment 3dmark99.jpg is no longer available

---
fwiw - these commands enable/disable PCI1 Post Writes on my Abit AV8 (K8T800 Pro):

Disable PCI1 Post Writes
PCISET.EXE 7282 1106 70 10000000 00000000

Enable PCI1 Post Writes
PCISET.EXE 7282 1106 70 10000000 10000000

Reply 47 of 48, by nvllsvm

User metadata
Rank Newbie
Rank
Newbie
nvllsvm wrote on 2024-10-03, 19:43:
I had issues with my Voodoo 5500 (PCI) on my Abit AV8 (K8T800 Pro) w/ AMD FX-60. Disabling PCI post writes did fix the issue, bu […]
Show full quote

I had issues with my Voodoo 5500 (PCI) on my Abit AV8 (K8T800 Pro) w/ AMD FX-60. Disabling PCI post writes did fix the issue, but resulted in poor performance - particularly noticeable in 3D titles like Midtown Madness 2 and Unreal Tournament. I confirmed this with 3dmark99.

However - keeping post writes enabled, but underclocking my CPU to 1.3ghz also eliminates the artifacts I was seeing (eg. the menus in Unreal) without such a drastic hit to performance.

The attachment 3dmark99.jpg is no longer available

---
fwiw - these commands enable/disable PCI1 Post Writes on my Abit AV8 (K8T800 Pro):

Disable PCI1 Post Writes
PCISET.EXE 7282 1106 70 10000000 00000000

Enable PCI1 Post Writes
PCISET.EXE 7282 1106 70 10000000 10000000

After some further testing, underclocking does not resolve the issue in all games. Testing was done at 800x600x16
What it fixes

  • Blood 2
  • Midtown Madness 2
  • Unreal
  • Unreal Tournament

What still has artifacts

  • Quake 2
  • Sin

Reply 48 of 48, by PcBytes

User metadata
Rank l33t
Rank
l33t
bloodem wrote on 2023-05-18, 09:27:
DesktopDynamite wrote on 2023-05-18, 05:14:
Update: […]
Show full quote

Update:

So, I have now downgraded the system to a PII 400Mhz, clocked at 266Mhz in BIOS. Also I have installed single stick of 64MB RAM clocked as 100Mhz [instead of 512MB of 133Mhz]
Currently I did remove the Nvidia AGP card completely and the USB 2.0 PCI card as well, moved the Voodoo 3 on to the first PCI slot.

Testing done on Windows98 and also restarting in MS-DOS, no artifacts anymore, I am guessing the RAM speed from 133Mhz to 100Mhz did the trick here, as at first, the artifacts remained with PII clocked down to 266Mhz and with 256MB at 133Mhz.

I will now try again with the PIII, but this time leaving it with 64MB RAM.

Testing will also be done under pure ms-dos 6.22 setup...

Your problems (and the problems described in this thread) can be permanently solved by flashing one of the newer Voodoo 3 BIOS versions (if you are comfortable with doing it). After that, the card will work fine with any CPU speed, including a very fast Athon XP (and there will be no need to change any motherboard BIOS settings).

Be careful, though, it's very easy to brick the card when flashing it (in which case, you will need an additional card to try and recover it - ask me how I know 😁 ). In your case, since you have a PCI Voodoo 3, you'd need an additional AGP card for the (potential) recovery process.

The BIOS flashing part might be YMMV. I, at least, couldn't revive a V3 3000 with the last BIOS - it did POST and output video but there was heavy artefacting that rendered the card unusable.

"Enter at your own peril, past the bolted door..."
Main PC: i5 3470, GB B75M-D3H, 16GB RAM, 2x1TB
98SE : P3 650, Soyo SY-6BA+IV, 384MB RAM, 80GB