• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

nv4_disp

tomcat

n00b
Joined
Dec 3, 2005
Messages
16
Hi ive got a Geforce 7800GT and every game i play would freeze up giving a BSOD saying that nv4_disp would be causing the error. I have the latest drivers and the latest BIOS for the MSI RS480 and latest cpu drivers for the AMD X2 3800+. I'm not too sure what to do. Could any of you give me some advice?
 
I looked around on google, hoping that I would find an easy solution for you. What I found is that this a very common problem - there are posts from all the way back in 2001 talking about it. It is obviously an Nvidia driver related bug, but nobody seems to know how to fix it completely. It seems to affect all motherboards and Nvidia cards using all different driver versions.

A couple of suggested Fixes I found, although none of these worked for everyone:

Wipe all the drivers and install latest drivers.
Set PCI Latency to 128.

One guy said running his memory in single channel mode fixed it for him, but that sucks.

Not much help, I know, but google "Nv4_disp bsod" and look for yourself. Tons of people with the exact problem, and no solutions.

Good luck!
 
Try setting the affinity to one processor when playing the game that is crashing. I used the MS Hotfix and AMD Hotfix and rolled back to 78.xx drivers (Pre Dual Core Support drivers). None of that helped with the NV4_DISP bug. I set the affinity, and it stopped blue screening. It has something to do with Nvidia drivers and dual core machines....
 
I had that same problem about a year ago with my GF4 4200, never figured out why it happened. I sold just about every part in that pc (minus the ram) to a friend of mine, he formatted it, put on his copy of windows and he had no problems at all. Go figure.
 
Bump up the RAM voltage a little and/or loosen the timings.
 
I gotta agree with Bop, I've had BSOD from NV4_disp alot and it's really usually because i've overclocked too much, could be on my PCU or mem, but most likely the mem :(
theres no straight way to fix it either. Just takes abit of experimentin :p
 
system ram issue defeinetly. i get that some times when the ram is oc'd too much without enough voltage.
 
well i upated to the latest driver last night and i STILL get this problem while playing WoW. and i dont even have dual core or OCed memory. did any one find another suggestion fix they wanna add to this threaD?
 
Check your memory timings, try loosening them. I had this problem as well and it was a memory timing issue.
 
Just to add to the chorus.. If you're getting this error and are heavily overclocking your system, set everything to stock speed and see if the error goes away. 3D gaming is one of the best ways to uncover system instabilities, far better than any individual stress test.
 
If you read his post you would notice he said he dosn't overclock and his sig shows no sign of overclocking either "Asus A8N-E / AMD 64 3500+ / OCZ 2GB DDR 400 Platinum Edition @ 2-3-3-5 1T timings"
 
I had this problem with a GTX256 and a GTX512 in my system.

Rolling back to 78.03 fixed it. I had to mod the driver so it would install with the 512.

Anyhow AMD CPU driver, setting affinity, dual core hotfix, etc. nothing helped. The problem was NVidia's driver though because anything pre 81.xx was fine - it was only drivers w/dual core that freaked out like this. Complete system rebuilds did not help.

Have an X1800XT now - and it's been smooth sailing ever since. :p
 
I had the same problem just really in WoW and I rolled back to the 78 series of drivers and all is fine. I hear many people are not having the same problems with the beta 83.90 drivers. You can get them at guru3d.com
 
Agh Next time I'm going with ATI. Went with ATI for a long time but then swtich to nvidia for the 7800GT. This card is certainly not worth the trouble. I've tried beta 82.65 with Driver cleaner to clean up all the gunk before it. Played guild wars for about 45 minutes but the BSOD claiming nv4_disp.dll infinite loop error came up again. I've been reading that disabling agp fast writes may solve the problem but I'm not too sure if this option is available for pci e video card users.
 
It's the 8x driver problem that comes with the multithreading. Reverting to the 78.xx series will fix your problem. I just posted a thread about how the next driver release fixes this problem.
 
chronic9 said:
can i use ANY of the 78.xx ??? like ForceWare 79.11 Win2000/XP ???

Yes you can, as long as the number system doesn't go into the 8s, that's when the multi-threaded support came along.
 
serbiaNem said:
It's the 8x driver problem that comes with the multithreading. Reverting to the 78.xx series will fix your problem. I just posted a thread about how the next driver release fixes this problem.
listen to him, that advice fixed my crashing problem too (even with a non-overclocked system, it would crash!)
 
I just recently had this problem, regardless of what drivers I was using.

Simple fix for me was to run Driver Cleaner Pro on my nvidia drivers and reinstall 81.98... at least for me, as I haven't had any problems with 8x.xx drivers.
 
drizzt81 said:
listen to him, that advice fixed my crashing problem too (even with a non-overclocked system, it would crash!)

Fixed my problem too. Thanks by the way. Anyways you can try the 83.90 some have had good luck wit them
 
so i ran driver cleaner pro or w.e its called. restart, no drivers installed, all good.
install 79.11 load up wow. and boom half hr. into the game. woola!
i guess ill try the beta drivers and ill update my mobo drivers 2.
 
Riptide_NVN said:
I had this problem with a GTX256 and a GTX512 in my system.

Rolling back to 78.03 fixed it. I had to mod the driver so it would install with the 512.

Anyhow AMD CPU driver, setting affinity, dual core hotfix, etc. nothing helped. The problem was NVidia's driver though because anything pre 81.xx was fine - it was only drivers w/dual core that freaked out like this. Complete system rebuilds did not help.

Have an X1800XT now - and it's been smooth sailing ever since. :p

Yep. I had the latest drivers with my 6800GS and had this problem. I decided to clean out the drivers totally and install the drivers that came on the CD which are 81.85 and have not experienced this problem since.
 
I'm having this issue in just one game so far. Rome Total War Barbarian Invasion. I've been able to play games like CS:S, NFS:MW etc for hours in a row. I had my system oc'ed so I took everything down to stock and the BSOD would just happen quicker. I reformated my machine and it still happens. I've run 2 instances of prime95 with affinity set to each core and custom testing to test out my ram + have that RHDRIBL test running to test out my video card while P95 is running and to create the maximum amount of heat possible in my case and it runs flawlessly for over 12 hours.

I believe I've used two different drivers from nvidia, the 81.xx WHQLs and the 82.xx betas. Both had the issue. I guess the probably cause is that there is a bug in the nvidia dual core optmized drivers or maybe even xp itself (when dual core cpus are involved) that cause some games to BSOD.



Edit: so I just read through the full thread. WIll the 83.90s fix this problem? I was about ready to RMA my opteron 170 thining it was defective. I have a 7800GTX 512 so I don't think any drivers lower than 8x.xx support my card. This is reminding me of my 9500 pro days.
 
peacetilence said:
Edit: so I just read through the full thread. WIll the 83.90s fix this problem? I was about ready to RMA my opteron 170 thining it was defective. I have a 7800GTX 512 so I don't think any drivers lower than 8x.xx support my card. This is reminding me of my 9500 pro days.

I forget how, but there is a way to modify the drivers manually to add support. I know someone here did just that to support the GTX512.
 
I went through this exact problem 6 months ago with a MSI RS480 and a 6600gt and didn't find a solution. Apart from a new Gigabyte NF4 mobo which ran sweet til I earthed it last week.

With the ATI chipset mobo i'd tried 3 different GF gfx cards, 5 different divers, out-of-case with a desktop fan, most of the BIOS settings one by one etc etc to no avail. Nforce mobo worked instantly, no issues whatsoever.

Dug the MSI/ATI mobo out to get the blown rig running at least and obviously still have same issues. Fine on onboard gfx but BSOD and freezes on PCIE card.

6 months down the line there are many more online reports of problems with this mobo, and my hunch is the voltage to the RAM being too low and making the system exhibit 'OClike' tendencies. The compatible RAM list is very limited to non-performance sticks, my Corsair XMS isn't on that list. No voltage options in the BIOS.

Out of curiosity what RAM are you running? Ive yet to source some vanilla RAM and test it.

PS my rig: A64 3000, MSI RS480, 2x512 Corsair XMS, 450w Fortron/Source PSU, GF6600gt

as you can see I'm running a single core processor and have also tried the pre-dual drivers with no improvement...

I'm hunching on the RAM peculiarities of this mobo in particular...
 
this BS. iam actually thinking of selling my TOP and getting a 512mb 1900xt.
i dont really wanna reformat XP, and i tried lots of drivers already.
 
Well I set my RAM to 166 (333/pc2700) 3-4-4-8

still didn't run stable so my hunch about the RAM is probably dead in the water....

Looking at a new mobo, cheaper than new GFX or RAM even if I could confirm a compatibility prob with either one.

geforce 6100/6150 with 410/430 combo from either Biostar, Foxconn or Gigabyte for me please. Like I said my Gigabyte on NF4 worked a treat...
 
updated bios. formatted. installed latest chipset drivers. installed beta nvida drivers. installed newest creative drivers. NOTHING else. ran wow, 20 mins into it BOOM!

iam pissed............... definatley selling the GTX and get a 1900xtx
 
so does any1 have any updates on this case? i still ahve the GTX, having last thoughts about seling it (i REALLY dont want 2)
 
Set the affinity to one core, or use the nvidia registry hack to disable dual core optimizations. I don't think the problem is severe enough to jump ship (since it seems to be a problem with dual core, more so than drivers; the optimizations Nvidia has added just seem to make it worse) If that doesn't fix it then it might be possible it's unstable hardware caused by a number of issues... I just replaced my mobo + memory in hopes it would get rid of some of these BSODs.
 
hmm, mayb it is the hardware...... since i DONT HAVE dual core.

peacetilence said:
Set the affinity to one core, or use the nvidia registry hack to disable dual core optimizations. I don't think the problem is severe enough to jump ship (since it seems to be a problem with dual core, more so than drivers; the optimizations Nvidia has added just seem to make it worse) If that doesn't fix it then it might be possible it's unstable hardware caused by a number of issues... I just replaced my mobo + memory in hopes it would get rid of some of these BSODs.
 
Back
Top