Cryodude

Anyone else getting this BSOD in XP? Seems to be driver related. Anything other than the native Geforce (12.40) drivers eventually will crash XP with WinXP 'nv4_disp.dll' Infinite Loop message. Any ideas would be appreciated It happens at stock speeds also, not just overclocking. Have also tried raid and non raid with same results. Have seen this in other threads, but have yet to find a solution system specs are as follows: A7V133A - OCZ Gladiator 512 PC 133 Mushkin (Cas 2) Win XP Pro 1.4 @ 1575 (10.5 * 150) Hercules Prophet Pro (230/460) Raid 0 (2-WD 40 ATA 100's) 2 - WD 60 ATA 66 (mp3 drives) Plexwriter 12/10/32A Intel Phoneline Nic - Slot 2 Turtle Beach Santa Cruz - Slot 3 Linksys Ethernet - Slot 4 Altec ADA 305s (USB) Cooler Guys Gamer Case

Hehe, bought a ti500 and it crashes more than the gf2 Pro. This has got out of hand........I'm seeing the problem everywhere Anyone heard anymore or have any cures for this problem? I am going to reformat(again) back to 9X til they get the problem worked out.

trying 22.50's also Will post results Are gf3's having this problem?

Well...........I spoke too soon...... still getting the crash Went back to the stock XP 1240's and of course all is well and slower If anybody figures this out...... clue me in. Tempted to go buy one of the new Radeons and throw this one in the trash where it belongs this is a VIA/(Bill Gates is Satan)XP/Nvidia problem.....in which they will all blame the other! This never happened with the same board...same cards with NT, Win2K, 98 or WINME./....hmmmm I have logged this problem over 100 times since installation. I have been home with a sick kid...so I've had the time

Have done the same for the gf2 Pro It detected my card also as normal They show to be 15.20 Nvidia drivers did a quick bench with the card overclocked 15% and at stock speeds. Both clock speeds are a hundred points or so less(not bad). They are comparable to the 2183's and 88's as far as I can tell so far and are a far cry from the default XP drivers. I'll take the slight hit for the cure! We shall see....... Wonder why Windows update didn't recognize this at first(hehe....surely not a windows bug) Thanks for the info guys! 8)