- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I am posting this because an issue that has been discussed in the Intel community since 2024 is still occurring and there is no confirmed solution.
My system details are:
Laptop: HP OMEN 16
CPU: Intel Core i7-14650HX
GPU: RTX 4060 Laptop GPU
Operating System: Windows 11( 25H2 )
Issue description:
During normal daily usage, when opening Quick Settings using Win + A or by clicking the system tray icons, the system frequently freezes for a short moment exactly when the CPU boosts. During this freeze the mouse cursor and touchpad stop responding and the UI becomes unresponsive. After a short pause everything continues normally.
This does not happen during heavy workloads.
Key observations:
CPU stress tests run without any issues
Gaming performance is stable
There is no thermal throttling
There are no crashes or BSODs
Replacing the device does not resolve the issue
This suggests the freeze happens during rapid CPU boost or power state transitions combined with Windows 11 UI activity, specifically Quick Settings, rather than sustained CPU load.
What is concerning is that this same issue has been reported by multiple users since 2024 across different Intel CPUs and different OEMs. Many community threads end with replies saying the same issue is still happening, but there is no official acknowledgment or solution.
I have tried BIOS updates, Intel graphics driver updates, and power plan adjustments, but the issue persists.
My questions are: @Mike_Intel
Is Intel aware of UI freezes triggered by opening Quick Settings during CPU boost?
Is this a known interaction between Intel power management, Thread Director, and Windows 11 UI?
Are there any upcoming driver, firmware, or scheduler updates planned to address this?
This issue significantly affects daily usability on an otherwise high performance Intel system.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @jeevadani12, thanks for summarizing this so clearly. I’m seeing almost identical behavior on a Lenovo Yoga Pro 9i Gen 10 Aura Edition (Tandem OLED + Intel Arc140T + NVIDIA dGPU) running Windows 11 Pro 25H2.
The freeze only occurs on the first Quick Settings open after cold boot or long sleep. Gaming and stress tests are fine, and both Intel and NVIDIA drivers are fully up to date. On a very similar system without a dGPU (Yoga Pro 7i Gen 10), Quick Settings opens instantly, which suggests the issue is related to multi-GPU initialization combined with Windows Shell / Quick Settings, not hardware failure.
This has already been reported via the Feedback Hub: https://aka.ms/AAzd826. Additional upvotes or comments there may help with prioritization. Some users and even Microsoft have said this issue was “fixed” in 24H2, but it’s clear that it still persists for many systems.
It seems clear that this is a platform-level issue affecting multiple OEMs and Intel CPUs, and not limited to any single device or manufacturer.
For additional user reports and discussion across different laptops and OEMs, see this Reddit thread:
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @jeevadani12, thanks for summarizing this so clearly. I’m seeing almost identical behavior on a Lenovo Yoga Pro 9i Gen 10 Aura Edition (Tandem OLED + Intel Arc140T + NVIDIA dGPU) running Windows 11 Pro 25H2.
The freeze only occurs on the first Quick Settings open after cold boot or long sleep. Gaming and stress tests are fine, and both Intel and NVIDIA drivers are fully up to date. On a very similar system without a dGPU (Yoga Pro 7i Gen 10), Quick Settings opens instantly, which suggests the issue is related to multi-GPU initialization combined with Windows Shell / Quick Settings, not hardware failure.
This has already been reported via the Feedback Hub: https://aka.ms/AAzd826. Additional upvotes or comments there may help with prioritization. Some users and even Microsoft have said this issue was “fixed” in 24H2, but it’s clear that it still persists for many systems.
It seems clear that this is a platform-level issue affecting multiple OEMs and Intel CPUs, and not limited to any single device or manufacturer.
For additional user reports and discussion across different laptops and OEMs, see this Reddit thread:
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page