[Bug]: Duplicate RTX 5070 Ti entry in performance metrics on Windows 11
維護者通常 2 天內回覆
@ckelseynv 已經在處理了。
開始於 2026年9月18日。
評估
這個 Issue 還沒有評估資料。
描述
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
- I searched existing issues for duplicates.
- This is not a security vulnerability.
- I agree to follow the Code of Conduct.
- 主要語言
- Go
- 星號
- 1.6k
- 分支
- 277
- 平均合併
- 4 天 14 小時
- 30 天內合併 PR
- 31
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
NVIDIA/Personal-AI-Router 的其他 Issue
-
難度 4/5 1-2 天 新手友好度 18/100
NVIDIA/Personal-AI-Router#175 · 1 則留言 ·
維護者通常 2 天內回覆
-
難度 5/5 一週以上 新手友好度 20/100
NVIDIA/Personal-AI-Router#165 ·
維護者通常 2 天內回覆
-
bug
難度 4/5 3-5 天 新手友好度 46/100
NVIDIA/Personal-AI-Router#164 ·
維護者通常 2 天內回覆
-
enhancement
難度 4/5 一週以上 新手友好度 12/100
NVIDIA/Personal-AI-Router#162 ·
維護者通常 2 天內回覆
-
enhancement
難度 4/5 3-5 天 新手友好度 25/100
NVIDIA/Personal-AI-Router#154 · 1 則留言 ·
維護者通常 2 天內回覆
查看 NVIDIA/Personal-AI-Router 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 76/100
keyxmakerx/Chronicle#1469 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 75/100
Gentleman-Programming/gentle-ai#5565 · 1 則留言 ·
維護者通常 1 天內回覆
-
bug frontend grammar sev-3
難度 2/5 1-3 小時 新手友好度 63/100
-
connector docs good first issue
難度 2/5 1-3 小時 新手友好度 72/100
soma-intelligence/open-health-sync#134 ·
維護者通常 1 天內回覆
-
bug frontend
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 3 天內回覆