Notebookcheck Logo

NVIDIA GeForce Go 6100 vs NVIDIA GeForce Go 6800

NVIDIA GeForce Go 6100

► remove from comparison NVIDIA GeForce Go 6100

The NVIDIA GeForce Go 6100 / 6150 is an integrated graphics card of the NVIDIA nForce Go 430 MCP for AMD Turion notebooks. It doesn't have any integrated memory, but uses a part of the mainmemory (up to 128 MB) like the direct competitor Intel GMA 950. Therefore, the gaming performance is quite moderate and can only be used for elder games.

NVIDIA GeForce Go 6800

► remove from comparison NVIDIA GeForce Go 6800

NVIDIA GeForce Go 6800 is lower clocked than the 6800 Ultra video card for notebooks (and also cooler). The number of pixel pipelines and vertex pipelines is the same like in 6800 Ultra.

Currently the performance of the 6800 is only compareable to a 8600M GT middle class graphics card.

The PureVideo technology delivers acceleration for H.264, WMV, and MPEG2 videos (also in HD) but has a bit less features than the PureVideo engine in the 8600M GT. > Comparison

NVIDIA GeForce Go 6100NVIDIA GeForce Go 6800
GeForce Go 6000 Series
GeForce Go 6800 Ultra compare 12/5 cores @ 0.45 GHz256 Bit @ 600 MHz
GeForce Go 6800 12/5 cores @ 0.3 GHz128 / 256 Bit @ 300 MHz
GeForce Go 6600 compare 8/4 cores @ 0.38 GHz128 Bit @ 300 MHz
GeForce Go 6400 compare 4/3 cores @ 0.4 GHz64 Bit @ 350 MHz
GeForce Go 6250 compare 4/3 cores @ 0.4 GHz64 Bit @ 350 MHz
GeForce Go 6200 compare 4/3 cores @ 0.3 GHz64 Bit @ 300 MHz
GeForce Go 6150 compare 2/1 cores @ 0.43 GHz
GeForce Go 6100 2/1 cores @ 0.43 GHz
GeForce Go 6800 Ultra compare 12/5 cores @ 0.45 GHz256 Bit @ 600 MHz
GeForce Go 6800 12/5 cores @ 0.3 GHz128 / 256 Bit @ 300 MHz
GeForce Go 6600 compare 8/4 cores @ 0.38 GHz128 Bit @ 300 MHz
GeForce Go 6400 compare 4/3 cores @ 0.4 GHz64 Bit @ 350 MHz
GeForce Go 6250 compare 4/3 cores @ 0.4 GHz64 Bit @ 350 MHz
GeForce Go 6200 compare 4/3 cores @ 0.3 GHz64 Bit @ 300 MHz
GeForce Go 6150 compare 2/1 cores @ 0.43 GHz
GeForce Go 6100 2/1 cores @ 0.43 GHz
CodenameC51MVNV42M
Pipelines2 / 1 Pixel- / Vertexshader12 / 5 Pixel- / Vertexshader
Core Speed425 MHz300 MHz
Memory Typeshared Memory
Shared Memoryyesno
APIDirectX 9c, Shader 3.0DirectX 9c, Shader 3.0
technology110 nm130 nm
FeaturesPureVideo, HD TV encoder, Windows Vista Premium90nm
Date of Announcement01.02.2006 25.02.2005
Information110nm, integrierte onboard auf dem NVIDIA nForce Go 430 MCP Chipsatz
Link to Manufacturer Pagehttp://www.nvidia.com/page/nb_chipset.htmlhttp://www.nvidia.com/page/go_6800.html
Memory Speed300 MHz
Memory Bus Width128 / 256 Bit
Max. Amount of Memory256 MB
Notebook Sizelarge

Benchmarks

3DMark 2001SE - 3DMark 2001 - Standard
5100 Points (5%)
23800 Points (25%)
3DMark 03 - 3DMark 03 - Standard
1265 Points (1%)
11000 Points (6%)
3DMark 05 - 3DMark 05 - Standard
655 Points (1%)
4100 Points (6%)
3DMark 06 3DMark 06 - Score Unknown Settings + NVIDIA GeForce Go 6100
3DMark 06
186 Points (0%)
3DMark 06 - Score Unknown Settings + NVIDIA GeForce Go 6800
1900 Points (3%)
3DMark 06 - Standard 1280x1024 + NVIDIA GeForce Go 6100
3DMark 06
min: 141     avg: 173     median: 173 (0%)     max: 205 Points

Average Benchmarks NVIDIA GeForce Go 6100 → 100% n=4

Average Benchmarks NVIDIA GeForce Go 6800 → 746% n=4

- Range of benchmark values for this graphics card
- Average benchmark values for this graphics card
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

For more games that might be playable and a list of all games and graphics cards visit our Gaming List

Add one or more devices and compare

In the following list you can select (and also search for) devices that should be added to the comparison. You can select more than one device.

restrict list:

show all (including archived), 2022, 2021
v1.17
log 28. 13:24:05

#0 checking url part for id 209 +0s ... 0s

#1 checking url part for id 12 +0s ... 0s

#2 not redirecting to Ajax server +0s ... 0s

#3 did not recreate cache, as it is less than 5 days old! Created at Fri, 24 Jun 2022 17:25:51 +0200 +0s ... 0s

#4 linkCache_getLink using $NBC_LINKCACHE +0.046s ... 0.047s

#5 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.05s

#6 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#7 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#8 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#9 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#10 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#11 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.05s

#12 composed specs +0s ... 0.05s

#13 did output specs +0s ... 0.05s

#14 start showIntegratedCPUs +0s ... 0.05s

#15 getting avg benchmarks for device 209 +0.03s ... 0.08s

#16 linkCache_getLink no uid found +0s ... 0.08s

#17 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.08s

#18 linkCache_getLink no uid found +0.002s ... 0.082s

#19 linkCache_getLink no uid found +0.003s ... 0.085s

#20 linkCache_getLink no uid found +0.001s ... 0.086s

#21 linkCache_getLink no uid found +0.001s ... 0.087s

#22 linkCache_getLink no uid found +0s ... 0.087s

#23 got single benchmarks 209 +0.004s ... 0.091s

#24 getting avg benchmarks for device 12 +0s ... 0.091s

#25 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.092s

#26 linkCache_getLink no uid found +0s ... 0.092s

#27 linkCache_getLink no uid found +0s ... 0.093s

#28 linkCache_getLink no uid found +0.001s ... 0.093s

#29 linkCache_getLink no uid found +0.001s ... 0.094s

#30 got single benchmarks 12 +0.004s ... 0.098s

#31 got avg benchmarks for devices +0s ... 0.098s

#32 linkCache_getLink no uid found +0s ... 0.098s

#33 linkCache_getLink no uid found +0s ... 0.098s

#34 linkCache_getLink no uid found +0.001s ... 0.099s

#35 linkCache_getLink no uid found +0s ... 0.099s

#36 linkCache_getLink no uid found +0s ... 0.1s

#37 linkCache_getLink no uid found +0s ... 0.1s

#38 linkCache_getLink no uid found +0s ... 0.1s

#39 linkCache_getLink no uid found +0s ... 0.1s

#40 linkCache_getLink no uid found +0s ... 0.101s

#41 linkCache_getLink no uid found +0s ... 0.101s

#42 min, max, avg, median took s +0s ... 0.101s

#43 before gaming benchmark output +0s ... 0.101s

#44 Got 0 rows for game benchmarks. +0.002s ... 0.103s

#45 linkCache_getLink using $NBC_LINKCACHE +0.058s ... 0.161s

#46 return log +0.002s ... 0.163s

Please share our article, every link counts!
> Notebook / Laptop Reviews and News > Benchmarks / Tech > Graphics Card Comparison - Head 2 Head
Redaktion, 2017-09- 8 (Update: 2017-09-11)