nVidia nv4_disp infinite loop bug

[Rand]

I've noticed something interesting browsing a few other computer hardware message boards/forums on the net, it seems a common theme right now around the net to be ranting about bugs with nVidia's WindowsXP drivers.
Specificially, the now infamous nv4-disp infinite loop bug experienced under WindowsXP with nVidia graphics card using boards based on VIA chipsets.
Supposedly the bug is related to memory usage of nVidia's Detonator 4/XP drivers, and its not experienced under the Det3's..

The problem manifests itself as blue screens pointing at the nvidia drivers as the culprit. (nv4_disp entered a continuous loop etc). It seems that anything that uses OpenGL triggers this but not every time, and not in a consistent manner.

I've noticed it getting quite a bit of popularity on many forums throughout the net, VIA's and Hercules/Guillemott forums in particular are inundated with complaints about the nVidia driver issues under WinXP.

Interesting enough, I've heard very little complaints about it on the AT forums- this forums seems to be pretty much the only forums I've noticed in which the nv4_disp bug isnt a common topic.
Hence my question, for those that are running an nVidia based graphucs card on a VIA platform under MS WindowsXP have you experienced any of the nVidia driver issues that have caused such rampant debate as is evident on the HardOCP/Hecules/Via Arena/Guru3D etc. etc. forums?

 

[Mem]

Going by VIAARENA thread



<< there have been a number of reports of people who get BSOD (blue screen of death) or a nv4_disp.dll looping error, with the system configuration of WinXP, GeForce 2 or 3 card and Nvidia 2## drivers.

Fiona Gatt VIA
VIAARENA TEAM


>>



I`ve never had the nv4_disp.dll looping error yet however I`ve had few lockups on exit of CS and TFC on exit when it changes res back to normal desktop setting(in openGL mode) but when I run it in D3D it has never happened.

I`ve had one auto reboot on entering CS from gamespy arcade.

Other times I`ve tried to run some older (win95/98games)Might& Magic 7 & 8 and get booted back to desktop so these may be incompatiable with XP OS
Xcom-interceptor will only run if I choose no 3d in options of the game,if I select D3D it will go blank in the space part where you fly.

06/12/2001 01:56 Application Error Faulting application mm8.icd, version 1.0.0.1, faulting module mm8.icd, version 1.0.0.1, fault address 0x000df52b.

06/12/2001 01:57 Application Error Faulting application mm8.icd, version 1.0.0.1, faulting module mm8.icd, version 1.0.0.1, fault address 0x000df52b.

06/12/2001 01:58 Application Error Faulting application mm8.icd, version 1.0.0.1, faulting module mm8.icd, version 1.0.0.1, fault address 0x000df52b.

06/12/2001 01:59 Application Error Faulting application mm8.icd, version 1.0.0.1, faulting module mm8.icd, version 1.0.0.1, fault address 0x000df52b.

06/12/2001 02:02 Application Error Faulting application mm8.icd, version 1.0.0.1, faulting module mm8.icd, version 1.0.0.1, fault address 0x000df52b.

06/12/2001 02:32 Application Hang Hanging application Interceptor.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

06/12/2001 02:34 Application Error Faulting application mm8.icd, version 1.0.0.1, faulting module mm8.icd, version 1.0.0.1, fault address 0x000df52b.

06/12/2001 02:34 Application Error Faulting application mm8.icd, version 1.0.0.1, faulting module mm8.icd, version 1.0.0.1, fault address 0x000df52b.

06/12/2001 02:36 Application Error Faulting application mm8.icd, version 1.0.0.1, faulting module mm8.icd, version 1.0.0.1, fault address 0x000df52b.

06/12/2001 02:49 Application Error Faulting application mm7.icd, version 1.0.0.1, faulting module mm7.icd, version 1.0.0.1, fault address 0x00065934.

06/12/2001 02:50 Application Error Faulting application mm7.icd, version 1.0.0.1, faulting module mm7.icd, version 1.0.0.1, fault address 0x000cf9b1.

06/12/2001 02:58 Application Error Faulting application mm7.icd, version 1.0.0.1, faulting module mm7.icd, version 1.0.0.1, fault address 0x000cf9b1.


Still testing games but I`ve 12 out of 16 running fine at the moment,

BTW auto reboot is now off so I can see the BSOD message problem if it happens again.
XP 1700+
EPOX 8KHA+
512mb crucial pc2100
Leadtek GF2 TI with nvidia 23.11 drivers,
Via 4 in 1 4.35 drivers installed(only installs the INF files)
VIA 4.10 AGP driver installed,
SB Audigy
WIN XP OS.

 

[Phuz]

I have this problem..

 

[jaybittle]

I have a very similar problem, but I don't necessarily get the "nv4_disp infinite loop bug" error.. I get a :

"Computer restated after an unexpected shutdown. Microsoft Windows detected Possible device Failure.
The Driver for the display device was unable to complete a drawing operation. Please check with the device manufacture for a driver update.
The display driver for NVIDIA GeForce 3 seems to be responsible for the system Instabitity"

I usually wake up to this error message, and when I get home from work, same thing. I think it has something to do with my system kicking off a screen saver, or something, because when I could use the machine all day and not have a problem, but be away from the computer for a couple of hours and bam!

I've tried a bunch of different versions of the Det4 drivers and have had all the same results.. 21.83, 22.80, 23.11.. still crashes overnight..

Also related, probably, is the 3rd stick of memory problem with via chipsets.. some people can get it work, I could not -- system performance was extremely horrible..


I have the following:

MSI K7T266 PRO2
Athlon XP 1600+ o/c 10.5x143
Crucial PC2100 2x256
Cardexpert GeForce 3 (not o/c)
Maxtor 40G & 60G HD
Teac 12x10x32x
Toshiba 16x DVD
S/B Audigy

 

[Mem]

<< To all the people who (think they) don't suffer BSODs, but experience random videohangs and instant reboots:

Windows XP is set to automaticaly reboot in case of a BSOD. If you don't alter this setting, you will never see the accompanying BSOD. But it's there!

To turn off automatic reboot in case of BSODs, go to your system properties, click on the advanced tab, into the Startup and Recovery settings, and disable Automatic Restart.
Now you will see the BSOD and the reason why you get a BSOD (like the nv4_disp.dll error). >>

 

[jaybittle]

Thanks Mem -- I'll try that when I get home and see if I get the same BSOD's..

cheers,
--jb

 

[Workin']

OK, I guess first here are my system basics:

Shuttle AK31A (VIA KT266A)
1.4GHz Athlon tbird (not overclocked)
4 sticks of 256MB Crucial unbuffered non-ECC DDR2100 (stock timings)
Gainward GeForce3 Ti200/450 Golden Sample (OC'd to 240/500)
Diamond MX300 (Vortex2)
Linksys 10/100 NIC
Adaptec 2930 SCSI
Maxtor 60GB 7200RPM ATA100
Toshiba EIDE DVD
Internal SCSI Zip drive
External SCSI Yamaha CDRW
External SCSI Jaz drive
Windows XP Professional

I initially had this problem when I first installed XP along with VIA 4-in-1's 4.35V and AGP 4.10, along with nvidia 21.83's. I also had Gainward's graphic card utility installed. Crash-o-matic under any D3D apps.

After reading about this problem until I thought my head would explode, I reformatted, installed XP, installed the 23.10 nvidia driver set, and installed NOTHING else (no VIA drivers or patches, no Gainward software, etc.) and it works perfectly so far with everything I've tried. The only game I typically play is UT (using D3D), and it is working fast and stable. All my other apps work perfectly, as well. Haven't tried OpenGL yet, so I can't comment on that. But it seems most people are having problems with D3D. I also don't leave my PC on 24/7, but so far my screensaver (the 3D tubes one that comes with Windows) hasn't made it crash or act weird.

At the moment I am really happy with my computer. It's fast, stable, and was pretty inexpensive.

 

[nemesismk2]

When will nvidia learn to make decent bug free drivers!

 

[jaybittle]

The current discussions over on VIAArena is that is isn't an NVidia problem, because some ATI cards are reporting the same problems (and I personally experienced them on an ATI and nVidia card)..

The problem is speculated to lie more in DirectX 8.1.. ie Micro$oft..

cheers,
--jb

 

[Rand]

Well at least oine can always go back to the Det3's to avoid the prob;lem, the Det3's apparently don't have the issue.

 

[Mem]

Update just brought "Gothic" the RPG game been playing that for about 5hrs today(yes I like it) no crashes or problems with XP OS and Nvidia drivers with that game so another one to add to my list that works great.

 

[DragonFire]

OMG!



<< The only game I typically play is UT (using D3D) >>



Why on earth would you play UT in D3D when you have a geforce3 card? Good god, install the S3 textures from the second cd and update your opengl driver in ut.




As for the nv4_disp bug, just install the new VIA service pack that they have out. that should stop most of the loops.

 

[daredevil]

I had that problem with the following combinations of drivers:1)Nvidia reference drivers 21.83-21.85 + Via AGP 4.10 2)Nvidia reference drivers 23.11 alone.Note that I hadn't installed at all Via 4-1 4.35.Also the BSOD has occured while I was on the net and not while playing any game.I have now installed 21.83 and I have unistalled Via AGP 4.10 and there is no problem.

 

[ProviaFan]

I've got a problem with my ATI Radeon SDR PCI doing this, with a VIA chipset. I've updated to the latest VIA 4in1s, and still haven't had any success. However, turning off video acceleration causes the problem to be solved (although that creates other problems with DirectX and OpenGL programs refusing to run).
The confusing thing is that it does not just seem related to VIA chipsets. In another thread, there are some people with a SiS chipset having this problem (with ATI cards of various sorts, but all Radeon).

 

[Workin']

<< install the S3 textures from the second cd and update your opengl driver in ut >>

I plan on doing that when I get the chance!

 

[BFG10K]

I have not had a single issue with nVidia's drivers on my KT133a chipset.

Why on earth would you play UT in D3D when you have a geforce3 card? Good god, install the S3 textures from the second cd and update your opengl driver in ut.

So you get cleanly rendered coronas and skies. S3TC degrades the image quality in these areas to abysmal levels.

 

[Mem]

I play UT in D3D all the time and the game just refuses to crash period in this mode so I`ve not bothered using openGL for this game,btw still no nv4_disp infinite loop error yet but I`m working on it .

 

[Emo]

This bug is really annoying... So far there is no clear resolution, is there?

 

[vss1980]

Well, just upgraded the drivers to 22.80 from 22.50 and managed to get the infinite loop bug to appear.
Upgrading from 22.80 to the latest 23.11 did not remedy the problem (as I expected).

However, I dont have a via or sis chipset motherboard, but an intel BX board (running a Leadtek Geforce DDR rev. B board).

I think I'll probably stick with the 21.88 drivers as I didn't seem to find any problems in these drivers in XP (even though they are slightly slower).

 

[ErikaeanLogic]

Just like Rand said, the belief at VIA is that this is an issue tied to the optimization of the NVidia driver by exploiting exaggerated access to system memory. There is a patch (and explanation) for it here.

 

[SOHCC]

I applied the beta patch, turned off fast write, changed to 2x AGP, and set memory setting to normal. I haven't seen BSOD in the last few hours. *fingers-cross*

 

[vss1980]

Yep, obviously nvidia and other graphics card makers are being greedy with system resources (reminds me of when other devices hogged the PCI bus for too long causing skips in the playback of songs).

I also actually have noticed one other thing about this problem. It occurs more often when the graphics card is overclocked (hence pushing out and taking in more data).

Anyway, gone back to 21.88 drivers and problem has gone away.

 

[Insidious]

<< Why on earth would you play UT in D3D when you have a geforce3 card? Good god, install the S3 textures from the second cd and update your opengl driver in ut. >>



Actually, I have found that since going to XP, my UT (with extras CD installation performed) runs MUCH better with D3D selected.
(I am guessing it is DirectX 8.1 being different/better(?)

This was a big surprise to me since OpenGL was always so much better on Windows98 SE for me.

Anyway, the UT sound can be flakey if I play, quit and then start the game again without a boot in between?????
(UT is the only game here (and I have A LOT of them installed) that has any wierdness at all)

 

[resinboy]

I run XP, ( system specs below), and a AliMagic chipset , and also get the same error. My vid card is not overclocked, but I WAS running my FSB at 150. I have backed down to 140, disabled VSYNCH, and set my agp to 2x: so far so good for 3 nights, now. I have tried drivers fron 1240's all the way up: I had problems with them all, but some were definitely worse.
Definitely a Windows XP bug- guess we have to wait for a patch from MS????

Resinboy

 

[TopGun]

I have this problem, it's driving me nuts, I played around with drivers all night eventually going back to the drivers that shipped with the card. I still get random crashes, and sometimes it will not boot all the way into windows, I get a black screen with no picture and have to reboot. Also randomly get the infinite loop bsod. I'm able to play games without a problem, in long stretches 5+ hours with no crashes. When I get back to windows and surf for 10-15 min I get a bsod related to the video drivers. I recently reloaded windows when I installed the geforce and that's when the problems begain, XP ran absolutly perfectly with not a single crash on my old voodoo 5, with 3rd party drivers! I guess my next step is to try to reload XP again....and maybe do minimal drivers, skip the via motherboard drivers maybe?