XP and ATI8500- solid???????

[resinboy]

Hi everyone:

a few weeks ago, I installed Win XP Corporate. So far , I am loving it.
However, when running any heavy 3D programs, ESPECIALLY any that use direct 3d, I get a BSOD complaining about the NVDSP4 drivers causing and endless loop. I have tried no less than 10 different sets of Detonators, from the 1260's right up to the latest Beta's. Same thing ( actually some were worse than others). Originally I thought it was related to U.T., as I have read there is apparently an issue with UT and XP (boy, it's a world of abbreviations). For the hell of it, I loaded up Q3, and it runs fine.
See below for system specs: I also am running 512 mg Crucial pc2100, at stock settings.
The problem is slightly less pronounced at 133mhz, more noticeable at 150.
I have tried raising the memory voltage to the boards maximum, disabled vid and system bios cacheable, ( I have always ran my chip voltage at 1.85 ( t-bird 1 gig).
Tried increasing AGP driving strength to maximum.
Saw a thread where someone suggested running the AMD Win 2K patch ( large page miniumum , I think), still same thing.
I have been noticing some similar complaints here and there, and was wondering if switching from my trusty G2GTS, to the ATI 8500 would solve the problem??

Since I have a new board, and a new operating system within 2 weeks of one another, it's making troubleshooting a bitch.

I frequent the AMD MB forums, and I have seen a few people mention they don't think the Iwill XP333 is real stable with Win XP for some reason.


Resinboy

 

[Technonut]

What issue with XP and UT? I am running an 8500 with XP Pro, and UT works fine. I average 65-70 FPS at 1280x1024x32. (vertical sync on) Texture and Skin detail set to high. I can't comment on the IWill XP333 since I am using the KG7-R, but as far as XP Pro and the 8500 goes, I have had no issues with any of my games using the 3286 drivers.

EDIT: The 8500 I have is an ATI built retail card.

 

[Rand]

The nv4_disp infinite loop bug is a well known error in nVidia's detonator drivers when used on WindowsXP platforms. It's especially common when using the Det4 drivers but it occasionally problemsome on the Det3's as well.

Supposedly it has something to do with the manner in which the nVidia Detonator drivers allocate memory usage.
The problem is most often encountered when using a VIA based mobo chipset but it also occasionally seen with Intel, SiS, and ALi chipsets as well.
At present there is no fix for the bug that works for everyone.
If using a VIA board updating to the 4.27 4in1's sometimes helps.
Dropping memory timings in the BIOS occasionally helps, as does dropping the AGP aperture size to below 16MB in the BIOS. You could also try dropping to AGP 1X.

I've had slight problems with the infinite loop bug also, but I managed to resolve it by dropping to AGP 2X, and enabling VIA AGP compatibility mode in NVMax, installing the 4.27 4in1 drivers.
In my experience the best drivers to use if your experiencing the bug is the 21.81 Det4's, or any pre 10.XX detonator drivers. The latest 23.11 seem to have the problem much more frequently then the other driver revisions.

As said, it's NOT an issue with UT and WinXP. It's a very well known compatibility issue between the nVidia nv4_disp diplay driver and the WindowsXP Operating System.

I have heard of ATi's cards having the infinite loop bug also on the very rare occasion, but it's quite unusual. The problem is mostly seen when using a VIA/WinXP/nVidia combo.

nVidia is reportedly working on a fix for the bug, but as yet there has been no results. VIA is also working on a fix for the problem when using VIA chipsets.