-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tray icons -> GPU history not working anymore from 3.1.24298 in WIN11 #2343
Comments
Unable to find any issues or changes to GPU History. You might need to check if Windows Update installed a graphics driver update. |
GPU History is unavailable because:
You have two options:
or
|
The |
If it still doesn't work then you have some sort of system issue. Resetting the graphics driver by using DDU might fix the issue, after the system reboots just re-install the graphics driver: https://www.wagnardsoft.com/content/Download-Display-Driver-Uninstaller-DDU-18089 |
I can reproduce it on one of my laptops witn Win10 and Intel 620 graphic card. Latest driver for Intel graphic card is installed, and I see the information about load of graphic cores (3d, decoding, encoding, etc. - 12 cores at all) in Task Manager. |
You have a different issue. The Windows kernel has a blocklist of Intel graphics devices and doesn't allow GPU performance counters for Intel graphics cards. You'll need to change the |
Tried to set EnableGpuPerformanceCounters to 0 and restart SI - no changes, still no graphic devices are present, ang all GPU tray icons shown as (unavailable). |
Passing by quickly: when you have systray issues, sometimes emptying cache can help (especially if paths change): |
@Nojevah we have problems getting the information from hardware, not showing it in tray. Information is unavailable even in options window. |
Brief description of your issue
Tray icons -> GPU history not working anymore from 3.1.24298 in WIN11
It's work fine in 3.0.7660 version.
Steps to reproduce (optional)
Expected behavior (optional)
No response
Actual behavior (optional)
No response
Environment (optional)
The text was updated successfully, but these errors were encountered: