Most Vulkan applications begin by enumerating all devices in the system and selecting one or more based on their capabilities. Currently, the NVIDIA driver must power on GPUs to discover their capabilities during this enumeration phase. The engineering team is investigating methods to perform these operations without powering on the GPU, but we cannot commit to an ETA for such a solution at this time.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| GPU randomly fails to wake up from D3Cold | 2 | 406 | October 18, 2024 | |
| 570 release feedback & discussion | 659 | 52473 | March 5, 2026 | |
| How to deal with nvidia-modprobe when switching between nvidia/nouveau | 9 | 9935 | December 30, 2023 | |
| NVIDIA driver 440.44 / Vulkan vulkaninfo reports too many GPUs | 3 | 881 | October 12, 2021 | |
| vulkan failed to initialize with 440.36 on ubuntu 18.04 | 8 | 5156 | October 12, 2021 | |
| [Critical Bug] RTX 5070 Ti (Mobile) - Missing nvidia_icd.json in WSL2 causes Vulkan initialization failure on Driver 591.86 | 4 | 233 | March 16, 2026 | |
| Crash on Wayland with Vulkan apps | 11 | 918 | March 7, 2024 | |
| Vulkaninfo failure when using cgroups to limit GPUs on CUDA11.2 driver | 1 | 1400 | April 22, 2021 | |
| Hybrid: Nvidia MX450 constantly falls off the bus (Xid 79 error) | 0 | 58 | February 10, 2026 | |
| VK_KHR_present_{id,wait} causes device loss on Nvidia 525.60.11 on PRIME setup | 5 | 2661 | March 25, 2023 |