Member Avatar for Cool Silence

This little driver seems to be causing alot of problems for alot of ppl.
It recently started with me as well, and i've tried a number of different options to resolve this, but without success thus far.
I've uninstalled the driver, booted into safe mode, run "Driver Sweeper", rebooted into safe mode w/networking, Downloaded the latest driver from the nVidia website for the card i'm using and installed it, rebooted, and went ahead and tested it playing NFSU 2.
About 5 mins into the game it goes into 4bit resolution and freezes for a while then the error pops up on the screen again.
I'm using an nVidia GeForce 6200 AGP, but the problem has been reported on PCI-e cards as well. I've tried using other nVidia cards as well but the same thing happens too. The only other thing i can come up with, but not sure that might be a factor is the 12V rail on the PSU is outputing @ 10.34V. Could this cause the problem?

Specs: P4 3.2 Ghz, Biostar P4m800-m7a V7.0, 1Gig DDR, 3 HDD(7Partitions), nVidia GeForce 6200 AGP 512 RAM DDR2, 450W PSU,
2 Dvd R/W, Windows XP w/SP3

  • 2 Contributors
  • 1 Reply
  • 221 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Laser

Dani AI

Generated

Short summary and what the message usually means: on XP-era systems the "nv4_disp" error commonly maps to the kernel condition THREAD_STUCK_IN_DEVICE_DRIVER — a driver thread waiting indefinitely on the GPU. That can be caused by either a buggy display driver or hardware that stops responding (power rail sag, motherboard/chipset/AGP or PCIe transport problems). Given reports that different Nvidia cards behave the same in the same PC, system-level causes should be investigated before replacing GPUs. (learn.microsoft.com)

Practical, low-effort diagnostics to collect evidence first: capture any mini-dump files from C:\Windows\Minidump and run a dump analysis with WinDbg (for a quick summary use !analyze -v) to see which module and stack frames are implicated. Also check the Windows System log (Event Viewer) for nv4_disp or graphics-related errors. While reproducing the fault, log GPU temperatures and voltages with a hardware monitor (HWMonitor, GPU‑Z or similar) so thermal runs or voltage drops are visible in real time. (learn.microsoft.com)

Power and isolation checks next: as suggested, the PSU is a high‑value suspect — measure the +12V rail under load with a DMM or, safer, swap in a known-good PSU. The ATX +12V rail should stay within about 11.4–12.6 V (±5%) under load; persistent sag under gaming load points to PSU or VRM problems rather than a single bad card. Also try the suspect card(s) in another system and test a known-good card in this system to separate card vs system faults. (manualzilla.com)

If power and sensors look fine, pursue firmware/chipset/BIOS and AGP settings: update motherboard chipset drivers and BIOS, and for AGP systems try forcing a lower AGP rate, disable AGP FastWrite and set the AGP aperture to a conservative value (64–128 MB). If minidump analysis keeps pointing at nv4_disp, try a clean driver environment (one change at a time — rollback to a historically stable legacy driver can help isolate regressions). The sequence above prioritizes non-destructive checks and gives concrete datapoints for deciding hardware replacement. (scribd.com)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.