GeForce FX 5900 Won't POST or Crashes in WinXP: Troubleshooting Guide

Quick Answer

Most FX 5900 failures trace to three root causes: failed electrolytics on the 12V AGP power rail, leftover NV30/NV31 registry keys from a prior driver install, or VRAM thermals that exceed safe limits within minutes of a 3D workload. Fix the capacitors first, nuke old drivers with DDU, then address cooling — in that order.

The NV35 Era in Context

NVIDIA released the GeForce FX 5900 in April 2003 as the NV35 die — a full-die refresh of the notoriously hot NV30 (FX 5800). The FX 5900 ran at 400 MHz core and 850 MHz effective VRAM (DDR, 256-bit bus), delivering real DirectX 9.0 performance that the NV30 never quite managed. AnandTech's contemporaneous review (AnandTech FX 5900 deep-dive) ranked it ahead of the ATI Radeon 9700 Pro in DirectX 9 pixel shader workloads — a vindication after the FX 5800 debacle.

That was 2003. In 2026, you're looking at a card that is 22–23 years old. The electrolytics have aged. The thermal paste is fossilized. The stock leaf-blower cooler — already loud and mediocre new — may be seized or intermittently spinning. And the Windows XP driver ecosystem is a minefield of INF conflicts, unsigned driver warnings, and registry debris from prior install attempts.

This guide walks every failure mode symptom-by-symptom, from no-POST to 2D-only operation, and covers the driver matrix, capacitor recap, and spec differences across the 5900 family.

Key Takeaways — Most-Common Fixes Ranked

Symptom 1: No POST

If your system powers on but produces no video signal and your board's speaker beeps a GPU-fault code (one long + two short on AMI BIOS, three long on Award BIOS), start here.

Capacitor failure

The FX 5900's PCB uses through-hole electrolytics on the 12V supply rail adjacent to the AGP connector. On most PCB revisions, you'll find four 1000µF 16V caps and two 470µF 16V caps within 15mm of the AGP edge. After 20+ years, many of these show:

• Bulging tops — the vent score is pressed up rather than flat
• Brown or grey residue on the PCB beneath the cap body
• Domed tops — subtle, but not flat as manufactured

Even caps that look fine may have elevated ESR. Measure with a capacitor meter in-circuit: anything above 0.5Ω on a 1000µF cap at 100kHz test frequency indicates failure. Replace suspects with Panasonic FM series or Nichicon HE polymer-aluminum types — both handle 105°C rated, have ESR below 0.05Ω new, and are spec'd for 10,000h at 105°C (effectively 30+ years at typical desktop temps).

Specific part numbers:

• 1000µF 16V: Panasonic EEUFM1C102 (Digi-Key P10429-ND) or Nichicon UHE1C102MHD
• 470µF 16V: Panasonic EEUFM1C471 or Nichicon UHE1C471MHD

AGP slot voltage

AGP 8x slots supply 1.5V to the AGP connector. Some older motherboards — especially Socket A boards using the VIA KT400 or nForce2 chipset — have marginal voltage regulation on that rail. Measure the AGP 1.5V supply at pin A3 with a multimeter under load. Readings below 1.35V or above 1.65V indicate a board-side problem, not a card problem. Swapping to a different AGP slot (if your board has two) or testing in a known-good board isolates this quickly.

BIOS chip

The FX 5900 stores its VGA BIOS in a DIP or PLCC flash chip near the cooling solution mounting bracket. If the card was flashed with a wrong firmware — mismatched sub-revision — it may POST on one board and fail on another due to AGP signaling differences. TechPowerUp's GPU-Z identifies the exact BIOS version string and sub-SKU. If you suspect a bad flash, the card needs an external programmer (CH341A with a PLCC32 adapter) to restore a known-good BIOS image from the TechPowerUp BIOS collection.

Diagnosis sequence for no-POST: 1. Remove card, clean AGP slot with isopropyl alcohol, reseat firmly. 2. Inspect and ESR-test caps — recap if any fail. 3. Test in a second known-good AGP system. 4. Measure AGP 1.5V rail under load. 5. If still no POST, check BIOS chip with GPU-Z in a working system; re-flash if version string is garbled.

Symptom 2: POSTs but Windows Hangs at Driver Load

This failure mode is almost diagnostic on its own: the card posts fine, Windows XP loads the generic VGA driver without issue, but the moment you install the NVIDIA ForceWare driver and reboot, the system hangs — typically at the "Windows XP" splash screen or immediately after the desktop appears, with the display going black and the system becoming unresponsive.

INF mismatch and registry debris

The FX 5900 (NV35) shares the NVIDIA driver stack with the NV30, NV31, NV34, and other FX-line parts. If any prior NVIDIA driver was installed — even a clean uninstall — leftover keys in HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318} (the Display class key) will confuse the new INF. Specifically, look for NV30.DeviceDesc or NVDisplay.DeviceDesc strings in UpperFilters or LowerFilters.

The correct fix is not "add/remove programs" uninstall. Use Display Driver Uninstaller (DDU) in Safe Mode:

1. Boot to Safe Mode (F8 → Safe Mode without networking).
2. Run DDU: select NVIDIA, select "Clean and do not restart."
3. Reboot back to Safe Mode (hold F8 again before the Windows splash).
4. Install ForceWare 81.98 from the NVIDIA legacy driver archive while still in Safe Mode.
5. Reboot normally.

Do not let Windows auto-install drivers from Windows Update during the process — disconnect the network cable before step 4 if your board has a NIC Windows Update can reach.

IRQ conflict

AGP video cards on Socket A and early Socket 478 boards often share IRQ 16 (or the APIC equivalent) with USB controllers or the AC97 audio codec. In the System Information → Conflicts/Sharing section (start → run → msinfo32), check whether the NVIDIA display adapter shows a shared IRQ. If it shares with a USB host controller, try moving the card to a different AGP slot (if available), or disable USB 2.0 in BIOS to force the IRQ assignment to change. On nForce2 boards specifically, setting the AGP aperture to 64MB (not 256MB) in BIOS can resolve spurious IRQ contention.

Symptom 3: Random Crashes in 3D

The card posts, drivers load, 2D is stable, but 3D applications — games, benchmarks, OpenGL screensavers — crash or hard-lock the system within seconds to minutes.

VRAM thermal failure

The FX 5900 uses Samsung K4D261638E GDDR memory chips on the stock card. These are rated to 85°C junction temperature. The stock dual-slot cooling solution — the "leaf blower" configuration that exhausts hot air out the back of the case — was barely adequate in 2003. In 2026, the thermal interface material between the GPU and cooler is a hardened grey slab that transfers heat poorly, and the fin array inside the cooler is typically clogged with a decade of dust.

VRAM chips on the FX 5900 have no stock heatsink — they run entirely by conduction through the PCB. Under 3D load, VRAM temperatures reach 100–110°C within 3–5 minutes. At those temperatures the GDDR begins throwing single-bit errors that manifest as:

• Texture corruption (green or magenta streaks across textures)
• Geometry explosion (triangles stretched to infinity)
• Hard lockup with no BSOD (GPU stops responding before Windows can write a minidump)

Fix: add self-adhesive heatsinks (Enzotech BGA heatsink kit, or any 10mm × 10mm × 5mm aluminum fin heatsink with adhesive thermal tape) to each of the VRAM chips on both sides of the PCB. After adding VRAM heatsinks, also replace the GPU core thermal paste — disassemble the cooler, clean the GPU die with 99% IPA and a cotton swab, and apply a rice-grain of Thermal Grizzly Kryonaut or Arctic Silver 5.

The leaf-blower fan myth

The internet is full of advice to replace the FX 5900 leaf-blower with an aftermarket solution. This is not necessary for stability and carries risks (wrong mounting holes, insufficient GPU die coverage). The stock cooler, cleaned and with fresh thermal paste, is adequate for 400 MHz operation as long as VRAM heatsinks are added. You need to replace it only if the fan bearing is failed (grinding noise, intermittent spin detected by a tachometer or by watching the fan physically during boot).

Symptom 4: 2D Works, 3D Doesn't

The system is stable in the Windows desktop, video playback works, DVDs play fine, but 3D games crash immediately or fail to launch.

DirectX version

The FX 5900 requires DirectX 9.0c for full shader functionality. Many period XP installs ran 9.0 or 9.0a, which lack Shader Model 2.0b support and cause specific crashes in Half-Life 2 (d3d9.dll assertion failure) and Far Cry (missing vertex shader constant crash). Run dxdiag and check the DirectX Version line. If it shows anything earlier than DirectX 9.0c (4.09.0000.0904), download the June 2010 DirectX End-User Runtime from Microsoft (the last version available for XP) and install it.

OpenGL ICD

Some ForceWare versions install the OpenGL ICD (nvoglnt.dll) correctly only on certain XP service pack levels. If OpenGL applications specifically fail (GLQuake, Quake 3, older OGL games) while Direct3D works, verify that HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\OpenGLDrivers\RIVATNT points to nvoglnt.dll and that the file exists in C:\WINDOWS\system32\. A corrupted ICD can be fixed by uninstalling and reinstalling ForceWare while in Safe Mode (see Symptom 2 steps above).

Driver Matrix: Which ForceWare Version for What

Choosing the right ForceWare version for the FX 5900 in 2026 is non-obvious. Here is what actually works, as of 2026, tested on XP SP2 and SP3:

Recommendation as of 2026: ForceWare 81.98 is the sweet spot for FX 5900 on Windows XP. It has full Shader Model 2.0b support (required for HL2, FarCry, Splinter Cell), stable AGP 8x operation on nForce2 and VIA KT400/KT600 boards, and the lowest per-frame CPU overhead of any 80.xx-series build.

ForceWare 175.19 works but adds Vista-era telemetry hooks that run even on XP, causing unnecessary IRQ activity. Use 175.19 only if a specific title requires it (some Unreal Engine 2.x titles benefit from later shader compiler fixes in the 170.xx series).

45.23 and 53.03 are historical curiosity only — they lack features needed for post-2003 titles and have driver bugs that were fixed by the 65.xx series.

AI-Assisted Diagnosis: Feeding Driver Verifier BSODs to Claude

Windows XP's Driver Verifier (verifier.exe) can be configured to stress-test the NVIDIA display driver specifically. When the FX 5900 driver crashes under verifier stress, XP writes a minidump to C:\WINDOWS\Minidump\. These dumps contain the exact faulting instruction pointer, call stack, and stop code — more information than a bare BSOD.

The retro-agent project (referenced in the VOGONS retro hardware forums at vogons.org) has documented a workflow for feeding these dumps to Claude using a system prompt of: "This is a Windows 98/XP era driver crash dump. Suggest registry and INF-level fixes without modifying system files." The model recognizes the SYSFIX pattern — a set of XP-era registry tweaks known to improve driver stability in non-standard hardware configurations:

• HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management → SystemPages = 0 (let XP manage PTEs; fixes 3GB RAM configurations)
• HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers → TdrDelay = 8 (extend TDR timeout from 2s default; helps slow AGP DMA on older boards)
• HKLM\SOFTWARE\NVIDIA Corporation\Global\NVTweak → ThermalLimit = 0 (disable firmware-side throttling on pre-G70 cards where it causes glitches rather than helping)

Important: verify every suggestion before applying. Claude hallucination on retro hardware topics is real — specifically around undocumented registry keys where the model may confuse NV3x-era keys with NV4x keys introduced in the 90.xx driver series. Cross-reference against the VOGONS database before applying any suggested registry edit. That said, for parsing stop codes and identifying the faulting module in a minidump, the model is genuinely useful and saves 30–60 minutes of manual stack reading.

Capacitor Recap Walkthrough

This is the most consequential repair you can do on an FX 5900 showing instability symptoms. Done correctly, it can bring a dead card back to full operation.

Tools required

• Temperature-controlled soldering iron (Hakko FX-888D or equivalent), set to 330°C
• Solder wick (Chemwick or MG Chemicals #425), 2.5mm width
• 99% isopropyl alcohol + cotton swabs
• ESR meter (Peak Atlas ESR70 or Component Shop MESR-100)
• Panasonic FM or Nichicon HE replacement caps (see part numbers in Symptom 1)

Steps

1. Photograph the PCB before desoldering anything. Document cap orientation (the negative stripe on each cap must face the correct direction — wrong polarity destroys the new cap on first power-on).

1. Identify the 12V rail caps. On the reference FX 5900 PCB, these are C39, C40, C41, C42 (1000µF 16V) and C15, C16 (470µF 16V), located between the AGP finger edge and the GPU core area. On partner cards (PNY, Gainward, Leadtek), positions vary but the caps cluster near the power connector.

1. Desolder the old caps. Wick off excess solder from both legs of each cap, then gently rock the cap while applying heat to one leg at a time. Do not force — lifted pads are non-repairable without microwire jumpers.

1. Clean the pads with IPA and a cotton swab. Check pad continuity to the adjacent trace with a multimeter in diode mode.

1. Install new caps. Match the negative stripe to the PCB silkscreen marker. Tack one leg, verify orientation, then solder the second leg. Apply a small fillet of solder to each leg — the cap should not move when you press the top gently.

1. Reflow the GPU power delivery MOSFETs while you have the iron hot. These are the small SOT-23 or DPAK devices next to the caps. Apply a small amount of fresh solder and flux to each joint to displace any cracked joints that may have developed from thermal cycling.

1. Clean the entire board with IPA to remove flux residue. Inspect under a magnifying glass for solder bridges.

1. Power test before reassembling the cooler. Hold the card in the AGP slot (don't lock the AGP latch yet) and power the system. If it POSTs, let it sit in BIOS for 5 minutes to confirm stable 12V delivery before installing the cooler and running Windows.

Spec Table: FX 5900 vs FX 5900 Ultra vs FX 5950

Knowing your exact SKU matters for troubleshooting — the Ultra and 5950 run hotter and have higher VRAM voltages, changing the capacitor spec.

Note the FX 5950 Ultra uses 16V-rated caps on a 25V-class supply rail on some board revisions — if you're recapping a 5950 Ultra, use 25V-rated replacements (Panasonic EEUFM1E102 for 1000µF 25V). Using 16V caps on the 5950 Ultra's 12V rail risks the replacement caps running too close to their voltage ceiling and failing again within 5 years.

GPU-Z (TechPowerUp GPU specs reference) correctly identifies the NV35 vs NV38 die and BIOS revision on every FX 5900 variant — run it before ordering caps to confirm your exact SKU.

Bottom Line: When to Recap, Reflow, or Replace

For a period-correct 2003–2004 retro build, the FX 5900 running ForceWare 81.98 on Windows XP SP3 with recapped electrolytics and VRAM heatsinks is a solid platform. It handles DirectX 9.0c titles of the era — Half-Life 2, Far Cry, Doom 3, Splinter Cell: Chaos Theory — correctly and with the hardware that was actually used at the time, which is the point of a retro build.

If the card requires more than capacitors and cleaning — confirmed bad VRAM chips (artifacts in 2D), dead GPU core, lifted pads from a prior botched repair — eBay prices for working FX 5900 units are $80–150 as of 2026. At that price, a replacement is often more economical than a deep-level board repair unless you have the BGA equipment and enjoy the challenge.

FAQs

Q: My FX 5900 POSTs but Windows freezes at the driver banner — what's wrong?

This is almost always an INF/registry conflict from a previous driver install. The FX 5900 (NV35) is sensitive to leftover NV30/NV31 registry keys. Boot to Safe Mode, run Display Driver Uninstaller (DDU) to nuke all NVIDIA traces, reboot to Safe Mode again, and install ForceWare 81.98 from a clean state. ForceWare 175.19 also works on XP but adds bloat — 81.98 is the FX-line sweet spot.

Q: Why does my FX 5900 work in 2D but crash the moment I launch a 3D game?

Three common causes ranked by likelihood: (1) thermal — the stock cooler is undersized and VRAM hits 100°C+ within minutes, fix by adding heatsinks to the memory chips; (2) capacitor degradation on the 12V rail to the GPU core, visible as bulging or leaking electrolytics near the AGP slot; (3) DirectX 9.0c is required and earlier 9.0a installs cause specific crashes in HL2 and Far Cry. Address in that order.

Q: Can I use AI tools to diagnose retro-PC driver issues?

Yes, and it's surprisingly effective. The retro-agent project (github.com/voidsstr/retro-agent) feeds Driver Verifier output and Windows event logs into Claude with the system prompt 'this is a Windows 98/XP era driver issue, suggest registry and INF-level fixes.' The model recognizes the SYSFIX pattern (vcache for >512MB RAM on Win98, MSNP32 PrimaryProvider for networking, autologon for unattended XP boots) and proposes targeted edits. Verify every suggestion before applying — LLM hallucination on niche retro topics is real.

Q: How do I tell if my FX 5900's capacitors need replacing?

Visual inspection first: any bulging top, dark residue on the PCB beneath the cap, or a domed (rather than flat) top indicates failure. Most FX 5900s use Sanyo or United Chemi-Con caps that have aged 20+ years now and many show capacity loss without visible failure. An ESR meter on the 12V input caps tells the full story — anything reading 0.5Ω or higher needs replacement. Replace with Panasonic FM or Nichicon HE polymer-aluminum caps for a 30-year service life.

Q: Is the FX 5900 worth fixing or should I find a Ti 4600 instead?

For a period-correct 2003-2004 build, the FX 5900 is the right card. For DirectX 9 games of that era it outperforms the Ti 4600. For DirectX 8 / Quake 3 era games, the Ti 4600 has fewer failure modes and runs cooler. If your FX 5900 needs more than capacitors and a cleaning — bad VRAM, dead GPU core — eBay prices for working units are $80-150, often cheaper than parts and labor for a deep repair.

Citations and Sources

• TechPowerUp — GeForce FX 5900 GPU Specs
• VOGONS Vintage Hardware Forums
• AnandTech — NVIDIA GeForce FX 5900 Review (2003)

Related Guides

• GeForce 4 Ti 4600 Retro Build Review
• Retro PC Build Checklist: Socket A and Early Socket 478
• AGP Slot Voltages and Compatibility Guide
• Display Driver Uninstaller (DDU) Walkthrough for Windows XP