Latest Intel Graphics Driver for Windows 11

New Intel Arc & Iris Xe Beta graphic DCH driver 31.0.101.5444 version released. See first post for more details.

Almighty1 said:

30.0.100.9922 was either causing my screen to go black with the blacklight on or ever since October 5, 2021 when Windows 11 officially was released, I never did a thing to the Windows 11 22000.194 I had installed, it just locks up the system solid. So installed 30.0.100.9894 using the installer and same problem too.

Click to expand...

Never update a driver that works. If you have an issue with it, then grabbing a new one might resolve it. When it works, leave it well enough alone.

NormanF said:

Never update a driver that works. If you have an issue with it, then grabbing a new one might resolve it. When it works, leave it well enough alone.

Click to expand...

Thanks, but no thanks! Much to the contrary, I'll just continue to follow the advice that Greg Carmack (Microsoft MVP 2010-2020 and well-known for his many helpful contributions on SevenForums in a past that may be forgotten by many, but not forgotten by me) has repeatedly given about this particular subject over the years. That is, do not underestimate the importance of keeping the graphics driver up-to-date, which tends to be fairly critical indeed, due to the common observation that doing so can help to prevent bumping into all sorts of problems that, even though these problems might look like they are unrelated to the graphics driver being outdated, very much can be attributed to running an outdated graphics driver. So, update it, and, only roll back to an older version of the graphics driver if the latest version is causing problems (or to find out if the problems that you are experiencing are caused by the lastest version).

Intel® Arc™ & Iris® Xe Graphics 31.0.101.5445 (WHQL Certified)​

NormanF said:

Never update a driver that works. If you have an issue with it, then grabbing a new one might resolve it. When it works, leave it well enough alone.

Click to expand...

Nah - just make image backups and keep drivers up to date.

NormanF said:

Never update a driver that works. If you have an issue with it, then grabbing a new one might resolve it. When it works, leave it well enough alone.

Click to expand...

I always keep my drivers bang up to date and don't have issues with anything.

Intel® Arc™ & Iris® Xe Graphics 31.0.101.5448 (WHQL Certified)​

Intel Arc & Iris Xe Beta graphic DCH driver 31.0.101.5518

Gaming Highlights:
Intel® Game On Driver support on Intel® Arc™ A-series Graphics GPUs and Intel® Core™ Ultra with built-in Intel® Arc™ GPUs for:

• Ghost of Tsushima DIRECTOR’S CUT
• Homeworld 3

Fixed Issues:
Intel® Arc™ A-Series Graphics Products:

• Dragon’s Dogma 2* (DX12) may experience lower than expected performance.

Intel® Core™ Ultra with built-in Intel® Arc™ GPUs:

• Dead Space* (DX12) may experience lower than expected performance.

Intel® Arc™ Control Fixed Issues:

• Endurance Gaming Power Options per application may not show correct status in Arc Control with on Intel® Core™ Ultra with built-in Intel® Arc™ GPUs

Click to expand...

Here are the known bugs in this update:

Intel® Arc™ A-Series Graphics Products:

• No Rest for the Wicked* (DX11) may experience intermittent application crash during gameplay.
• Enshrouded* (VK) may experience application crash during gameplay.
• Doom Eternal* (VK) may exhibit intermittent flickering corruptions in game menu and during gameplay.
• PugetBench* Extended Preset Benchmark may fail to complete on certain Adobe Premiere Pro* Processing Tests.
• Topaz Video AI* may experience errors when using some models for video enhancement.

Intel® Core™ Ultra with built-in Intel® Arc™ GPUs: Avatar:

• Frontiers Of Pandora* (DX12) may experience a crash during game loading.
• Uncharted: Legacy of Thieves Collection* (DX12) may experience an application crash on loading to gameplay.
• Suicide Squad: Kill the Justice League* (DX12) may exhibit corruption on shadows during gameplay.
• PugetBench* Extended Preset Benchmark may fail to complete on certain Adobe Premiere Pro* Processing Tests.
• Blender* may experience an application crash while rendering some scenes on certain system memory configurations.
• Topaz Video AI* may experience errors when using some models for video enhancements.
• Procyon AI* may experience an application crash while running benchmark with precision float32.

Intel® Core™ Processor (12th -14th Generation) Products:

• Dragon Quest X Online* (DX9) may experience sporadic application crash during gameplay

Click to expand...

Intel Arc & Iris Xe Graphics - Windows 31.0.101.5522 (WHQL Certified)​

Intel Arc & Iris Xe Graphics - Windows 31.0.101.5534 (NON WHQL Certified)​

​

Intel 7th-10th Gen Processor Graphics - Windows 31.0.101.2128 (WHQL Certified)​

Intel Arc & Iris Xe Graphics - Windows 31.0.101.5590 (WHQL Certified)​

hdmi said:

Thanks, but no thanks! Much to the contrary, I'll just continue to follow the advice that Greg Carmack (Microsoft MVP 2010-2020 and well-known for his many helpful contributions on SevenForums in a past that may be forgotten by many, but not forgotten by me) has repeatedly given about this particular subject over the years. That is, do not underestimate the importance of keeping the graphics driver up-to-date, which tends to be fairly critical indeed, due to the common observation that doing so can help to prevent bumping into all sorts of problems that, even though these problems might look like they are unrelated to the graphics driver being outdated, very much can be attributed to running an outdated graphics driver. So, update it, and, only roll back to an older version of the graphics driver if the latest version is causing problems (or to find out if the problems that you are experiencing are caused by the lastest version).

Click to expand...

Yes, and there were some big resource leaks with dwm.exe which was fixed with a newer version as mentioned here:

My black screen problem was a result of upgrading over a bad version that Windows Update was replacing with by default and the problem was gone after Windows Update pushes a newer version that I installed with the most current version as seen here:

NormanF said:

Never update a driver that works. If you have an issue with it, then grabbing a new one might resolve it. When it works, leave it well enough alone.

Click to expand...

Problem solved as the issue was one driver of the drivers (v30.0.100.9922 to be exact) is bad as seen here so upgrades over it has the same problem until one clean installs:

Almighty1 said:

Yes, that part is correct, whenever a new bios is installed including 1.27, load factory defaults and the undervolting is available. What I am talking about is the virtualization that is needed for Windows Subsystem for Linux to work which is ofcourse not just virtualization and it is VBS I am thinking about which breaks Throttlestop and Intel XTU from being about to read the MSR registers (MSR 0x150 to be specific) required for undervolting as I am using Windows Subsystem for Linux, Windows Subsystem for Android and Hyper-V which runs Windows 11 Dev Insiders.

Click to expand...

This is the reason why I didn't continue to use PowerMonkey to undervolt in Windows 11 as mentioned here:
"PowerMonkey works great for undervolting on Windows 11. Windows subsystem for Linux and Windows Subsystem for Android runs fine but when one tries to run another insider channel of Windows 11 under Hyper-V running under Windows 11, it will not work as it requires Secure Boot to be enabled which disables PowerMonkey."

Almighty1 said:

Yes, and there were some big resource leaks with dwm.exe which was fixed with a newer version as mentioned here:

BUG: dwm.exe uses memory leakage with Intel HD Graphics 630

Hi, dwm.exe (Desktop-Window Manager) uses high memory with Intel Intel HD Graphics 630. This problem has been reported before: https://answers.microsoft.com/en-us/windows/forum/all/desktop-windows-manager-dwm-memory-leakage-in/c2968fb0-ee26-4483-9f08-dfa19149cd24...

community.intel.com

Click to expand...

Yeah, I still remember dwm.exe also had frequent skyrocketing CPU usage with lag spikes on Intel 11th gen CPUs with Iris Xe graphics, but no memory leaks or no significant ones at least that I was able to notice on my Medion Akoya S15450 with Core i5-1135G7 while always running the generic driver from Intel. The workaround to this annoying bug was to go in Windows Settings and disable Transparency effects (under Accessibility | Visual effects and also under Personalization | Colors).

Almighty1 said:

My black screen problem was a result of upgrading over a bad version that Windows Update was replacing with by default and the problem was gone after Windows Update pushes a newer version that I installed with the most current version as seen here:

Intel Graphics UHD 630 Driver(s) causing random black screen issues or locks up video randomly

I had been running Windows 11 Professional x64 Build 22000.194 prior to the October 5, 2021 release date on a Dell XPS 15 9570 Laptop with the Intel Core i7-8750H CPU. There were no issues with the drivers prior to October 5, 2021. However, after October 5, 2021, it appears all of the...

community.intel.com

Click to expand...

These days I simply download the installer from the Intel Download Center, then choose to not let it reboot after the install, but also remember to still reboot manually as soon as I no longer am busy doing whatever it was that I was doing. After the reboot, I go in Windows Update and click on Check for updates, which causes it to install the older driver from Microsoft. Then I run the same installer from the Intel Download Center again and choose to let it reboot when it finishes. Doing this effectively prevents Windows Update from automatically installing the older driver from Microsoft again, as this older driver doesn't get removed from the Windows Driver Store when you install the new one. Next, after I remove the old one with DriverStoreExplorer, that's when Windows Update offers it again, which I don't want, and, that's why I always just leave it in there.

hdmi said:

Yeah, I still remember dwm.exe also had frequent skyrocketing CPU usage with lag spikes on Intel 11th gen CPUs with Iris Xe graphics, but no memory leaks or no significant ones at least that I was able to notice on my Medion Akoya S15450 with Core i5-1135G7 while always running the generic driver from Intel. The workaround to this annoying bug was to go in Windows Settings and disable Transparency effects (under Accessibility | Visual effects and also under Personalization | Colors).

These days I simply download the installer from the Intel Download Center, then choose to not let it reboot after the install, but also remember to still reboot manually as soon as I no longer am busy doing whatever it was that I was doing. After the reboot, I go in Windows Update and click on Check for updates, which causes it to install the older driver from Microsoft. Then I run the same installer from the Intel Download Center again and choose to let it reboot when it finishes. Doing this effectively prevents Windows Update from automatically installing the older driver from Microsoft again, as this older driver doesn't get removed from the Windows Driver Store when you install the new one. Next, after I remove the old one with DriverStoreExplorer, that's when Windows Update offers it again, which I don't want, and, that's why I always just leave it in there.

Click to expand...

What I do when there is a new version out which isn't many for 8th gen processors is when I have the time to reboot, I right click on device manager and uninstall and remove the driver files, reboot and repeat until it says Microsoft Basic VGA Driver so it completely removes the older drivers. Then I install the current driver and let Windows Update replace it which usually happens within 30 minutes, then I install the current driver again. I no longer upgrade because should the old version have issues like v30.0.100.9922 did, anything installed over it can have the same problem. Had to use your trick as Windows Update seems to be pushing v27.20.100.9664 and no longer the v30 or v31 anymore.

Almighty1 said:

What I do when there is a new version out which isn't many for 8th gen processors is when I have the time to reboot, I right click on device manager and uninstall and remove the driver files, reboot and repeat until it says Microsoft Basic VGA Driver so it completely removes the older drivers. Then I install the current driver

Click to expand...

This whole procedure AFAIK is what they call "doing a clean install of the Intel graphics driver". Also AFAIK, it is still possible with DDU. How to Use the Display Driver Uninstaller (DDU) to Uninstall an...

Almighty1 said:

and let Windows Update replace it which usually happens within 30 minutes,

Click to expand...

Why wait for it? I use a shortcut that points to explorer.exe ms-settings:windowsupdate and just force it to Check for updates. In fact I do that all the time, to prevent Windows Update from suddenly interfering with my workflow, as Active Hours was invented by someone who very clearly hasn't done any real work for one second in his life.

Almighty1 said:

then I install the current driver again. I no longer upgrade because should the old version have issues like v30.0.100.9922 did, anything installed over it can have the same problem. Had to use your trick as Windows Update seems to be pushing v27.20.100.9664 and no longer the v30 or v31 anymore.

Click to expand...

I don't know if this is Dell's fault or not, as it's been a while since I stopped using my old Kaby Lake (Core i5-7200U) Windows 10 laptop, but I still wouldn't touch Dell with a 10 ft. pole. IMO they should stay in the sewage system of Windows Update.

hdmi said:

This whole procedure AFAIK is what they call "doing a clean install of the Intel graphics driver". Also AFAIK, it is still possible with DDU. How to Use the Display Driver Uninstaller (DDU) to Uninstall an...

Why wait for it? I use a shortcut that points to explorer.exe ms-settings:windowsupdate and just force it to Check for updates. In fact I do that all the time, to prevent Windows Update from suddenly interfering with my workflow, as Active Hours was invented by someone who very clearly hasn't done any real work for one second in his life.

I don't know if this is Dell's fault or not, as it's been a while since I stopped using my old Kaby Lake (Core i5-7200U) Windows 10 laptop, but I still wouldn't touch Dell with a 10 ft. pole. IMO they should stay in the sewage system of Windows Update.

Click to expand...

Yes, but Intel has their own clean install as part of the driver installation except it doesn't clean all traces of it. You are right DDU can do it but DDU requires going into safe mode. I wait because I want to watch it happen. Shortcuts don't work for me, otherwise I won't have hundreds of things on my desktop which were more to serve as reminders for things except they never work. LOL. You are right about the active hours thing as I always wanted to set mines literally 24/7/365.

I don't think this is Dell's fault since everyone gets the Intel driver forced down their throats regardless of what brand of machine one has, nVidia drivers don't have this problem. So it's Intel I think as I even gotten forced Intel drivers as well.

I just tried "explorer.exe ms-settings:windowsupdate" from the command prompt which you suggested and you still have to manually click the "Check for Updates" button. There was another command when Windows Beta Insiders had a build that was missing the Check for Updates button which is "USOClient StartInteractiveScan" from KB5029352 Windows 11 Insider Beta 22621.2199 and 22631.2199 - Aug. 18 which actually does the updates checking as well.

maffle said:

@Almighty1 I am honestly shocked seeing that screenshot! Your CPU is throttling due to thermal limit (PROCHOT) at 100°C WTF!? Also what you said that undervolting is not working due to Windows 11 and virtualization enabled is total nonsense, where did you get that information from? Dell disabled undervolting with a bios update, that is why I am still on bios 1.20 that was the lastt bios with undervolting working. There was a trick though to reenable undervolting by going into bios and load one of the two bios or custom defaults not sure anymore which it was you need to try. PKG power = SOC power. Your CPU is burning at 45W at just 35% load at 100°C also with speedshift off, that is terrible. No other words. Also my god! CPU voltage of 1.25V! These are my settings for normal usage where I want to run it fan less limiting at 22w with undervolt. Windows 11, virtualization on, bios 1.20. Also two cores at 100° and the other at 90°c shows your heat-spreader is not properly connected anymore to the CPU.

Click to expand...

As a update, thanks for the comments but just like you not wanting to try different drivers. It was a pain in the you know where to type with a broken keyboard as it was skipping input and lagging even though only the "A" key was broken. As I mentioned, undervolting does not work for me because I am using Hyper-V to run Windows Canary which is why PowerMonkey works for that to undervolt except that due to the SecureBoot requirement. I have undervolting working with all BIOSes which includes v1.20.0, v121.0, v1.22.1, v1.23.0, v1.24.0, v1.25.0, v1.26.0 and currently on v1.27.0. As for the temps and such, you do know that each CPU is not 100% the same. Some are made better and have lower temps and also lower voltages, same reason for some Intel chips why people wanted the ones made in Costa Rica. Even Dell XPS 15 9570's are all different as this is the first time I literally removed everything except the display and this is what I can tell you after replacing the keyboard, battery, fans directly with parts from Dell and also the thermal interface material with genuine Honeywell PTM7950 Phase Changing 0.25mm thermal pad (turns to liquid at 45C and stays solid at 45C):
1) CPU and GPU could have different specs on what it can tolerate
2) There are motherboards and heatsinks that have 5 screws which I am sure is better and there are ones with 4 screws, I have the later as seen below:

3) The fans can be different specs with the exact same part numbers:
Left Fan: Original Dell Part #008YY9 Delta 4.46CFM
New Dell Part #008YY9 FCN 4.6CFM
Right Fan: Original Dell Part #0TK9J1 Delta 4.37CFM
New Dell Part #0TK9J1 FCN 5.2CFM
So obviously the replacements have higher airflow.
4) I am using the Windows Ultimate Performance Power Plan which you may not as each day, I use it to watch tens of millions in investments which makes me hundreds of thousands, all in US$ per day so even right now, idle, I am pushing 535 processes a time:

5) I tried different thermal interface materials before which includes SYY157 and questionable Honeywell 0.2mm PTM7950 Phase Changing Pads (don't know if they are genuine) which was applied correctly but this time replaced it with LTT store sold genuine Honeywell 0.25mm PTM7950 Phase Changing pads, doing the GPU was easy but doing the CPU took 3 times and each time the material got torn so there were holes so I had to use some of the ones from the first two times to patch the areas.

But anyways, here are the current results which is what matters as I had never seen this low temperatures before especially the minimum, current and maximum, remember I am pushing the CPU to the max with the higher wattages and everything.
Before:

After:

With that said, the Metal standoff under the screw in the front center for the fan on the right which is actually the left fan broke off the motherboard as it seems the adhesive which is electrically conductive as I tested for continuity using a multimeter with what is remaining on the motherboard side broke so I am trying to figure out where to find electrically conductive adhesive that will work and be strong enough so the fan is now missing that screw to hold it down which I am sure is used for grounding.