• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Blue screen nv4_disp.dll

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.


New Member
Mar 26, 2002
I have tried all drivers from 23.xx to 28.xx still getting blue screen during 3DMark especially under the bumpmapping test (the big stone floating)
Games are freezing too
I have also tried to play with bios settings....... and removed my soundblaster live card

Please if someone has an clue what's wrong let me know.

My System Win XP - P4 1800 256ram Gf4 ti from Leadtek.
Moderbord Asus P4S333, Chipset SIS645, Ram KingMax
Bios update, drivers for chipset updated. I
Regards Zackman


On a string I was held Senior
Jul 11, 2001
i live
first off how are you cooling the card??
are you overclocked at all(either the proc or the card)??

i have gotten the error once when i was first overclocking the card but since then i have gotten better cooling and no more errors.


Captain Random Senior Evil
Nov 8, 2001

I got that error during 3dmark when I overclocked my cpu too high....


Jul 9, 2001
Louisville, KY
Have you tried the drivers that came with the card?

When installing drivers in XP I've developed the following procedure that has worked right for me every time. First reboot then hit F8 after POST screen to get into safe mode. Next right click My computer-->Properties-->device manager and Uninstall your display adapter.

Next go to your control panel and uninstall your display adapter there. After you uninstall in both places reboot your computer and let XP put default drivers back in. After this install the appropriate nvidia drivers.

NOTE: make sure any virus scan program is disabled while installing drivers

if none of that works try the 21.81's and if you still get errors then perhaps your card is defective


New Member
Jun 13, 2002

I have the exact same system cept i have mushkin ram....exacally the same problem too i lock up on the stone thing, this is too much a coincidence. Im assumiong both our cards cant be damaged in teh same way plus we have differant brands. I have an abit. This leads me to belive its one of two things, its either teh agp drivers, or our nvidia drivers. ANyone have an ideas?


Apr 26, 2001
my suggestion is:
remove your case side panels and leave only one memory stick if you have more than one, set your bios settings to defaults - memory timings reading from SPD, agp interface set to 2x and both sideband addressing/fast writes disabled if you have them available.
then make sure you not have the video card sharing IRQ with other devices.
if you prefer you can try uninstalling/reinstalling video card and chipset drivers. choose other chipset drivers version. im not sure whether 21.xx have the support or not as for that vcard (i dont think so) but they are both stable drivers.

what about your psu? what is it, what wattage?


New Member
Jun 13, 2002
Zack i found teh SOlution in a forum post

Here is the link, seems like teh chipset and geforce4 dont like each other and windows doestn make things easy. The fix is simple and works, the common r=thread is the P4s333 everyone with a p4s333 that tries this resolves the prob. GL.

Here's something to look at - it might help!
Check out what ACPI driver XP decided it wanted to give you!
Device Manager - Computer [expand this section]

If it says 'ACPI Uniprocessor PC' try updating the driver to
'Advanced Configuration and Power Interface[ACPI] PC'

..you'll need to tell XP to update the driver and install from
a 'list or specific location', the choose 'don't search', then
if necessary uncheck 'show compatible hardware' - change the driver
to the one suggested.



Senior Band Wagon Jumper
Jun 9, 2001
Montreal, Quebec, Canada
It's stems from a problem with the NT kernel that WinXP uses, and the earlier Nvidia drivers. It also happens in Win2K after you install the Nvidia drivers but not in 98, 98se, or WinMe. I haven't had time at work to narrow down which driver version fixes the problem, but it's fairly dead at work, so I may have time to continue to figure out which version of the Nvidia drivers do not work.