GeForce 4 series
series of GPUs
The GeForce 4 series (codenames below) refers to the fourth generation of Nvidia's GeForce line of graphics processing units (GPUs). There are two different GeForce4 families, the high-performance Ti family (NV25), and the budget MX family (NV17). The MX family spawned a mostly identical GeForce4 Go (NV17M) family for the laptop market. All three families were announced in early 2002; members within each family were differentiated by core and memory clock speeds. In late 2002, there was an attempt to form a fourth family, also for the laptop market, the only member of it being the GeForce4 4200 Go (NV28M) which was derived from the Ti line.
GeForce4 Ti
Architecture
The GeForce4 Ti (NV25) was launched in February 2002 and was a revision of the GeForce 3 (NV20). It was very similar to its predecessor; the main differences were higher core and memory clock rates, a revised memory controller (known as Lightspeed Memory Architecture II/LMA II), Direct3D 8.1 support with up to Pixel Shader 1.3, an additional vertex shader (the vertex and pixel shaders were now known as nFinite FX Engine II), hardware anti-aliasing (Accuview AA), and DVD playback. Legacy Direct3D 7-class fixed-function T&L was now implemented as vertex shaders. Proper dual-monitor support (TwinView) was also brought over from the GeForce 2 MX. The GeForce 4 Ti was superior to the GeForce 4 MX in virtually every aspect save for higher production cost, although the MX had the Nvidia VPE (video processing engine) which the Ti lacked.
Lineup
The initial two models were the Ti4400 (US$299) and the top-of-the-range Ti4600 (US$399).
Begin with the source’s own compact description: “GeForce 4 series” is series of GPUs. The dossier treats that line as a proposition to test through GeForce, series and GPUs, not as a finished interpretation.
Why this record matters
The phrase “series of GPUs” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Sep 17, 2026. The linked authority identifier is Q1028872. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2002.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “GeForce 4 series”, its source revision and the description used here.
- Expand the search: follow GeForce 4 series primary sources, GeForce 4 series archive and GeForce research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “GeForce 4 series”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “GeForce 4 series” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.