PAIR version or commit
0.1.1
Affected component
Desktop application — local node performance metrics / Windows GPU detection
Environment
- OS: Windows 11 25H2, build 26200.9445
- CPU: AMD Ryzen 7 9800X3D
- Discrete GPU: one physical NVIDIA GeForce RTX 5070 Ti, 16 GB VRAM
- NVIDIA driver: 610.74
- Integrated graphics: AMD Radeon(TM) Graphics, also listed separately by PAIR
Steps to reproduce
- Install and launch PAIR 0.1.1 on this system.
- Open the Overview tab.
- Expand the local node's performance metrics using the chart icon.
- Inspect the GPU entries.
The issue was first noticed after installation and was still present during a subsequent inspection of the running application.
Expected behavior
The local node should show a single entry for the physical RTX 5070 Ti. The AMD integrated GPU may appear as a separate entry.
Actual behavior
PAIR shows two entries named NVIDIA GeForce RTX 5070 Ti, each reporting a total VRAM capacity of 15.6 GB.
During inspection, the first entry showed GPU activity and allocated VRAM, while the second showed 0% usage and 0 B allocated VRAM. The AMD integrated GPU appeared as a third entry.
This makes the local node appear to contain two RTX 5070 Ti GPUs. Whether this also affects scheduling or other resource calculations has not been tested.
Sanitized logs or screenshots
Original screenshot:
NVIDIA's diagnostic tool reports only one NVIDIA GPU:
> nvidia-smi --query-gpu=index,name,driver_version,memory.total,pci.bus_id --format=csv
index, name, driver_version, memory.total [MiB], pci.bus_id
0, NVIDIA GeForce RTX 5070 Ti, 610.74, 16303 MiB, 00000000:01:00.0
A read-only inspection of HKLM\SOFTWARE\Microsoft\DirectX found two entries with the same NVIDIA GPU description but different AdapterLuid values:
Description AdapterLuid (decimal)
NVIDIA GeForce RTX 5070 Ti 96749
NVIDIA GeForce RTX 5070 Ti 158088
Investigation notes
The Windows GPU detection code in v0.1.1 enumerates DXGI adapters and uses DirectX registry AdapterLuid values to filter out nonphysical adapters.
Since both NVIDIA adapter IDs are present in the registry on this system, registry membership alone would not distinguish them if DXGI enumerates both. This is a possible explanation for the duplicate, not a confirmed root cause: the raw DXGI adapter list has not yet been captured, and the origin of the second registry entry is unknown.
The next diagnostic step would be to compare the adapters returned by DXGI with the physical device inventory. Any fix should preserve support for systems with two genuine GPUs of the same model.
Confirmations
PAIR version or commit
0.1.1
Affected component
Desktop application — local node performance metrics / Windows GPU detection
Environment
Steps to reproduce
The issue was first noticed after installation and was still present during a subsequent inspection of the running application.
Expected behavior
The local node should show a single entry for the physical RTX 5070 Ti. The AMD integrated GPU may appear as a separate entry.
Actual behavior
PAIR shows two entries named NVIDIA GeForce RTX 5070 Ti, each reporting a total VRAM capacity of 15.6 GB.
During inspection, the first entry showed GPU activity and allocated VRAM, while the second showed 0% usage and 0 B allocated VRAM. The AMD integrated GPU appeared as a third entry.
This makes the local node appear to contain two RTX 5070 Ti GPUs. Whether this also affects scheduling or other resource calculations has not been tested.
Sanitized logs or screenshots
Original screenshot:
NVIDIA's diagnostic tool reports only one NVIDIA GPU:
A read-only inspection of
HKLM\SOFTWARE\Microsoft\DirectXfound two entries with the same NVIDIA GPU description but differentAdapterLuidvalues:Investigation notes
The Windows GPU detection code in v0.1.1 enumerates DXGI adapters and uses DirectX registry
AdapterLuidvalues to filter out nonphysical adapters.Since both NVIDIA adapter IDs are present in the registry on this system, registry membership alone would not distinguish them if DXGI enumerates both. This is a possible explanation for the duplicate, not a confirmed root cause: the raw DXGI adapter list has not yet been captured, and the origin of the second registry entry is unknown.
The next diagnostic step would be to compare the adapters returned by DXGI with the physical device inventory. Any fix should preserve support for systems with two genuine GPUs of the same model.
Confirmations