Laggy, freezing UI with Linux and Intel UHD 620 #57455

New Issue

Michael Arndt · 2018-10-28T17:44:01+01:00

Michael Arndt commented

2018-10-28 17:44:01 +01:00

System Information
Ubuntu 18.10 (wayland and xorg affected), Intel(R) UHD Graphics 620 (Kabylake GT2)

Blender Version
Broken: 2.80 (sub 27), branch: blender2.8, commit date: 2018-10-28 09:40, hash: 94ab6429bb, type: Release
Worked: 2.79 (sub 0), branch: master, commit date: 2018-03-22 14:10, hash: f4dc9f9d68, type: Release

Also worked on the same machine when Fedora was installed a few days ago, cannot find out exact build of blender 2.8 used though

Short description of error
Complete System is not responsive for several seconds, becomes unresponsive again after a few seconds, eventually freezes.

Exact steps for others to reproduce the error
Start blender, try to orbit around qube in default scene

system-info2.txt

**System Information** Ubuntu 18.10 (wayland and xorg affected), Intel(R) UHD Graphics 620 (Kabylake GT2) **Blender Version** Broken: 2.80 (sub 27), branch: blender2.8, commit date: 2018-10-28 09:40, hash: 94ab6429bbd, type: Release Worked: 2.79 (sub 0), branch: master, commit date: 2018-03-22 14:10, hash: f4dc9f9d68b, type: Release Also worked on the same machine when Fedora was installed a few days ago, cannot find out exact build of blender 2.8 used though **Short description of error** Complete System is not responsive for several seconds, becomes unresponsive again after a few seconds, eventually freezes. **Exact steps for others to reproduce the error** Start blender, try to orbit around qube in default scene [system-info2.txt](https://archive.blender.org/developer/F5274347/system-info2.txt)

Michael Arndt commented

2018-10-28 17:44:01 +01:00

Added subscriber: @Mene

blender-admin commented

2018-10-28 17:44:01 +01:00

#58965 was marked as duplicate of this issue

blender-admin commented

2018-10-28 17:44:01 +01:00

#58417 was marked as duplicate of this issue

blender-admin commented

2018-10-28 17:44:01 +01:00

#58226 was marked as duplicate of this issue

Brecht Van Lommel changed title from ~~Unusable with Ubuntu 18.10~~ to Laggy, freezing UI with Linux and Intel UHD 620

2018-11-30 11:24:49 +01:00

Brecht Van Lommel commented

2018-11-30 11:24:58 +01:00

Added subscribers: @jpritikin, @brita

joshua pritikin commented

2018-11-30 13:14:39 +01:00

Is there any way I can help track down this bug?

Inês Almeida commented

2018-11-30 18:36:15 +01:00

@jpritikin It's already good information that it happens on both Wayland and X11, but only when doing something such as interacting with a menu.
It looks like it could be graphics card related. Unfortunately, that doesn't make it easy for a developer to debug without the same hardware :(
Could you make a short video that shows a freeze?

What about earlier builds of 2.80-to-be? Are those available somewhere?

I think you would have to build Blender yourself.

@jpritikin It's already good information that it happens on both Wayland and X11, but only when doing something such as interacting with a menu. It looks like it could be graphics card related. Unfortunately, that doesn't make it easy for a developer to debug without the same hardware :( Could you make a short video that shows a freeze? > What about earlier builds of 2.80-to-be? Are those available somewhere? I think you would have to build Blender yourself.

Brecht Van Lommel commented

2018-11-30 18:42:56 +01:00

Added subscribers: @Jeroen-Bakker, @fclem, @brecht

Brecht Van Lommel commented

2018-11-30 18:42:56 +01:00

CC-ing the devs who were discussing this on IRC, @Jeroen-Bakker found it's related to round corner drawing.
http://pasteall.org/1395682

CC-ing the devs who were discussing this on IRC, @Jeroen-Bakker found it's related to round corner drawing. http://pasteall.org/1395682

Lewis Toohey commented

2018-11-30 20:52:24 +01:00

Added subscriber: @lewis2e

Lewis Toohey commented

2018-11-30 21:12:02 +01:00

Probably not that helpful, but I also have this exact issue when running Blender 2.80 on my laptop.

Ubuntu 18.10 (Cosmic). Intel HD Graphics 620.

Happy to help with diagnostics if needed.

system-info.txt

Probably not that helpful, but I also have this exact issue when running Blender 2.80 on my laptop. Ubuntu 18.10 (Cosmic). Intel HD Graphics 620. Happy to help with diagnostics if needed. [system-info.txt](https://archive.blender.org/developer/F5771273/system-info.txt)

joshua pritikin commented

2018-11-30 23:00:47 +01:00

Could you make a short video that shows a freeze?

Here you go, https:*youtu.be/QB7cRpAWqv0

it's related to round corner drawing.

If I reverse the patch you linked and recompile, will the bug be gone?

> Could you make a short video that shows a freeze? Here you go, [https:*youtu.be/QB7cRpAWqv0 ](https:*youtu.be/QB7cRpAWqv0) > it's related to round corner drawing. If I reverse the patch you linked and recompile, will the bug be gone?

Clément Foucault commented

2018-11-30 23:50:56 +01:00

@jpritikin It would be nice to know if it fixes the issue in your case.

Brecht Van Lommel commented

2018-12-01 12:59:39 +01:00

Added subscriber: @bvz2000

joshua pritikin commented

2018-12-01 16:32:37 +01:00

It would be nice to know if it fixes the issue in your case.

I am happy to report that the change given in http:*pasteall.org/1395682 solved my issue!

> It would be nice to know if it fixes the issue in your case. I am happy to report that the change given in [http:*pasteall.org/1395682 ](http:*pasteall.org/1395682) solved my issue!

Clément Foucault commented

2018-12-01 20:41:17 +01:00

I reworked the rounded corner drawing d55c269dd1.

If that does not help, I would like you to try P849 on top of latest 2.8 and see if it fixes the problem.

I reworked the rounded corner drawing d55c269dd1. If that does not help, I would like you to try [P849](https://archive.blender.org/developer/P849.txt) on top of latest 2.8 and see if it fixes the problem.

joshua pritikin commented

2018-12-01 21:00:39 +01:00

I reworked the rounded corner drawing d55c269dd1.

The problem still persists.

If that does not help, I would like you to try P849 on top of latest 2.8 and see if it fixes the problem.

The problem still persists. No improvement.

> I reworked the rounded corner drawing d55c269dd1. The problem still persists. > If that does not help, I would like you to try [P849](https://archive.blender.org/developer/P849.txt) on top of latest 2.8 and see if it fixes the problem. The problem still persists. No improvement.

Pablo Dobarro commented

2018-12-01 21:27:48 +01:00

Added subscriber: @PabloDobarro

Jeroen Bakker commented

2018-12-01 21:43:00 +01:00

Hi Clement,

I tested your try, but it didn't fix the issue. I also tested by using just a UNIFORM COLOR shader and I get very bad artifacts like the driverstate gets corrupted.

Issue is introduced by 34b3d6e2f8
Reverting this commit (for now) will solved the problem.

[21:26] hypersomniac: Your fix didn't help. Currently trying to change the vertex shader, but then it seems that the driverstate is not consistent.
[21:31] --> Sanne (~Sanne@164-222-103-86.dynamic.dsl.tng.de) has joined this channel.
[21:31] hypersomniac: https://drive.google.com/file/d/1x8TVHtdfzE26ZyKnicKnZmw9Ltn0qV6P/view?usp=sharing
[21:32] this is when using UNIFORM_COLOR shader,
[21:33] <-- JTa (~Thunderbi@unaffiliated/jta) has left this server (Quit: JTa).
[21:33] with this patch http://pasteall.org/1397437/diff

I have the same results when I minimize the vertex shader of the border drawing. So I will be twiggling around some statements.

Hi Clement, I tested your try, but it didn't fix the issue. I also tested by using just a UNIFORM COLOR shader and I get very bad artifacts like the driverstate gets corrupted. Issue is introduced by https://git.blender.org/gitweb/gitweb.cgi/blender.git/commit/34b3d6e2f88c275032cfec5aacd036cb65d20dc3 Reverting this commit (for now) will solved the problem. [21:26] <atmind> hypersomniac: Your fix didn't help. Currently trying to change the vertex shader, but then it seems that the driverstate is not consistent. [21:31] --> Sanne (~Sanne@164-222-103-86.dynamic.dsl.tng.de) has joined this channel. [21:31] <atmind> hypersomniac: https://drive.google.com/file/d/1x8TVHtdfzE26ZyKnicKnZmw9Ltn0qV6P/view?usp=sharing [21:32] <atmind> this is when using UNIFORM_COLOR shader, [21:33] <-- JTa (~Thunderbi@unaffiliated/jta) has left this server (Quit: JTa). [21:33] <atmind> with this patch http://pasteall.org/1397437/diff I have the same results when I minimize the vertex shader of the border drawing. So I will be twiggling around some statements.

Jeroen Bakker commented

2018-12-01 22:30:51 +01:00

Ah never mind. the UNIFORM COLOR. I see now what you tried to do with the draw border shader :-)

Jer Bot commented

2018-12-01 23:22:45 +01:00

Added subscriber: @JerBot

Jer Bot commented

2018-12-01 23:22:45 +01:00

This lagging/freezing issue also affects the latest build of Manjaro 18.0 (Arch Linux), on a Dell XPS 13" w/ the Intel 620.

Happy to report that the http://pasteall.org/1395682 FIXED my issue.

This lagging/freezing issue also affects the latest build of Manjaro 18.0 (Arch Linux), on a Dell XPS 13" w/ the Intel 620. Happy to report that the http://pasteall.org/1395682 **FIXED my issue**.

Clément Foucault commented

2018-12-02 00:17:52 +01:00

Can someone try P850 ? That's really strange that even GPU_SHADER_2D_UNIFORM_COLOR is creating problems so I suspect that there is not enough work for the driver and it misses something.

The thing with http://pasteall.org/1395682 is that it just removes all the area borders.

And reverting the optimization is a bit like saying that we put the issue on the side as it can show up at any time under another circumstance.
Theses are pretty dead-simple shaders and draw calls !

Can someone try [P850](https://archive.blender.org/developer/P850.txt) ? That's really strange that even GPU_SHADER_2D_UNIFORM_COLOR is creating problems so I suspect that there is not enough work for the driver and it misses something. The thing with http://pasteall.org/1395682 is that it just removes all the area borders. And reverting the optimization is a bit like saying that we put the issue on the side as it can show up at any time under another circumstance. Theses are pretty dead-simple shaders and draw calls !

Pablo Dobarro commented

2018-12-02 01:02:12 +01:00

I'm on a Dell XPS 13" with an Intel 620 on Manjaro 18, P850 fixes the issue and there are no errors rendering the area borders.

I'm on a Dell XPS 13" with an Intel 620 on Manjaro 18, [P850](https://archive.blender.org/developer/P850.txt) fixes the issue and there are no errors rendering the area borders.

Clément Foucault commented

2018-12-02 01:12:39 +01:00

@PabloDobarro can you try this P851 ? This should be less problematic for performance.

@PabloDobarro can you try this [P851](https://archive.blender.org/developer/P851.txt) ? This should be less problematic for performance.

Pablo Dobarro commented

2018-12-02 01:29:25 +01:00

@fclem With P851 the issue is still present, I'm not noticing any difference

@fclem With [P851](https://archive.blender.org/developer/P851.txt) the issue is still present, I'm not noticing any difference

Clément Foucault commented

2018-12-02 01:31:32 +01:00

@PabloDobarro and with P852 ?

@PabloDobarro and with [P852](https://archive.blender.org/developer/P852.txt) ?

Pablo Dobarro commented

2018-12-02 01:39:54 +01:00

@fclem I get the same result with P851 and P852, it keeps freezing.

@fclem I get the same result with [P851](https://archive.blender.org/developer/P851.txt) and [P852](https://archive.blender.org/developer/P852.txt), it keeps freezing.

Clément Foucault commented

2018-12-02 01:44:36 +01:00

@PabloDobarro So finally tests P853 and P854 and then i'll commit a more isolated fix for only this GPU familly + linux

@PabloDobarro So finally tests [P853](https://archive.blender.org/developer/P853.txt) and [P854](https://archive.blender.org/developer/P854.txt) and then i'll commit a more isolated fix for only this GPU familly + linux

Pablo Dobarro commented

2018-12-02 01:52:44 +01:00

@fclem Both P853 and P854 solve the issue, with apparently no difference between them

@fclem Both [P853](https://archive.blender.org/developer/P853.txt) and [P854](https://archive.blender.org/developer/P854.txt) solve the issue, with apparently no difference between them

blender-admin commented

2018-12-02 01:57:22 +01:00

This issue was referenced by 40d0374411

This issue was referenced by 40d0374411e28f8d1409303743e71b8b6b8aab2c

Clément Foucault commented

2018-12-02 01:57:42 +01:00

Changed status from 'Open' to: 'Resolved'

Clément Foucault closed this issue

2018-12-02 01:57:42 +01:00

Clément Foucault commented

2018-12-02 01:58:27 +01:00

Much thanks to all of you who helped narrow down the issue! Very much appreciated!

joshua pritikin commented

2018-12-02 03:26:34 +01:00

I tested 40d0374411. I'm sorry to report that It's still not fixed.

I tested 40d0374411e28f. I'm sorry to report that It's still not fixed.

Clément Foucault commented

2018-12-02 03:29:04 +01:00

@jpritikin Can you share you system-info.txt ? Maybe the fix is not applied to your hardware.

Pablo Dobarro commented

2018-12-02 03:30:35 +01:00

@fclem I'm testing the new patch but it doesn't call glFlush() on my system. Shouldn't it be GPU_DRIVER_ANY instead of GPU_OS_ANY when checking the gpu type?

@fclem I'm testing the new patch but it doesn't call `glFlush()` on my system. Shouldn't it be `GPU_DRIVER_ANY` instead of `GPU_OS_ANY` when checking the gpu type?

joshua pritikin commented

2018-12-02 03:30:52 +01:00

Looks like the code you used to detect Intel UHD doesn't work. If I add the glFlush() unconditionally then things work fine.

joshua pritikin commented

2018-12-02 03:32:03 +01:00

My system info, system-info.txt

My system info, [system-info.txt](https://archive.blender.org/developer/F5784904/system-info.txt)

blender-admin commented

2018-12-02 03:49:26 +01:00

This issue was referenced by 28b83b34d4

This issue was referenced by 28b83b34d4edbb314665e3d0ddf87144c6903408

Clément Foucault commented

2018-12-02 03:50:55 +01:00

my bad @PabloDobarro was correct. fixed

Jer Bot commented

2018-12-02 05:25:12 +01:00

Everyone's help with this issue is much appreciated. I can think of many ways to show you how much I appreciate this... and here's one:

Everyone's help with this issue is much appreciated. I can think of many ways to show you how much I appreciate this... and here's one: ![proudPartner_blenderDevFun_editSigned.jpg](https://archive.blender.org/developer/F5785763/proudPartner_blenderDevFun_editSigned.jpg)

Lewis Toohey commented

2018-12-04 20:57:42 +01:00

So is this fixed for everyone? It's still happening for me. The UI locks up every few seconds. I can't see a particular pattern to it.

I am using the latest beta at time of writing - 7e5f31be41

System info in post above.

So is this fixed for everyone? It's still happening for me. The UI locks up every few seconds. I can't see a particular pattern to it. I am using the latest beta at time of writing - 7e5f31be418 System info in post above.

Clément Foucault commented

2018-12-05 04:25:50 +01:00

@lewis2e it seems your gpu is not from the same familly as the original poster (the string "... HD Graphics 620 ..." instead of "... UHD Graphics 620 ..." . I'll make the detection match yours.

I've kicked the buildbot for you so it might be there soon.

@lewis2e it seems your gpu is not from the same familly as the original poster (the string "... HD Graphics 620 ..." instead of "... UHD Graphics 620 ..." . I'll make the detection match yours. I've kicked the buildbot for you so it might be there soon.

Lewis Toohey commented

2018-12-05 09:03:45 +01:00

@fclem Thanks! I appreciate it.

I'll give it a try tonight. Hopefully it will be the same problem.

@fclem Thanks! I appreciate it. I'll give it a try tonight. Hopefully it will be the same problem.

Lewis Toohey commented

2018-12-05 20:24:57 +01:00

@fclem Yes! This is now fixed for me. Thank you so much.

Brecht Van Lommel commented

2018-12-08 01:45:01 +01:00

Added subscriber: @hugegameartgd

Tamas Toth commented

2019-01-31 13:39:42 +01:00

Added subscriber: @ebola

Tamas Toth commented

2019-01-31 13:39:42 +01:00

Hi All!

For me this bug is new as I'm trying to use Blnder 2.80 beta just from some days ago and the second aspect of the reason of the problem as I bought one Intel NUC8i7 what has Intel Iris 655 IGPU. It seems that the whole 'family' affected by the bug not just the serie 620.

The exact situation. With the official 2.80 nighlies (from some days ago (about last 2 weeks of January 2019)) I get the very same issues what are defined in this topic. With Eevee or Cycles rendering engines also when I try to start any work the interface started to lost it's responses and after some snippy reactions at the end it freezes the whole system. Just the hard reset help.

On the same machine with Blender 2.79 there is no problem, everything works just fine with the new NUC as before on my very-very old notebook with Intel GMA 4500.

So it seems that the bug what defined in this topic affect to Intel Iris 655 also (and I think from the reactions that basically affected to the whole Intel Iris 6xx IGPU family).

Could anybody help me what could be the next/first step to test any possible solution to help on me and on Blender developments/developers also?

Thanks for your help in advance!

Hi All! For me this bug is new as I'm trying to use Blnder 2.80 beta just from some days ago and the second aspect of the reason of the problem as I bought one Intel NUC8i7 what has Intel Iris 655 IGPU. It seems that the whole 'family' affected by the bug not just the serie 620. The exact situation. With the official 2.80 nighlies (from some days ago (about last 2 weeks of January 2019)) I get the very same issues what are defined in this topic. With Eevee or Cycles rendering engines also when I try to start any work the interface started to lost it's responses and after some snippy reactions at the end it freezes the whole system. Just the hard reset help. On the same machine with Blender 2.79 there is no problem, everything works just fine with the new NUC as before on my very-very old notebook with Intel GMA 4500. So it seems that the bug what defined in this topic affect to Intel Iris 655 also (and I think from the reactions that basically affected to the whole Intel Iris 6xx IGPU family). Could anybody help me what could be the next/first step to test any possible solution to help on me and on Blender developments/developers also? Thanks for your help in advance!

Tamas Toth commented

2019-01-31 13:43:00 +01:00

Changed status from 'Resolved' to: 'Open'

Tamas Toth reopened this issue

2019-01-31 13:43:00 +01:00

Tamas Toth commented

2019-01-31 13:54:18 +01:00

Some more precise data about the environment:

Blender-2.80-da1da3053d75-linux-glibc224-x86_64.tar.bz2 (latest tried)
Ubuntu 18.10
Latest mesa drivers from: https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa?field.series_filter=cosmic
The system is: https://www.intel.com/content/www/us/en/products/docs/boards-kits/nuc/nuc8i7beh-brief.html

B 2.79 sysinfo: system-info.txt

Thanks again for your efforts!

Some more precise data about the environment: - Blender-2.80-da1da3053d75-linux-glibc224-x86_64.tar.bz2 (latest tried) - Ubuntu 18.10 - Latest mesa drivers from: https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa?field.series_filter=cosmic - The system is: https://www.intel.com/content/www/us/en/products/docs/boards-kits/nuc/nuc8i7beh-brief.html B 2.79 sysinfo: [system-info.txt](https://archive.blender.org/developer/F6466615/system-info.txt) Thanks again for your efforts!

Tamas Toth commented

2019-01-31 18:21:22 +01:00

If I'm right the patch (in the latest nightly) of this topic initiated only just in the following circumstances:

if (strstr(renderer, "UHD Graphics") ||
		    /* Not UHD but affected by the same bugs. */
		    strstr(renderer, "HD Graphics 530") ||
		    strstr(renderer, "Kaby Lake GT2"))
		{
			GG.device |= GPU_DEVICE_INTEL_UHD;
		}

As Iris 655 has name (in Blender sysinfo): renderer: 'Mesa DRI Intel(R) HD Graphics (Coffeelake 3x8 GT3) ' in my case I do not get the 'glFlush' patch.

Could @Clément Foucault (fclem) or anybody please try to modify the source condition to include this IGPU string too?

Thanks again and continuously!

If I'm right the patch (in the latest nightly) of this topic initiated only just in the following circumstances: ``` if (strstr(renderer, "UHD Graphics") || /* Not UHD but affected by the same bugs. */ strstr(renderer, "HD Graphics 530") || strstr(renderer, "Kaby Lake GT2")) { GG.device |= GPU_DEVICE_INTEL_UHD; } ``` As Iris 655 has name (in Blender sysinfo): `renderer: 'Mesa DRI Intel(R) HD Graphics (Coffeelake 3x8 GT3) '` in my case I do not get the 'glFlush' patch. Could **@Clément Foucault (fclem)** or anybody please try to modify the source condition to include this IGPU string too? Thanks again and continuously!

Tamas Toth commented

2019-01-31 18:50:48 +01:00

And lastly after some more research seems what I referred could be true but of course this is just a supposition as I did not follow the Intel IGPU history in the last some years.

Based on this informations...

This is my CPU with the defined 'Intel Iris Plus Graphics 655': https://ark.intel.com/products/137979/Intel-Core-i7-8559U-Processor-8M-Cache-up-to-4-50-GHz-

And some resources about these Intel IGPU series.
https://en.wikipedia.org/wiki/Intel_Graphics_Technology
https://www.notebookcheck.com/UHD-Graphics-617-vs-Iris-Plus-Graphics-655_9356_8828.247532.0.html
https://www.notebookcheck.com/Intel-HD-Graphics-615.173369.0.html

...I think that these IGPUs basically are very same with same drivers and as the result it seems that the bug (or so) affected to all these devices what could basically named by:

Mesa DRI Intel(R) HD Graphics or Mesa DRI Intel(R) UHD Graphics independently from their performances.

Of course I'm not an Intel IGPU expert but hope it could help on all those people who use Intel IGPU. (What is of course basically not a lucky state for 3D modelling but the life can bring some interesting situations:))

Thanks for your attentions!

And lastly after some more research seems what I referred could be true but of course this is just a supposition as I did not follow the Intel IGPU history in the last some years. Based on this informations... This is my CPU with the defined 'Intel Iris Plus Graphics 655': https://ark.intel.com/products/137979/Intel-Core-i7-8559U-Processor-8M-Cache-up-to-4-50-GHz- And some resources about these Intel IGPU series. https://en.wikipedia.org/wiki/Intel_Graphics_Technology https://www.notebookcheck.com/UHD-Graphics-617-vs-Iris-Plus-Graphics-655_9356_8828.247532.0.html https://www.notebookcheck.com/Intel-HD-Graphics-615.173369.0.html ...I think that these IGPUs basically are very same with same drivers and as the result it seems that the bug (or so) affected to all these devices what could basically named by: `Mesa DRI Intel(R) HD Graphics` or `Mesa DRI Intel(R) UHD Graphics` independently from their performances. Of course I'm not an Intel IGPU expert but hope it could help on all those people who use Intel IGPU. (What is of course basically not a lucky state for 3D modelling but the life can bring some interesting situations:)) Thanks for your attentions!

Clément Foucault was assigned by Tamas Toth

2019-01-31 18:56:08 +01:00

Brecht Van Lommel commented

2019-07-08 15:01:32 +02:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2019-07-08 15:01:32 +02:00

Brecht Van Lommel commented

2019-07-08 15:01:32 +02:00

As far as I know this was resolved.

Tamas Toth commented

2019-07-08 15:57:18 +02:00

@brecht yes! Sorry for the delay, but some weeks earlier I tried the actual build and there were not more problems with it. So independently from what was the solution but thank(s) for the developer(s) who made/correct it:)

I can validate that the problem have already solved (from my aspect).

@brecht yes! Sorry for the delay, but some weeks earlier I tried the actual build and there were not more problems with it. So independently from what was the solution but thank(s) for the developer(s) who made/correct it:) I can validate that the problem have already solved (from my aspect).

Jer Bot commented

2019-07-09 00:55:08 +02:00

@brecht , yes... ALL IS GOOD. I haven't had any stalling issues since I tried out the first patch. I'd say this bug is resolved. Thanks (everyone).

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Laggy, freezing UI with Linux and Intel UHD 620 #57455