Update. I ordered a FireGL x3. If it doesn't work either, I'm going to be strongly suspicious that this is actually a PSU issue. I have a hard time believing I could wind up with 3 bricked cards in a row! Also, I just finished recapping my i845 board, so i'll soon have another board to compare with …

Sounds about right for a X1950 Pro. Try setting FSB to 133Mhz in bios. If the computer takes longer or completely stops locking up at least you will have ruled out AGP incompatibilities. Ok, just tried it. It still locks up, but it acts differently. While it was loading test 3 in 3dmark 01SE I got …

Hmm, interesting, I'll try that and report back in a bit.

Yeah, power is a possible issue, but I thought the nf2 boards got most of their juice from the 12v rail like intel boards Depends on the motherboard, not the chipset. If the board used the 4-pin 12v connector it should be using 12v for the CPU. Seems like your FIC does. The X1950 Pro also takes …

X1950 is pretty tame when it comes to AGP compatibility or so I found. You can check my K8 system’s configuration, driver version and 3DMark01 run results here: https://www.vogons.org/viewtopic.php?f=63&t=33459&start=700#p724957 When someone says K7 and lockup my instinctual suspicion is a weak 5V …

It certainly could be. I'm not very familiar with the quirks of the AGP X1950 though. I haven't used a bridged ATI card in ages. I think ideally you would use Catalyst 7.11 or older. Catalyst 7.12 has a major OpenGL overhaul that breaks some older games like KOTOR. They dropped support for a bunch …

Could it be a flaky motherboard throwing things off/conflicting with the bridge chip?? This is an OEM (eMachines) board after all. The only thing that's gotten anything other than a sudden hang was disabling agp spread spectrum in the bios. I managed to get a flickering screen then a black screen …

I recently bought an x1950 pro to mate with my K7 based Windows XP system, however I'm having issues with it. Basically it locks up within a few minutes of starting a 3d accelerated app. I've tried both the most recent catalyst driver as well as an older one. I've also tried disabling fast write, …