You might see the following symptoms when memory exhaustion occurs on vGPU profiles with 512 MB or less of framebuffer:
The root cause is a known issue associated with changes to the way that recent Microsoft operating systems handle and allow access to overprovisioning messages and errors. NVIDIA is working closely with Microsoft to resolve these issues. If your systems are provisioned with enough framebuffer to support your use cases, you should not encounter these issues.
A 512-MB framebuffer is very small. If your systems are provisioned with 512 MB or less of framebuffer, the multiple demands made in a virtualized environment can cause memory exhaustion, for example:
To reduce the probability of users encountering issues, NVENC has been disabled for 512 MB and smaller framebuffers in the GRID 4.0 (August 2016) release for protocols such as VMware Blast Extreme and Citrix HDX/ICA.
This issue is described in the "Known Issues" section of the driver release notes for the affected hypervisors for the GRID 4.0 (August 2016) release:
Always read the lists of known issues and resolved issues in the driver release notes for each release for your hypervisor.
To minimize the risk of users encountering memory exhaustion issues, NVIDIA has disabled NVENC on profiles with 512 MB or less of framebuffer in the GRID 4.0 (August 2016 release). Application GPU acceleration remains fully supported and available for all profiles, including profiles with 512 MB or less of framebuffer. NVENC support from both Citrix and VMware is a recent feature and, if you are using an older version, you should experience no change in functionality.
To avoid memory exhaustion issues, use these workarounds and solutions:
Monitoring your framebuffer usage can help you select the correct size of framebuffer for your environment to avoid memory exhaustion. If you are experiencing issues, monitoring your framebuffer usage can help you assess whether these issues are caused by memory exhaustion.
You can get information about how to monitor framebuffer usage from the NVIDIA Support knowledge base by:
Several commercial and free tools that can monitor framebuffer usage are available. For example, Jeremy Main's free GPUProfiler tool is available on GitHub.
In Microsoft Windows 10, the demands on graphical resources such as GPU framebuffer and other system resources has significantly increased compared to older OS releases. As a result, you might find that a 512 MB framebuffer is inappropriate for your Windows 10 workload and that a profile with 1 GB of framebuffer is more appropriate.
In response to the increased demands by Windows 10 on system resources, Citrix and VMware have published tools and configuration advice to help users reduce Windows 10 resource usage.
If you are an NVIDIA customer with support and believe that you are encountering issues as a result of frame buffer memory exhaustion, log in to the NVIDIA Support Enterprise Services site to raise a support case, referencing issue 200130864.
NVIDIA GRID vGPU
GRID vGPU profiles that have 512 Mbytes or less of frame buffer:
VMware Horizon and ESXi
Citrix XenDesktop and XenServer
Users are most likely to encounter this issue if using:
This Web site contains links to Web sites and third-party tools controlled by parties other than NVIDIA. NVIDIA is not responsible for and does not endorse or accept any responsibility for the contents or use of these third party Web sites or tools. NVIDIA is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by NVIDIA of the linked Web site. It is your responsibility to take precautions to ensure that whatever tools or information you select for your use is free of viruses or other items of a destructive nature.