IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
115 stars 3 forks source link

GPU Clock Speed is Capped at 300MHz After Launching Microsoft Edge in Application Guard with "Advanced graphics" enabled in Windows Security on First Boot #251

Closed willamettefour closed 1 year ago

willamettefour commented 1 year ago

Checklist [README]

Application [Required]

Microsoft Edge (running in Application Guard)

Processor / Processor Number [Required]

i5-12490F

Graphic Card [Required]

ASRock ARC A770

GPU Driver Version [Required]

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

intel_ssu.txt

Description and steps to reproduce [Required]

Launching Microsoft Edge in Application Guard with "Advanced graphics" enabled in Windows Security on first boot causes the GPU clock speed to be capped at 300MHz. Increasing the voltage, power limit, or performance boost sliders don't fix the issue. GPU clocks return to normal after hibernating, sleeping, or shutting down and starting back up with Fast Startup enabled. The issue doesn't occur when "Advanced graphics" is disabled. The power plan doesn't seem to matter, and the attached video was tested using the High Performance power plan.

https://user-images.githubusercontent.com/94886283/220433421-e9362bde-c752-4cf9-b462-d25335fab9e6.mp4

Device / Platform

No response

Crash dumps [Required, if applicable]

No response

Application / Windows logs

No response

IntelSupport-Rozilah commented 1 year ago

hi @willamettefour , Thanks for contacting Intel, we will start to verify the issue once our system is ready. Stay tuned!

IntelSupport-Rozilah commented 1 year ago

hi @willamettefour, The case has been verified on our side and we are able to reproduce it with our configurations as below: Processor Name: Intel(R) Core(TM) i7-12700K Driver version: 31.0.101.4125 We will be working on a fix. I want to give you a heads-up that the fix may take 3 to 6 months to be included. Please do not close the case until the fix is done.

willamettefour commented 1 year ago

I don't know if newer drivers or Windows updates fixed the issue, but I no longer experience the problem with driver version 4575.

IGCIT commented 1 year ago

thanks @willamettefour for the update, closing as fixed :)