Advanced Driver Search

«Standard» packages are those that do not require the DCH driver components.

«DCH» (Declarative, Componentized, Hardware Support Apps) refers to new packages preinstalled by OEMS implementing the Microsoft Universal Driver paradigm.

DCH drivers cannot be installed over a standard system, and Standard drivers cannot be installed over a DCH system.

To confirm the type of system you have, locate Driver Type under the System Information menu in the NVIDIA Control Panel.

«WHQL Certified» Windows Hardware Quality Labs testing or WHQL Testing is a testing process which involves running a series of tests on third-party (i.e. non-Microsoft) hardware or software, and then submitting the log files from these tests to Microsoft for review. The procedure may also include Microsoft running their own tests on a wide range of equipment, like different hardware and different Microsoft Windows editions.

«GRD» Game Ready Drivers provide the best possible gaming experience for all major games. From early access through the lifecycle of the game, NVIDIA’s driver team continues to exhaustively test all major milestones so they can optimize performance, maximize stability, and perfect overall gameplay functionality.

«SD» Studio Drivers provide the best possible experience for key major creative applications. NVIDIA does extensive testing which focuses on the top creative applications and ensures the highest levels of performance, stability, and functionality are provided.

«NFB / QNF» New Feature Branch (NFB) [formerly known as Quadro New Feature (QNF)] driver is from the most recent driver release branch, and provides users with the opportunity to access the latest new features and functionality in between Production Branch releases. It has been tested for workstation environments with reduced product support, and is recommended only for those users who need specific features that are mentioned in the respective release highlights or release notes.

«PB / ODE» Production Branch (PB) [formerly known as Optimal Driver for Enterprise (ODE)] / Studio driver is what most users select for optimal stability and performance. Production Branch drivers offer ISV certification, long life-cycle support, and access to the same functionality as corresponding Studio Drivers of the same version.

«PB / LLB» Production Branch (PB) [formerly known as Linux Long Lived Branch (LLB)] Production Branch Linux drivers provide ISV certification and optimal stability and performance for Unix customers. This driver is most commonly deployed at enterprises, providing support for the sustained bug fix and security updates commonly required.

«NFB / SLB» New Feature Branch (NFB) [formerly known as Linux Short Lived Branch (SLB)] New Feature Branch Linux drivers provide early adopters and bleeding edge developers access to the latest driver features before they are integrated into the Production Branches.

Расширенный поиск драйвера

«Стандартными» пакетами являются те, которые не требуют компонентов драйверов DCH.

«DCH» ( Декларативные, Компонентные, Аппаратные приложения для поддержки) – это новые пакеты, которые предварительно устанавливаются OEM-провайдерами и включают универсальный драйвер Microsoft.

Драйверы DCH не могут быть установлены со стандартной системой, а стандартные драйверы с системой DCH.

Чтобы подтвердить тип системы, которую вы используете, перейдите в пункт Тип драйвера, который находится ниже меню «Системная информация» на панели управления NVIDIA.

Более подробную информацию можно получить на сайте Новости о разработке драйверов

«WHQL сертификация» Тестирование Windows Hardware Quality Labs, или WHQL, — это процесс тестирования, который включает проведение серии тестов на аппаратном или программном обеспечении третьей стороны (т.е. не Microsoft) и предоставление результатов тестов для оценки компании Microsoft. Процедура может также включать проведение Microsoft собственных текстов на широком спектре оборудования, например, на различном аппаратном обеспечении и с различными выпусками Microsoft Windows.

«GRD» Драйверы Game Ready обеспечивают лучшие игровые возможности во всех популярных играх. Начиная с раннего доступа и на протяжении всего существования игры, команда по разработке драйверов NVIDIA тщательно тестирует все ключевые функции, поэтому драйверы оптимизируют производительность, позволяют добиться максимальной стабильности и отличной функциональности геймплея.

«SD» Драйверы Studio обеспечивают лучшие возможности работы в основных приложениях для профессионального творчества. NVIDIA проводит тщательное тестирование, направленное на проверку функциональности в ведущих приложениях, и гарантирует высочайший уровень производительности, стабильной работы и функциональности.

«NFB / QNF» New Feature Branch (NFB) [Ранее назывался Quadro New Feature (QNF)] из последней серии выпусков драйверов, он обеспечивает новейшие возможности и функции между выпусками драйвера Production Branch. Драйвер был протестирован для рабочих станций с ограниченной поддержкой продукта и рекомендован к использованию только для пользователей, нуждающихся в особых возможностях, которые указаны в соответсвующем разделе «Возможности выпуска».

«PB / ODE» Production Branch (PB) [Ранее назывался Оптимизированный для предприятий драйвер (ODE)] / Studio Большинство пользователей выбирает этот тип драйвера для обеспечения оптимальной производительности и стабильной работы. Драйверы Production Branch оснащены сертификатами ISV, поддержкой всего жизненного цикла и обеспечивают все функции драйверов Studio такой же версии.

«PB / LLB» Production Branch (PB) [Ранее назывались драйверы для Linux с долгосрочной поддержкой (LLB)] Драйверы Production Branch для Linux оснащены сертификатами ISV и обеспечивают оптимальную производительность и стабильность работы для пользователей Unix. Такой драйвер обычно используется в компаниях, обеспечивая постоянные исправления ошибок и стандартные обновления безопасности.

«NFB / SLB» New Feature Branch (NFB) [Ранее назывался Драйвер для Linux с краткосрочной поддержкой (SLB) Драйверы New Feature Branch для Linux предоставляют разработчикам и ранним пользователям доступ к новым функциям до интеграции в драйверы Production Branches.

Nvidia drivers windows server 2016

Release information for all users of NVIDIA virtual GPU software and hardware on Microsoft Windows Server.

1. Release Notes

1.1. NVIDIA vGPU Software Driver Versions

Each release in this release family of NVIDIA vGPU software includes a specific version of the NVIDIA Windows driver and NVIDIA Linux driver.

NVIDIA vGPU Software Version	NVIDIA Windows Driver Version	NVIDIA Linux Driver Version
12.1	461.33	460.32.03
12.0	461.09	460.32.03

All releases in this release family of NVIDIA vGPU software are compatible with all releases of the NVIDIA vGPU software license server.

1.2. Updates in Release 12.1

New Features in Release 12.1

1.3. Updates in Release 12.0

New Features in Release 12.0

Hardware and Software Support Introduced in Release 12.0

• Support for the following GPUs:
  • NVIDIA A100 HGX 80GB
  • NVIDIA A40
  • NVIDIA RTX A6000
• Support for Windows 10 October 2020 Update (20H2) as a guest OS
• Support for SuSE Linux Enterprise Server 15 SP2

2. Validated Platforms

This release family of NVIDIA vGPU software provides support for several NVIDIA GPUs on validated server hardware platforms, Microsoft Windows Server hypervisor software versions, and guest operating systems.

2.1. Supported NVIDIA GPUs and Validated Server Platforms

This release of NVIDIA vGPU software provides support for the following NVIDIA GPUs on Microsoft Windows Server , running on validated server hardware platforms:

• GPUs based on the NVIDIA Maxwellв„ў graphic architecture:
  • Tesla M6
  • Tesla M10
  • Tesla M60
• GPUs based on the NVIDIA Pascalв„ў architecture:
  • Tesla P4
  • Tesla P6
  • Tesla P40
  • Tesla P100 PCIe 16 GB
  • Tesla P100 SXM2 16 GB
  • Tesla P100 PCIe 12GB
• GPUs based on the NVIDIA Volta architecture:
  • Tesla V100 SXM2
  • Tesla V100 SXM2 32GB
  • Tesla V100 PCIe
  • Tesla V100 PCIe 32GB
  • Tesla V100S PCIe 32GB
  • Tesla V100 FHHL
• GPUs based on the NVIDIA Turingв„ў architecture:
  • Tesla T4
  • Quadro RTX 6000 in displayless mode
  • Quadro RTX 6000 passive in displayless mode
  • Quadro RTX 8000 in displayless mode
  • Quadro RTX 8000 passive in displayless mode

  In displayless mode, local physical display connectors are disabled.

• GPUs based on the NVIDIA Ampere architecture:
  • NVIDIA A100 HGX 80GB (supports only compute workloads on Linux with GPU pass through; graphics acceleration is not supported)
  • NVIDIA A100 PCIe 40GB (supports only compute workloads on Linux with GPU pass through; graphics acceleration is not supported)
  • NVIDIA A100 HGX 40GB (supports only compute workloads on Linux with GPU pass through; graphics acceleration is not supported)
  • NVIDIA A40 in displayless mode
  • NVIDIA RTX A6000 in displayless mode

  In displayless mode, local physical display connectors are disabled.

  For a list of validated server platforms, refer to NVIDIA GRID Certified Servers.

  2.1.1. Switching the Mode an NVIDIA A40 or NVIDIA RTX A6000 GPU

  NVIDIA A40 and NVIDIA RTX A6000 GPUs support displayless and display-enabled modes but must be used in NVIDIA vGPU software deployments in displayless mode.

  NVIDIA A40 GPUs are supplied from the factory in displayless mode. However, NVIDIA RTX A6000 GPUs are supplied in a display-enabled mode and your NVIDIA A40 GPU might be in a display-enabled mode if its mode has previously been changed.

  To change the mode of NVIDIA A40 and NVIDIA RTX A6000 GPUs, use the displaymodeselector tool, which you can request from the NVIDIA Display Mode Selector Tool page on the NVIDIA Developer website.

  Only NVIDIA A40 and NVIDIA RTX A6000 GPUs support the displaymodeselector tool. Other GPUs that support NVIDIA vGPU software do not support the displaymodeselector tool and, unless otherwise stated, do not require mode switching.

  2.1.2. Switching the Mode of a Tesla M60 or M6 GPU

  Tesla M60 and M6 GPUs support compute mode and graphics mode. NVIDIA vGPU requires GPUs that support both modes to operate in graphics mode.

  Recent Tesla M60 GPUs and M6 GPUs are supplied in graphics mode. However, your GPU might be in compute mode if it is an older Tesla M60 GPU or M6 GPU, or if its mode has previously been changed.

  To configure the mode of Tesla M60 and M6 GPUs, use the gpumodeswitch tool provided with NVIDIA vGPU software releases. If you are unsure which mode your GPU is in, use the gpumodeswitch tool to find out the mode.

  Only Tesla M60 and M6 GPUs support the gpumodeswitch tool. Other GPUs that support NVIDIA vGPU do not support the gpumodeswitch tool and, unless otherwise stated, do not require mode switching.

  Even in compute mode, Tesla M60 and M6 GPUs do not support NVIDIA Virtual Compute Server vGPU types.

  2.2. Hypervisor Software Releases

  This release supports only the hypervisor software versions listed in the table.

  Microsoft Windows Server 2019

  Windows Server 2019 with Hyper-V role

  Microsoft Windows Server 2016

  Windows Server 2016 1803 with Hyper-V role

  Windows Server 2016 1709 with Hyper-V role

  Windows Server 2016 1607 with Hyper-V role

  Not supported on the following GPUs:

  • NVIDIA A100 HGX 80GB
  • NVIDIA A100 PCIe 40GB
  • NVIDIA A100 HGX 40GB

  Software	Version Supported	Notes

  2.3. Guest OS Support

  NVIDIA vGPU software supports several Windows releases and Linux distributions as a guest OS using GPU pass-through .

  Microsoft Windows Server with Hyper-V role supports GPU pass-through over Microsoft Virtual PCI bus. This bus is supported through paravirtualized drivers.

  Use only a guest OS release that is listed as supported by NVIDIA vGPU software with your virtualization software. To be listed as supported, a guest OS release must be supported not only by NVIDIA vGPU software , but also by your virtualization software. NVIDIA cannot support guest OS releases that your virtualization software does not support.

  NVIDIA vGPU software supports only 64-bit guest operating systems. No 32-bit guest operating systems are supported.

  2.3.1. Windows Guest OS Support

  NVIDIA vGPU software supports only the 64-bit Windows releases listed as a guest OS on Microsoft Windows Server .

  If a specific release, even an update release, is not listed, it’s not supported.

  • Windows Server 2019
  • Windows Server 2016 1607, 1709
  • Windows Server 2012 R2 with patch Windows8.1-KB3133690-x64.msu (not supported on GPUs based on architectures after the NVIDIA Turing architecture)
  • Windows 10 October 2020 Update (20H2) and all Windows 10 releases supported by Microsoft up to and including this release

  2.3.2. Linux Guest OS Support

  NVIDIA vGPU software supports only the 64-bit Linux distributions listed as a guest OS on Microsoft Windows Server .

  If a specific release, even an update release, is not listed, it’s not supported.

  • Red Hat Enterprise Linux 7.7-7.9, 8.0-8.3
  • CentOS 7.6, 7.7, 8.0, 8 (1911)
  • Ubuntu 18.04 LTS
  • Ubuntu 16.04 LTS
  • SUSE Linux Enterprise Server 15 SP2
  • SUSE Linux Enterprise Server 12 SP2

  3. Known Issues

  3.1. 12.0 Only: Sessions freeze when Adobe Premiere with the Adobe Mercury Engine is used

  Description

  Sessions freeze when Adobe Premiere with the Adobe Mercury Engine is used. The session can freeze after 15-20 minutes of use or when a project is being exported.

  Workaround

  Status

  Resolved in NVIDIA vGPU software 12.1

  3.2. 12.0 Only: Issues occur when Blackmagic Design DaVinci Resolve is used

  Description

  Multiple issues, such as application crashes, application instability, and session freezes, occur when Blackmagic Design DaVinci Resolve is used. CUDA error 702 might also be observed.

  Status

  Resolved in NVIDIA vGPU software 12.1

  3.3. NVIDIA vGPU software graphics driver installation fails in Ubuntu guest VMs

  Description

  Installation of the NVIDIA vGPU software graphics driver from a .run file fails in Ubuntu guest VMs that are running Linux kernel version 5.8 or later.

  Version

  Ubuntu 20.04 LTS and 18.04 with Linux kernel version 5.8 or later

  Workaround

  Revert to a Linux kernel version earlier than 5.8.

  Status

  3.4. NVIDIA Control Panel fails to start if launched too soon from a VM without licensing information

  Description

  If NVIDIA licensing information is not configured on the system, any attempt to start NVIDIA Control Panel by right-clicking on the desktop within 30 seconds of the VM being started fails.

  Workaround

  Restart the VM and wait at least 30 seconds before trying to launch NVIDIA Control Panel .

  Status

  3.5. Citrix Virtual Apps and Desktops session corruption occurs in the form of residual window borders

  Description

  When a window is dragged across the desktop in a Citrix Virtual Apps and Desktops session, corruption of the session in the form of residual window borders occurs.

  Version

  This issue affects only Citrix Virtual Apps and Desktops version 7 2003

  Workaround

  Use Citrix Virtual Apps and Desktops version 7 1912 or 2006.

  Status

  Not an NVIDIA bug

  3.6. Remoting solution session freezes with VGPU message 21 failed and VGPU message 14 failed errors

  Description

  The remoting solution session sometimes freezes while a window is being resized. For a Windows guest VM, the error message VGPU message 21 failed is written to the log file on the hypervisor host. For a Linux guest VM, the error messages VGPU message 21 failed and VGPU message 14 failed are written to the log file on the hypervisor host.

  Workaround

  Try resizing the window again.

  Status

  3.7. On Linux, the frame rate might drop to 1 after several minutes

  Description

  On Linux, the frame rate might drop to 1 frame per second (FPS) after NVIDIA vGPU software has been running for several minutes. Only some applications are affected, for example, glxgears . Other applications, such as Unigine Heaven, are not affected. This behavior occurs because Display Power Management Signaling (DPMS) for the Xorg server is enabled by default and the display is detected to be inactive even when the application is running. When DPMS is enabled, it enables power saving behavior of the display after several minutes of inactivity by setting the frame rate to 1 FPS.

  Workaround

  If necessary, stop the Xorg server.

  In a plain text editor, edit the /etc/X11/xorg.conf file to set the options to disable DPMS and disable the screen saver.

  1. In the Monitor section, set the DPMS option to false .
  2. At the end of the file, add a ServerFlags section that contains option to disable the screen saver.
  3. Save your changes to /etc/X11/xorg.conf file and quit the editor.

  Start the Xorg server.

  Status

  3.8. Microsoft DDA fails with some GPUs

  Description

  Microsoft Discrete Device Assignment (DDA) fails with GPUs that have more than 16 GB of GPU memory. After the NVIDIA vGPU software graphics driver is installed in the guest VM, a second display device appears on the GPU and the driver prompts for a reboot. After the reboot, the device disappears and the Microsoft Hyper-V Video device appears.

  This issue occurs because less memory-mapped input/output (MMIO) space is configured for the operating system than the device requires.

  Workaround

  Perform this workaround in a Windows Power Shell window on the hypervisor host.

  Set the upper MMIO space to the amount that the device requires to allow all of the MMIO to be mapped. Upper MMIO space starts at approximately 64 GB in address space.

  mmio-space The amount of MMIO space that the device requires, appended with the appropriate unit of measurement, for example, 64GB for 64 GB of MMIO space.

  The required amount of MMIO space depends on the amount of BAR1 memory on the installed GPUs and the number of GPUs assigned to the VM as follows:

  mmio-space = 2 Лџ gpu-bar1-memory Лџ assigned-gpus

  gpu-bar1-memory The amount of BAR1 memory on one of the installed GPUs. For example, in a server in which eight GPUs are installed and each GPU has 32 GB of BAR1 memory, gpu-bar1-memory is 32 GB. assigned-gpus The number of GPUs assigned to the VM. vm-name The name of the VM to which the GPU is assigned.

  The following example sets the upper MMIO space to 64 GB for the VM named mygpuvm , to which one GPU with 32 GB of BAR1 memory is assigned.

  For more information, see Deploy graphics devices using Discrete Device Assignment on the Microsoft technical documentation site.

  Status

  Not an NVIDIA bug

  3.9. DWM crashes randomly occur in Windows VMs

  Description

  Desktop Windows Manager (DWM) crashes randomly occur in Windows VMs, causing a blue-screen crash and the bug check CRITICAL_PROCESS_DIED . Computer Management shows problems with the primary display device.

  Version

  This issue affects Windows 10 1809, 1903 and 1909 VMs.

  Status

  Not an NVIDIA bug

  3.10. NVIDIA vGPU software graphics driver fails after Linux kernel upgrade with DKMS enabled

  Description

  After the Linux kernel is upgraded (for example by running sudo apt full-upgrade ) with Dynamic Kernel Module Support (DKMS) enabled, the nvidia-smi command fails to run. If DKMS is enabled, an upgrade to the Linux kernel triggers a rebuild of the NVIDIA vGPU software graphics driver. The rebuild of the driver fails because the compiler version is incorrect. Any attempt to reinstall the driver fails because the kernel fails to build.

  When the failure occurs, the following messages are displayed:

  Workaround

  When installing the NVIDIA vGPU software graphics driver with DKMS enabled, specify the —no-cc-version-check option.

  Status

  3.11. Blue screen crash occurs or no devices are found after VM reset

  Description

  If a VM on Microsoft Windows Server with Hyper-V role is reset from the hypervisor host, a blue screen crash (BSOD) occurs on Windows VMs and the nvidia-smi command reports No devices were found on Linux VMs. This issue occurs only on Windows Server 2019 with Tesla T4 GPUs with SRIOV enabled, Quadro RTX 8000 passive GPUs, and Quadro RTX 6000 passive GPUs.

  Workaround

  Contact NVIDIA Enterprise Support for a workaround for this issue, referencing the knowledge base article Workaround for Blue Screen Crashes On Hyper-V DDA With SRIOV-Enabled GPUs . This article is available only to NVIDIA Enterprise Support personnel.

  Status

  Not an NVIDIA bug

  3.12. Publisher not verified warning during Windows 7 driver installation

  Description

  During installation of the NVIDIA vGPU software graphics driver for Windows on Windows 7, Windows warns that it can’t verify the publisher of the driver software. If Device Manager is used to install the driver, Device Manager warns that the driver is not digitally signed. If you install the driver, error 52 ( CM_PROB_UNSIGNED_DRIVER ) occurs.

  This issue occurs because Microsoft is no longer dual signing WHQL-tested software binary files by using the SHA-1 and SHA-2 hash algorithms. Instead, WHQL-tested software binary files are signed only by using the SHA-2 hash algorithm. All NVIDIA vGPU software graphics drivers for Windows are WHQL tested.

  By default, Windows 7 systems cannot recognize signatures that were created by using the SHA-2 hash algorithm. As a result, software binary files that are signed only by using the SHA-2 hash algorithm are considered unsigned.

  For more information, see 2019 SHA-2 Code Signing Support requirement for Windows and WSUS on the Microsoft Windows support website.

  Version

  Workaround

  If you experience this issue, install the following updates and restart the VM or host before installing the driver:

  Status

  3.13. Frame capture while the interactive logon message is displayed returns blank screen

  Description

  Because of a known limitation with NvFBC, a frame capture while the interactive logon message is displayed returns a blank screen.

  An NvFBC session can capture screen updates that occur after the session is created. Before the logon message appears, there is no screen update after the message is shown and, therefore, a black screen is returned instead. If the NvFBC session is created after this update has occurred, NvFBC cannot get a frame to capture.

  Workaround

  Press Enter or wait for the screen to update for NvFBC to capture the frame.

  Status

  3.14. RDS sessions do not use the GPU with some Microsoft Windows Server releases

  Description

  When some releases of Windows Server are used as a guest OS, Remote Desktop Services (RDS) sessions do not use the GPU. With these releases, the RDS sessions by default use the Microsoft Basic Render Driver instead of the GPU. This default setting enables 2D DirectX applications such as Microsoft Office to use software rendering, which can be more efficient than using the GPU for rendering. However, as a result, 3D applications that use DirectX are prevented from using the GPU.

  Version

  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012

  Solution

  Change the local computer policy to use the hardware graphics adapter for all RDS sessions.

  Choose Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment .

  Set the Use the hardware default graphics adapter for all Remote Desktop Services sessions option.

  3.15. A segmentation fault in DBus code causes nvidia-gridd to exit on Red Hat Enterprise Linux and CentOS

  Description

  On Red Hat Enterprise Linux 6.8 and 6.9, and CentOS 6.8 and 6.9, a segmentation fault in DBus code causes the nvidia-gridd service to exit.

  The nvidia-gridd service uses DBus for communication with NVIDIA X Server Settings to display licensing information through the Manage License page. Disabling the GUI for licensing resolves this issue.

  To prevent this issue, the GUI for licensing is disabled by default. You might encounter this issue if you have enabled the GUI for licensing and are using Red Hat Enterprise Linux 6.8 or 6.9, or CentOS 6.8 and 6.9.

  Version

  Red Hat Enterprise Linux 6.8 and 6.9

  CentOS 6.8 and 6.9

  Status

  3.16. No Manage License option available in NVIDIA X Server Settings by default

  Description

  By default, the Manage License option is not available in NVIDIA X Server Settings . This option is missing because the GUI for licensing on Linux is disabled by default to work around the issue that is described in A segmentation fault in DBus code causes nvidia-gridd to exit on Red Hat Enterprise Linux and CentOS.

  Workaround

  This workaround requires sudo privileges.

  If you are licensing a physical GPU for vCS , you must use the configuration file /etc/nvidia/gridd.conf .

  If NVIDIA X Server Settings is running, shut it down.

  If the /etc/nvidia/gridd.conf file does not already exist, create it by copying the supplied template file /etc/nvidia/gridd.conf.template .

  As root, edit the /etc/nvidia/gridd.conf file to set the EnableUI option to TRUE .

  Start the nvidia-gridd service.

  When NVIDIA X Server Settings is restarted, the Manage License option is now available.

  Status

  3.17. Licenses remain checked out when VMs are forcibly powered off

  Description

  NVIDIA vGPU software licenses remain checked out on the license server when non-persistent VMs are forcibly powered off.

  The NVIDIA service running in a VM returns checked out licenses when the VM is shut down. In environments where non-persistent licensed VMs are not cleanly shut down, licenses on the license server can become exhausted. For example, this issue can occur in automated test environments where VMs are frequently changing and are not guaranteed to be cleanly shut down. The licenses from such VMs remain checked out against their MAC address for seven days before they time out and become available to other VMs.

  Resolution

  If VMs are routinely being powered off without clean shutdown in your environment, you can avoid this issue by shortening the license borrow period. To shorten the license borrow period, set the LicenseInterval configuration setting in your VM image. For details, refer to Virtual GPU Client Licensing User Guide .

  Status

  Notices

  Notice

  This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation (“NVIDIA”) makes no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assumes no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality.

  NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice.

  Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete.

  NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document.

  NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage. NVIDIA accepts no liability for inclusion and/or use of NVIDIA products in such equipment or applications and therefore such inclusion and/or use is at customer’s own risk.

  NVIDIA makes no representation or warranty that products based on this document will be suitable for any specified use. Testing of all parameters of each product is not necessarily performed by NVIDIA. It is customer’s sole responsibility to evaluate and determine the applicability of any information contained in this document, ensure the product is suitable and fit for the application planned by customer, and perform the necessary testing for the application in order to avoid a default of the application or the product. Weaknesses in customer’s product designs may affect the quality and reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this document. NVIDIA accepts no liability related to any default, damage, costs, or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this document or (ii) customer product designs.

  No license, either expressed or implied, is granted under any NVIDIA patent right, copyright, or other NVIDIA intellectual property right under this document. Information published by NVIDIA regarding third-party products or services does not constitute a license from NVIDIA to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property rights of the third party, or a license from NVIDIA under the patents or other intellectual property rights of NVIDIA.

  Reproduction of information in this document is permissible only if approved in advance by NVIDIA in writing, reproduced without alteration and in full compliance with all applicable export laws and regulations, and accompanied by all associated conditions, limitations, and notices.

  THIS DOCUMENT AND ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL NVIDIA BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF ANY USE OF THIS DOCUMENT, EVEN IF NVIDIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Notwithstanding any damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms of Sale for the product.

  VESA DisplayPort

  DisplayPort and DisplayPort Compliance Logo, DisplayPort Compliance Logo for Dual-mode Sources, and DisplayPort Compliance Logo for Active Cables are trademarks owned by the Video Electronics Standards Association in the United States and other countries.

  Читайте также:  Данная версия windows не имеет ограничения