Iris Xe GPU Driver Crash with multiple Electron/Chrome-based apps?

When I run multiple apps based on Chrome/Chromium/Electron, they randomly lock up the entire windows UI. I first noticed this while using Discord while having YouTube tabs up and flipping between tabs or between channels in Discord.

When this happens (very frequently, happens roughly every 5 minutes), the entire Windows 10 UI hangs and no longer updates with only the mouse cursor moving but not seemingly unable to interact with anything. Alt+Tab, Ctrl+Alt+Del – nothing works.

Sleeping then unsleeping recovers responsiveness and reveals that all mouse/keyboard/UI operations you were performing were actually going through just not visible.

I am assuming this is some kind of Intel Iris Xe driver bug/crash just from gut, but IMO this is a real show-stopper because many Electron-based apps don’t even have a preference / menu item for disabling the hardware acceleration and more and more apps are becoming Electron-based (VSCode, BoostNote, Discord, Web Browsers, etc.) so only being able to run a single one of those apps at a time is very bad.

For completeness, I’m running:
Chrome 95.0.4638.69
Discord Stable 104276

The problem happens with any app running Electron though, VSCode, BoostNote, etc.

Edit: I set up this laptop with the driver pack, I have now installed the latest Intel Iris Xe Graphics driver – 30.0.101.1069 (from 11/2) – I will report if this resolves the issue. For reference, the driver included in the pack was 27.20.100.9565 (from 4/29)

Edit 2: It did not resolve the issue – if anything, it’s worse and happens faster.

Does nobody else have issues with this? I’m starting to think there’s something defective with my Intel CPU and/or motherboard in this thing (?)

I agree about that being a show-stopper. Unfortunately, I can only say that I am unable to reproduce this issue on Windows 11, which I know isn’t very helpful.

May I ask whether this is a new Windows installation?

One basic troubleshooting idea: could you try completely uninstalling your graphics drivers, then reinstalling them with the driver pack?

Maybe try opening Event Viewer and see if there are any relevant critical or error events?

This was a brand new Windows 10 installation (wanted to start fresh)

I did also just get a blue screen / bug check, and this was a fresh boot, started only Chrome, started a single YouTube video, and it started becoming very unresponsive/laggy for about 2 minutes before crashing.

The faulting component was:
MODULE_NAME: dxgmms2

Here is what Event Viewer shows for it:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffab0808683000, 0x0000000000000000, 0xfffff80a4e62b295, 0x000000000000000c). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 5c3c8c5c-945a-41d9-9d55-0dad3abef29f.

I don’t see anything else relevant in event viewer sadly.

I opened the crash dump in WinDbg to get some additional details

It looks like some memory management stuff? I will run some extensive RAM testing on this machine.

I will also revert to the driver in the pack since the new one isn’t helping.

1 Like

I’m fairly confident that the memory is solid – ran both memtest86 for 24 hours+ and a well-regarded in-OS memory testing tool for another 12.

ramtest_pkQpLojOst

Well, that’s a graphics driver file.

We’ve already fussed with drivers enough. Unless someone with more expertise chimes in, here’s what I’d recommend, if you’re up for it:

  1. Create a minimal, reproducible (in theory) example of the behavior by reinstalling Windows once more, the framework drivers, and the minimum number of apps necessary to reproduce the behavior.
  2. If the issue doesn’t occur, then you can determine the cause by only making one change at a time. If the issue occurs again, contact Framework Support via the support form. I imagine that taking these steps would make things easy for support.

Or just use the contact form straightaway.

I think I may have fixed part of the problem (not the bluescreen part, I have gotten 2 or 3 of those, but at least the freezing part) – This is indeed an Intel Iris Xe GPU driver issue being caused by the panel not being refreshed anymore from the power saving feature called ‘Panel Self Refresh’. Here is how to disable it: How to Enable and Disable Panel Self Refresh

Edit: Nevermind – sadly it started doing it again even with panel self-refresh off

You didn’t say, but I think I better not assume: Memtest86 ran for 24 hours+… How many completed loop is that? And they all completed without error, right?

We previously had a user who misread the text output…and thought his memory was OK when it in fact failed.

Also, for completeness, what BIOS version are you on? …and which version of Windows 10 are you on? Pro 21H1 / 21H2?

I’m curious, but how are you so sure that it is just electron apps? To me this sounds like memory lock ups.

@2disbetter because it only happens with electron-based / chromium-based apps that have hardware acceleration enabled.

@RandomUser I don’t remember how many cycles it was, but there were definitely no errors, I have ran that tool for more than 20 years and have seen my fair share of RAM issues in the past. Memory is ruled out at this point IMO.

I am on Windows 10 1803 with BIOS 3.06 - I need this older version of Windows for a variety of reasons. One of those reasons is that Microsoft broke things in later revisions of Windows that makes some of my hardware not work in later revisions. My NVIDIA and AMD GPU desktop machines don’t have this problem in 1803 and even my previous laptop with AMD 4500U on-chip graphics also does not have this problem. Upgrading from 1803 is not really an option for me, though I might install the latest revision in order to test/verify if it still happens in it.

That’s good. Ruling the RAM out makes it a lot easier. However, I am on Windows 10 21H2 and do not have issues with electron apps or Chromium based browsers.

I briefly looked if you already mentioned this, but I don’t think so: Are you using the Framework supplied drivers? Specifically the Intel XE driver?

Test out 21H1 and see if there’s any difference. Technology timeline certainly comes into play…and tigerlake wasn’t there when 1803 was released.

In fact, Intel doesn’t seem to support Xe Graphics going as far back as 1803:

From the readme:
Release Version: Planned Release

Driver Version: 30.0.101.1069

Build Date: November 02, 2021

Operating Systems:
Microsoft Windows* 10-64 - October 2018 Update (1809)(RS5)
Microsoft Windows* 10-64 - May 2019 Update (1903)(19H1)
Microsoft Windows* 10-64 - November 2019 Update (1909)(19H2)
Microsoft Windows* 10-64 - May 2020 Update (2004)(20H1)
Microsoft Windows* 10-64 - October 2020 Update (20H2)
Microsoft Windows* 10-64 - May 2021 Update (21H1)
Microsoft Windows* 11

3 Likes

@RandomUser OK I will try 21H1, but I will also try 1809 since I believe it was 1903 that screwed over my hardware.