Intel ARC 140v fuzzy text and video playback issue in Chromium based apps

[alexm1126]

Hello,

I recently got an ASUS Zenbook S14 with an Intel Core Ultra 7 258V and Intel Arc 140V. At random times, the screen briefly flashes, after which text becomes fuzzy or glitched, and videos cause the screen to go completely black in Chromium-based applications (such as Chrome, Edge, and Discord) as well as some desktop apps like Adobe Lightroom.

This issue persists across all Intel driver versions I’ve tried, including the latest 6647 WHQL release. The only workaround I’ve found is disabling hardware acceleration, but that’s not an ideal solution. I have now rolled back to the OEM driver version 6047 but I'm still waiting to see if the issue comes back.

Additional Observations:

• The issue occurs on the internal laptop display (I haven’t tested an external monitor).
• The display goes black for a brief moment before the issue starts, and the glitches persist until I restart the laptop.
• When streaming video in Chrome or other apps, the screen turns completely black.
• The glitched text appears when there is movement on the screen.

Has anyone else experienced this issue? Could this be a CPU/GPU hardware problem, a Windows bug, or a driver-related issue? Any insights or fixes would be greatly appreciated!

I’ve also attached some photos showing the issue (captured in Discord).
IMG_4736.JPEG shows the issue and IMG_4734.JPEG is how it should normally be.

Thanks in advance!

[ArielP_Intel]

Hello alexm1126,

Thank you for posting in Intel Communities! I apologize for the inconvenience this has caused you. I understand that it is an ASUS Zenbook S14.

To assist you further, kindly answer the questions below:

1. Was your system working properly fine before?
2. Have you made any recent changes?
3. Have you tried using OEM drivers?

Your clarification is greatly appreciated. Looking forward to hearing from you soon!

Best regards,

Ariel P.

Intel Customer Support Technician

[alexm1126]

Hello,

Yes, the laptop is an Asus Zenbook S14. I'm confident that the issue started after updating to the latest Intel driver (not from ASUS site). I haven't made any changes to the hardware config. I have reverted since posting the thread to the latest OEM provided driver and the issue hasn't come back. I guess it's something to do with the custom hardware configuration by ASUS that needs the OEM drivers to function properly. I wish they would update sooner to the latest driver versions. Thanks for your support!

[ArielP_Intel]

Hello alexm1126,

That's great! It's good to hear that you were able to solve the issue on your own. With that said, I will close this inquiry now. If you need further assistance, please submit a new question as this thread will no longer be monitored.

Best regards,

Ariel P.

Intel Customer Support Technician

[ylevinkr]

having the same issue with HP omnibook ultra (core ultra7 256v,  arc 140v) with both OEM driver and latest driver.
happens in both chrome and edge, effecting the whole app, an not only the websites visited.
This only happens when using HW acceleration.

edit:
using Dell thunderbolt universal dock, connected to Samsung Odyssey G9 OLED.

 

 

[alexm1126]

Honestly this has to be one of the weirdest bugs I've seen. Not sure what's causing the issue but I really hope it's not an issue with the chip itself as I really really enjoy the Ultra 7 series 2 and so far it's proven to be a great daily use product. Maybe it could be something with chromium/electron or a windows 11 issue with the new CPU/GPU series?

[Edit] I do have a small clue as to what might be causing the issue but i'm no expert so it's just speculation. I switched chrome to experimental vulkan flag with hw acceleeration enabled and the issue stopped happening (and when switching back to directx it happened again until resttarting the laptop). Maybe there is an issue with DX11/12 and these new Arc gpus?

The bug actually occured to me today only once since posting this thread, not sure what caused it this time. 

[ylevinkr]

Vulcan did not fix this for me, but I'm using an external display so turning it off and on again fixes it temporarily.
Still very annoying.

[alexm1126]

If restarting the monitor fixes the issue temporarily then i guess it's some sort of a driver or memory cache issue? i can't actually get the exact steps to reproduce the problem to actually dive deeper into what's actually going on as it happens at random times. I guess when the display connection resets the cache clears? Or something else software-related. Because if it were a hardware issue resetting the display wouldn't fix the issue, right?