Intel
Rules
-
Be civil. Uncivil language, slurs, and insults will result in a ban. If you can't say something respectfully, don't say it at all.
-
No Unoriginal Sources, Referral links or Paywalled Articles.
-
All posts must be related to Intel or Intel products.
-
Give competitors' recommendations only where appropriate. If a user asks for Intel only (i.e. i5-12600k vs i5-13400?) recommendations, do not reply with non-Intel recommendations. Commenting on a build pic saying they should have gone AMD/Nvidia is also inappropriate, don't be rude. Let people enjoy things.
-
CPU Cooling problems: Just like 95C is normal for Ryzen, 100C is normal for Intel CPUs in many workloads. If you're worried about CPU temperatures, please look at reviews for the laptop or CPU cooler you're using.
view the rest of the comments
This has been happening for ages and while I blamed Windows initially, I highly suspect it's an Intel issue as it doesn't happen with NVIDIA (neither with AMD) dedicated GPUs.
I've gone down that rabbit hole a few times and I'm aware of two methods to avoid that. The first is to let Windows Update install the old OEM driver, then you install the new one on top without removing the previous driver (e.g. do not check the "perform clean install" button on Intel installer, nor use DDU).
The second method is using DDU to remove all precious drivers, then install the most recent one from Intel without internet (to prevent Windows Update to auto download the OEM driver before you can act), and, after that, restore your connection and quickly run
wushowhide.diagcab
(can't link it right now but it's easy to find, just Google it) to hide the OEM driver before Windows Update downloads/installs it. Beware that feature updates normally reset the list of hidden updates, so you'll need to do that again whenever a big update (like 23H2) drops...