GeForce 900 series

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
GeForce 900 Series
Release date September 2014
Codename Maxwell
Models GeForce Series
  • GeForce GT Series
  • GeForce GTX Series
Cards
Mid-range GeForce GTX 950M
GeForce GTX 950
GeForce GTX 960M
GeForce GTX 960
GeForce GTX 965M
High-end GeForce GTX 970M
GeForce GTX 970
GeForce GTX 980M
GeForce GTX 980
Enthusiast GeForce GTX 980 "Notebook"
GeForce GTX 980 Ti
GeForce GTX Titan X
Rendering support
Direct3D Direct3D 11.3[1] and Direct3D 12, feature level 11_0 (GM10x) or 12_1 (GM20x)[1][2][3][4]
OpenCL 1.2[5]
OpenGL OpenGL 4.5
Vulkan (API) Vulkan 1.0
SPIR-V
History
Predecessor GeForce 700 series
Successor GeForce 10 series

The GeForce 900 Series is a family of graphics processing units developed by Nvidia, used in desktop and laptop PCs. It serves as the high-end introduction for the Maxwell architecture (GM-codenamed chips), named after the Scottish theoretical physicist James Clerk Maxwell.

The Maxwell microarchitecture, the successor to Kepler microarchitecture, will for the first time feature an integrated ARM CPU of its own.[6] This will make Maxwell GPUs more independent from the main CPU, according to Nvidia's CEO Jen-Hsun Huang.[7] Nvidia expects three major things from the Maxwell architecture: improved graphics capabilities, simplified programming as well as better energy-efficiency compared to the GeForce 700 Series and GeForce 600 Series [8]

Maxwell was announced in September 2010.[9] The first GeForce consumer-class products based on the Maxwell architecture were released in early 2014.[10] Eventually, the Maxwell architecture will be used for mobile application processors that belong to the Erista family of Tegra SoCs.

Architecture

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Maxwell (microarchitecture)

First generation Maxwell (GM10x)

First generation Maxwell GM107/GM108 were released as GeForce GTX 745, GTX 750/750 Ti and GTX 850M/860M (GM107) and GT 830M/840M (GM108). These new chips provide few consumer-facing additional features; Nvidia instead focused on power efficiency. Nvidia increased the amount of L2 cache from 256 KiB on GK107 to 2 MiB on GM107, reducing the memory bandwidth needed. Accordingly, Nvidia cut the memory bus from 192 bit on GK106 to 128 bit on GM107, further saving power.[11] Nvidia also changed the streaming multiprocessor design from that of Kepler (SMX), naming it SMM. The structure of the warp scheduler is inherited from Kepler, which allows each scheduler to issue up to two instructions that are independent from each other and are in order from the same warp. The layout of SMM units is partitioned so that each of the 4 warp schedulers in an SMM controls 1 set of 32 FP32 CUDA cores, 1 set of 8 load/store units, and 1 set of 8 special function units. This is in contrast to Kepler, where each SMX has 4 schedulers that schedule to a shared pool of 6 sets of 32 FP32 CUDA cores, 2 sets of 16 load/store units, and 2 sets of 16 special function units.[12] These units are connected by a crossbar that uses power to allow the resources to be shared.[12] This crossbar is removed in Maxwell.[12] Texture units and FP64 CUDA cores are still shared.[11] SMM allows for a finer-grain allocation of resources than SMX, saving power when the workload isn't optimal for shared resources. Nvidia claims a 128 CUDA core SMM has 86% of the performance of a 192 CUDA core SMX.[11] Also, each Graphics Processing Cluster, or GPC, contains up to 4 SMX units in Kepler, and up to 5 SMM units in first generation Maxwell.[11]

GM107 supports CUDA Compute Capability 5.0 compared to 3.5 on GK110/GK208 GPUs and 3.0 on GK10x GPUs. Dynamic Parallelism and HyperQ, two features in GK110/GK208 GPUs, are also supported across the entire Maxwell product line.

Maxwell provides native shared memory atomic operations for 32-bit integers and native shared memory 32-bit and 64-bit compare-and-swap (CAS), which can be used to implement other atomic functions.

NVENC

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Nvidia NVENC

Maxwell-based GPUs also contain the NVENC SIP block introduced with Kepler. Nvidia's video encoder, NVENC, is 1.5 to 2 times faster than on Kepler-based GPUs meaning it can encode video at 6 to 8 times playback speed.[11]

PureVideo

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Nvidia PureVideo

Nvidia also claims an 8 to 10 times performance increase in PureVideo Feature Set E video decoding due to the video decoder cache paired with increases in memory efficiency. However, H.265 is not supported for full hardware decoding, relying on a mix of hardware and software decoding.[11] When decoding video, a new low power state "GC5" is used on Maxwell GPUs to conserve power.[11]

Second generation Maxwell (GM20x)

Second generation Maxwell introduced several new technologies: Dynamic Super Resolution,[13] Third Generation Delta Color Compression,[14] Multi-Pixel Programming Sampling,[15] Nvidia VXGI (Real-Time-Voxel-Global Illumination),[16] VR Direct,[17][18][19] Multi-Projection Acceleration,[14] and Multi-Frame Sampled Anti-Aliasing (MFAA)[20] however support for Coverage-Sampling Anti-Aliasing (CSAA) was removed.[21] HDMI 2.0 support was also added.[22][23]

Second generation Maxwell also changed the ROP to memory controller ratio from 8:1 to 16:1.[24] However, some of the ROPs are generally idle in the GTX 970 because there are not enough enabled SMMs to give them work to do and therefore reduces its maximum fill rate.[25]

Second generation Maxwell also has up to 4 SMM units per GPC, compared to 5 SMM units per GPC.[24]

GM204 supports CUDA Compute Capability 5.2 compared to 5.0 on GM107/GM108 GPUs, 3.5 on GK110/GK208 GPUs and 3.0 on GK10x GPUs.[14][24][26]

Maxwell second generation GM20x GPUs have an upgraded NVENC which supports HEVC encoding and adds support for H.264 encoding resolutions at 1440p/60FPS & 4K/60FPS compared to NVENC on Maxwell first generation GM10x GPUs which only supported H.264 1080p/60FPS encoding.[19]

Maxwell GM206 GPU supports full fixed function HEVC hardware decoding.[27][28]

False advertisement

GeForce GTX 970 specifications controversy

Issues with the GeForce GTX 970's performance were first brought up by users when they found out that the cards, while featuring 4 GB of memory, rarely accessed memory over the 3.5 GB boundary. Further testing and investigation eventually led to Nvidia issuing a statement that the card's initially announced specifications had been altered without notice before the card was made commercially available, and that the card took a performance hit once memory over the 3.5 GB limit were put into use.[29][30][31]

The card's back-end hardware specifications, initially announced as being identical to those of the GeForce GTX 980, differed in the amount of L2 cache (1.75 MB versus 2 MB in the GeForce GTX 980) and the amount of ROPs (56 versus 64 in the 980). Additionally, it was revealed that the card was designed to access its memory as a 3.5 GB section, plus a 0.5 GB one, access to the latter being 7 times slower than the first one.[32] The company then went on to promise a specific driver modification in order to alleviate the performance issues produced by the cutbacks suffered by the card.[33] However, Nvidia later clarified that the promise had been a miscommunication and there would be no specific driver update for the GTX 970.[34] Nvidia claimed that it would assist customers who wanted refunds in obtaining them.[35] On February 26, 2015, Nvidia CEO Jen-Hsun Huang went on record in Nvidia's official blog to apologize for the incident.[36] In February 2015 a class-action lawsuit alleging false advertising was filed against Nvidia and Gigabyte Technology in the U.S. District Court for Northern California.[37][38]

Nvidia revealed that it is able to disable individual units, each containing 256KB of L2 cache and 8 ROPs, without disabling whole memory controllers.[39] This comes at the cost of dividing the memory bus into high speed and low speed segments that cannot be accessed at the same time unless one segment is reading while the other segment is writing because the L2/ROP unit managing both of the GDDR5 controllers shares the read return channel and the write data bus between the two GDDR5 controllers and itself.[39] This is used in the GeForce GTX 970, which therefore can be described as having 3.5 GB in its high speed segment on a 224-bit bus and 0.5 GB in a low speed segment on a 32-bit bus.[39]

Limited DirectX 12 hardware support

While the Maxwell series was marketed as fully DirectX 12 compliant,[2][40][41] Oxide Games, developer of Ashes of the Singularity, uncovered that the hardware of Maxwell cards does not perform well under DirectX 12 in certain conditions.[42][43]

Using the new asynchronous compute and shader pipeline is not possible with Maxwell GPUs, despite Nvidia specifically advertising the feature for the 900 series.[40] Instead, Nvidia partially implemented this core feature through a driver-based shim, coming at a high performance cost.[43] AMD's GCN-based graphics cards include hardware-based asynchronous compute,[44] giving them the edge in certain DirectX 12 benchmarks and games.[43][45][46]

Oxide claims to have been pressured by Nvidia not to include the asynchronous compute feature in their benchmark at all, so that the 900 series would not be at a disadvantage when competing against AMD's DirectX 12 compliant GCN architecture.[42]

On August 4, 2015, Oxide stated, "We actually just chatted with Nvidia about Async Compute, indeed the driver hasn't fully implemented it yet, but it appeared like it was."[47] Nvidia is working together with Oxide on a full async compute implementation. Unlike AMD's full hardware implementation of the asynchronous pipeline, Nvidia will rely on the driver to implement a software queue and a software distributor to forward asyncronous tasks to the hardware schedulers, capable of distributing the workload to the correct units.[48]

Products

GeForce 900 (9xx) series

Model Launch Code name Fab (nm) Transistors (million) Die size (mm2) Bus interface Core config[lower-alpha 1] Clock speeds Fillrate Memory API support (version) Processing power (GFLOPS) TDP (watts) SLI support[lower-alpha 2] Release price (USD)
Base core clock (MHz) Boost core clock (MHz) Memory (MT/s) Pixel (GP/s)[lower-alpha 3] Texture (GT/s)[lower-alpha 4] Size (MiB)[lower-alpha 5] Bandwidth (GB/s)[lower-alpha 5] Bus type Bus width (bit)[lower-alpha 5] DirectX OpenGL OpenCL Vulkan Single precision[lower-alpha 6] Double precision[lower-alpha 7]
GeForce GTX 950 [51] August 20, 2015 GM206 28 2940 227 PCIe 3.0 x16 768:48:32 1024 1188 6610 32.7 49.2 2048
4096		 106 GDDR5 128 12.0[1][4] 4.5 1.2[5] 1.0 1572 49.1 90 2-way $159
GeForce GTX 950 (OEM) [52] Unknown 1024:64:32 935 Unknown 5010 29.9 59.8 2048 80 1915 59.8 Unknown N/A OEM
GeForce GTX 960 [53] January 22, 2015 1127 1178 7010 39.3 72.1 2048
4096		 112 2308 72.1 120 2-way $199
GeForce GTX 960 (OEM) [54] Unknown GM204 5200 398 1280:80:48 924 Unknown 5010 44.4 73.9 3072 120 192 2365 73.9 Unknown OEM
GeForce GTX 970 [55] September 18, 2014 1664:104:56[56] 1050 1178 7010 54.6 109.2 3584+512[57] 196+28[58] 224+32[39] 3494 109 145 3-way $329
GeForce GTX 980 [41] 2048:128:64 1126 1216 72.1 144 4096 224 256 4612 144 165 4-way $549
GeForce GTX 980 Ti[59] June 2, 2015 GM200 8000 601 2816:176:96 1000 1076 96 176 6144 336 384 5632 176 250 $649
GeForce GTX Titan X [60][61][62] March 17, 2015 3072:192:96 1089 192 12288 6144 192 $999

GeForce 900M (9xxM) series

Some implementations may use different specifications.

Model Launch Code name Fab (nm) Transistors (million) Die size (mm2) Bus interface Core config[lower-alpha 1] Clock speeds Fillrate Memory API support (version) Processing power (GFLOPS) TDP (watts) SLI support[lower-alpha 2]
Base core clock (MHz) Boost core clock (MHz) Memory (MT/s) Pixel (GP/s)[lower-alpha 3] Texture (GT/s)[lower-alpha 4] Size (MiB) Bandwidth (GB/s) Bus type Bus width (bit) DirectX OpenGL OpenCL Vulkan Single precision[lower-alpha 6] Double precision[lower-alpha 7]
GeForce 910M[63] Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown DDR3 Unknown 12.0 4.5 Unknown Unknown Unknown Unknown Unknown Unknown
GeForce 920M[64][65][66] March 13, 2015 GF117 28 585 116 PCIe 3.0 x8 384:16:8 775 1550 1800 3.1 12.4 1024 14.4 DDR3 64 12.0 4.5 1.1 No 595.2 Unknown 33 No
GK208 Unknown 87 575 575 4.6 9.2 2048 1.2 441.6 18.4
GeForce 920MX[67] Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown DDR3 GDDR5 Unknown 12.0 4.5 Unknown Unknown Unknown Unknown Unknown Unknown
GeForce 930M[68][69] March 13, 2015 GM108 28 Unknown Unknown PCIe 3.0 x8 384:16:8 1029 1124 2002 8.23 16.5 1024 2048 16 DDR3 64 12.0 4.5 1.2 1.0 790.3 24.7 33 No
GeForce 930MX[70] Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown DDR3 GDDR5 Unknown 12.0 4.5 Unknown Unknown Unknown Unknown Unknown Unknown
GeForce 940M[71][72][73] March 13, 2015 GM107 28 1870 148 PCIe 3.0 x16 640:40:16 1029 1100 2002 16.5 41.2 2048 16 - 80.2 GDDR5 DDR3 128 12.0 4.5 1.2 1.0 1317 41.1 75 No
GM108 Unknown Unknown PCIe 3.0 x8 384:16:8 8.2 16.5 64 790.3 24.7 33
GeForce 940MX[74] Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown DDR3 GDDR5 Unknown 12.0 4.5 Unknown Unknown Unknown Unknown Unknown Unknown
GeForce 945M[75] Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown DDR3 GDDR5 Unknown 12.0 4.5 Unknown Unknown Unknown Unknown Unknown Unknown
GeForce GT 945A[76] Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown 1024 Unknown GDDR5 Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown
GeForce GTX 950M[77][78] March 13, 2015 GM107 28 1870 148 PCIe 3.0 x16 640:40:16 914 1085 5012 14.6 36.6 2048 80 GDDR5 128 12.0[1][4] 4.5 1.2[5] 1.0 1170 36.56 75 No
GeForce GTX 960M[79][80] March 13, 2015 GM107 28 1870 148 PCIe 3.0 x16 640:40:16 1029 1085 5012 16.5 41.2 2048 80 GDDR5 128 12.0[1][4] 4.5 1.2[5] 1.0 1317 41.16 65 No
GeForce GTX 965M[81][82] January 5, 2015 GM204 28 5200 398 PCIe 3.0 x16 1024:64:32 924 950 5000 30.2 60.4 2048 80 GDDR5 128 12.0[1][4] 4.5 1.2[5] 1.0 1945 60.78 60 [83] Yes
GeForce GTX 970M[84] October 7, 2014 GM204 28 5200 398 PCIe 3.0 x16 1280:80:48 924 993 5012 37.0 73.9 3072
6144		 120 GDDR5 192[85] 12.0[1][4] 4.5 1.2[5] 1.0 2365 73.9 75 Yes
GeForce GTX 980M[86] October 7, 2014 GM204 28 5200 398 PCIe 3.0 x16 1536:96:64 1038 1127 5012 49.8 99.6 4096
8192		 160 GDDR5 256[85] 12.0[1][4] 4.5 1.2[5] 1.0 3189 99.6 100 Yes
GeForce GTX 980 (Notebook)[87] September 22, 2015 GM204 28 5200 398 PCIe 3.0 x16 2048:128:64 1064 1216 7010 72.1 144 4096
8192		 224 GDDR5 256 12.0[1][4] 4.5 1.2[5] 1.0 4612 144 145 Yes
  1. ↑ 1.0 1.1 Shader Processors : Texture mapping units : Render output units
  2. ↑ 2.0 2.1 A maximum of 2 dual-GPU cards can be connected in tandem for a 4-way SLI configuration as dual-GPU cards feature on-board 2-way SLI.
  3. ↑ 3.0 3.1 Pixel fillrate is calculated as the lowest of three numbers: number of ROPs multiplied by the base core clock speed, number of rasterizers multiplied by the number of fragments they can generate per rasterizer multiplied by the base core clock speed, and the number of streaming multiprocessors multiplied by the number of fragments per clock that they can output multiplied by the base clock rate.[25]
  4. ↑ 4.0 4.1 Texture fillrate is calculated as the number of TMUs multiplied by the base core clock speed.
  5. ↑ 5.0 5.1 5.2 Due to the disabling of one or more L2 cache/ROP units without disabling all of the memory controllers attached to the disabled units, the memory has been segmented. One segment must be reading while the other must be writing to achieve the peak speed. Since the peak speed is impossible to reach with pure reads or pure writes, they and their associated buses are split in this table.
  6. ↑ 6.0 6.1 Single precision performance is calculated as 2 times the number of shaders multiplied by the base core clock speed.
  7. ↑ 7.0 7.1 Double precision performance of the Maxwell chips' are 1/32 of single-precision performance.[49][50]

Chipset table

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Comparison table of GeForce 900 Series

Future

After Maxwell, the next architecture is code-named Pascal.[88][89] Nvidia has announced that the Pascal GPU will feature stacked DRAM, unified memory, and NVLink. [88][89] The first GPU based on the Pascal architecture, the GeForce GTX 1080, will be released May 27, 2016.[90]

See also

References

  1. ↑ 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ 5.0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Nvidia Maxwell to be first GPU with ARM CPU in 2013, Guru3d.com
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ 11.0 11.1 11.2 11.3 11.4 11.5 11.6 Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ 12.0 12.1 12.2 Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ 14.0 14.1 14.2 http://international.download.nvidia.com/geforce-com/international/pdfs/GeForce_GTX_980_Whitepaper_FINAL.PDF
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ 24.0 24.1 24.2 Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ 39.0 39.1 39.2 39.3 Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ 40.0 40.1 http://international.download.nvidia.com/geforce-com/international/images/nvidia-geforce-gtx-980-ti/nvidia-geforce-gtx-980-ti-directx-12-advanced-api-support.png
  41. ↑ 41.0 41.1 Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ 42.0 42.1 Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ 43.0 43.1 43.2 Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  76. ↑ NVIDIA™ GeForce GT 945A (1GB GDDR5) user-selectable by application via NVIDIA Control Panel http://store.hp.com/us/en/ContentView?catalogId=10051&langId=-1&storeId=10151&eSpotName=Sprout-Pro#!
  77. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  78. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  79. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  80. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  81. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  82. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  83. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  84. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  85. ↑ 85.0 85.1 Lua error in package.lua at line 80: module 'strict' not found.
  86. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  87. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  88. ↑ 88.0 88.1 Lua error in package.lua at line 80: module 'strict' not found.
  89. ↑ 89.0 89.1 Lua error in package.lua at line 80: module 'strict' not found.
  90. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links


Retrieved from "https://infogalactic.com/w/index.php?title=GeForce_900_series&oldid=723089422"