Youtube, Discord, Visual Studio Code are flickering with black checkered squares/vertical lines. Partial solutions to this issue.

[Solaris17]

hey guys, just signed up to say I saw this issue with my 4090 that I just bought. Was concerned that its the GPU hardware and was going to return but looks like its widespread and is driver related. Here's my post on Reddit with a short video of the issue. Here's the recording direct link: https://youtube.com/shorts/CkLSddIx5k0?si=pLGv3mpg4qiko1yX

YES! this is what happens!!! I was about to RMA my 4090. Out of curiosity do you also get random lag or freezing when you have a video going and your playing a game?

It doesnt happen on my A770, so I thought my 4090 was just trashed.

 

[Mussels]

YES! this is what happens!!! I was about to RMA my 4090. Out of curiosity do you also get random lag or freezing when you have a video going and your playing a game?

It doesnt happen on my A770, so I thought my 4090 was just trashed.

This could be what MS is dealing with in the upcoming 11 update, with mismatched framerates between overlay planes - 60Hz video on a 120Hz display is easy, but 60Hz on 144? Frames gotta drop somehow, and this may be how it presents.

Scrolling in the browser with YT has been laggy for years now even on 30 series, I just dont get the artifacting on top. If the video is paused, it's smooth - it's like it has issues combining different frame rates within the same window/program - It can't handle Chrome itself at 144FPS, with the video at 60

I know your displays are 144Hz, can you test them all at 120Hz and see if the 2:1 ratio helps?

 

[Solaris17]

I know your displays are 144Hz, can you test them all at 120Hz and see if the 2:1 ratio helps?

Thank I can get back to you but it will be a few weeks, my 4090 is packed for a move. I appreciate the insight though! I'll let you know.

 

[Wezelkrozum]

That ties in to MPO, so it does seem related to the overlay layers after all

Something is presenting over the top of the video, whatever it may be

Yes, it has certainly something to do with the video.
However, I need to rectify my earlier statements.

I believe there are 2 (or maybe even 3) separate bugs related to MPO and videos in chromium that cause the same checkerboard artifacts. Because not all my artifacts are resolved with the --disable-direct-composition-video-overlays flag anymore. And they all seem to have different ways that cause it (different test/reproduction paths).
I was able to narrow current artifacts down to a change between chromium build 1136035 and 1136075. Those builds have both the chromium version 115.0.5736.0 and have been publicly rolled out on July 18, 2023.

1. [Reported on 2020/12/03] The bug where it happens when you draw a playing video onto a canvas element. This can be resolved with the --disable-direct-composition-video-overlays flag. And I had reported this in 2020: https://bugs.chromium.org/p/chromium/issues/detail?id=1155285#c44
2. [Reported by several users around march 2023 at the start of this forum thread] I'm personally not sure what triggered these reports. But this could indeed be the 22h2 update for Windows 10 as KsushaTeaKisa reported. This bug can be resolved by changing the ANGLE flag to D3D9 or OpenGL.
3. [Found out today 2023/09/08] The bug where it happens when I move elements or trigger css animations on a webpage that displays a video. It does not matter if the video is playing or paused. This also can be resolved by changing the ANGLE flag to D3D9 or OpenGL. This bug has apparently been introduced between chromium build 1136035 and 1136075 and have been publicly rolled out on July 18, 2023 ( Chrome 115 release notes ). I'll report this issue to the chromium devs and add a link to that issue here later. The interesting difference between these builds is that they have updated ANGLE from version 2.1.20985 to 2.1.20986. So this could be a bug in ANGLE and not in Chromium directly.

I think those dates match the acceleration in reports pretty well:
1. Only the users of my extension since 2020/12/03
2. The users that had quickly updated Windows since march 2023
3. The users that have updated to Chrome 115 since 2023/07/18


PS:

I know your displays are 144Hz, can you test them all at 120Hz and see if the 2:1 ratio helps?

I can still reproduce the artifacts that were introduced in Chrome 115 on a 120Hz display.

 

[KsushaTeaKisa]

Yes, it has certainly something to do with the video.
However, I need to rectify my earlier statements.

I believe there are 2 (or maybe even 3) separate bugs related to MPO and videos in chromium that cause the same checkerboard artifacts. Because not all my artifacts are resolved with the --disable-direct-composition-video-overlays flag anymore. And they all seem to have different ways that cause it (different test/reproduction paths).
I was able to narrow current artifacts down to a change between chromium build 1136035 and 1136075. Those builds have both the chromium version 115.0.5736.0 and have been publicly rolled out on July 18, 2023.

1. [Reported on 2020/12/03] The bug where it happens when you draw a playing video onto a canvas element. This can be resolved with the --disable-direct-composition-video-overlays flag. And I had reported this in 2020: https://bugs.chromium.org/p/chromium/issues/detail?id=1155285#c44
2. [Reported by several users around march 2023 at the start of this forum thread] I'm personally not sure what triggered these reports. But this could indeed be the 22h2 update for Windows 10 as KsushaTeaKisa reported. This bug can be resolved by changing the ANGLE flag to D3D9 or OpenGL.
3. [Found out today 2023/09/08] The bug where it happens when I move elements or trigger css animations on a webpage that displays a video. It does not matter if the video is playing or paused. This also can be resolved by changing the ANGLE flag to D3D9 or OpenGL. This bug has apparently been introduced between chromium build 1136035 and 1136075 and have been publicly rolled out on July 18, 2023 ( Chrome 115 release notes ). I'll report this issue to the chromium devs and add a link to that issue here later. The interesting difference between these builds is that they have updated ANGLE from version 2.1.20985 to 2.1.20986. So this could be a bug in ANGLE and not in Chromium directly.

I think those dates match the acceleration in reports pretty well:
1. Only the users of my extension since 2020/12/03
2. The users that had quickly updated Windows since march 2023
3. The users that have updated to Chrome 115 since 2023/07/18


PS:

I can still reproduce the artifacts that were introduced in Chrome 115 on a 120Hz display.

At the time I started this thread, I was using a 1080p display at 75Hz, now since the beginning of summer I have been using a new 1440p display at 170Hz and now I noticed one thing. The higher the screen refresh rate I set, the more often these artifacts appear. For example, before I didn’t see artifacts in the Steam client, but now I see them if I turn on some video on the game page in shop, and these artifacts began to appear on Youtube pages much more often. I can even now reproduce the artifacts while the video is paused if I move my mouse over the top header of the browser next to the tabs.

P.S I'm currently using Windows 11 with all the latest updates.

 

[Wezelkrozum]

At the time I started this thread, I was using a 1080p display at 75Hz, now since the beginning of summer I have been using a new 1440p display at 170Hz and now I noticed one thing. The higher the screen refresh rate I set, the more often these artifacts appear. For example, before I didn’t see artifacts in the Steam client, but now I see them if I turn on some video on the game page in shop, and these artifacts began to appear on Youtube pages much more often. I can even now reproduce the artifacts while the video is paused if I move my mouse over the top header of the browser next to the tabs.

P.S I'm currently using Windows 11 with all the latest updates.

I believe that is also bug nr 3. Could you check if you can reproduce this on build 1136075 but not on 1136035?

You can download Google's chromuim builds here:
Chromium build 1136035
Chromium build 1136075

Extract the zip, close any other application windows and run /chrome-win/chrome.exe.
Only run one chrome.exe application at the time, because running multiple chrome builds in parallel conflicts with each other.

Is it possible to share a screen recording? Then I will include in my bug report to chromium.

 

[KsushaTeaKisa]

I believe that is also bug nr 3. Could you check if you can reproduce this on build 1136075 but not on 1136035?

You can download Google's chromuim builds here:
Chromium build 1136035
Chromium build 1136075

Extract the zip, close any other application windows and run /chrome-win/chrome.exe.
Only run one chrome.exe application at the time, because running multiple chrome builds in parallel conflicts with each other.

Is it possible to share a screen recording? Then I will include in my bug report to chromium.

I tried both of these builds and I was easily able to reproduce this bug by my new method using the browser interface when the video is paused (4K quality).

Link to video

For more information:
Display 1440p at 170Hz and 8bit
GPU 2060 super
Windows 11 22H2 build 22621.2215, HAGS enabled, MPO enabled
No games/screen recordings while reproducing the bug of course

 

[Wezelkrozum]

I tried both of these builds and I was easily able to reproduce this bug by my new method using the browser interface when the video is paused (4K quality).

Link to video

For more information:
Display 1440p at 170Hz and 8bit
GPU 2060 super
Windows 11 22H2 build 22621.2215, HAGS enabled, MPO enabled
No games/screen recordings while reproducing the bug of course

Then I think that you are reproducing bug nr 2 via that new method.
(I was also able to get artifacts via your method. But I only got them 3 times in a timespan of 10 minutes with build 1136075 and so far did not get them in build 1136035. But I wasn't really able to prove that they were not in the previous because it can take more than 10 minutes on my machine.)

Can you also reproduce bug nr 3 in both Chromium builds via this method?
1. Create a YouTube playlist with at least 20 videos (so that the list is scrollable)
2. Click a video in the playlist and pause it.
3. Click on the playlist title to navigate back to the playlist page with a miniplayer in the bottom right corner.
4. Drag a video in the playlist to multiple locations (and to the left and right to create a horizontal scrollbar on the webpage)

Here is a video recording of me reproducing bug nr 3 in build 1136075 but not in build 1136035:

 

[KsushaTeaKisa]

Then I think that you are reproducing bug nr 2 via that new method.
(I was also able to get artifacts via your method. But I only got them 3 times in a timespan of 10 minutes with build 1136075 and so far did not get them in build 1136035. But I wasn't really able to prove that they were not in the previous because it can take more than 10 minutes on my machine.)

Can you also reproduce bug nr 3 in both Chromium builds via this method?
1. Create a YouTube playlist with at least 15 videos (so that the list is scrollable)
2. Click a video in the playlist and pause it.
3. Click on the playlist title to navigate back to the playlist page with a miniplayer in the bottom right corner.
4. Drag a video in the playlist to multiple locations (and to the left and right to create a horizontal scrollbar on the webpage)

Here is a video recording of me reproducing bug nr 3 in build 1136075 but not in build 1136035:

I'll try to do it tomorrow, it's night now in my place
I will update this post as soon as I have the result.


EDIT:
I did your method #3. I was able to reproduce the bug only in build 1136075.
But for some reason it was hard for me to reproduce it, because the artifacts did not appear as often as yours, but the artifacts were definitely there. If I use my standard Google Chrome browser 116.0.5845.181, I can reproduce method #3 much easier. Really don't know why, perhaps some peculiarity of the RTX 20.
In build 1136035 I was unable to reproduce the bug using method #3, I spent about 30 minutes after the video trying to reproduce it there.

Video:

Examples of artifacts from the video:
Timecode 0:22

Timecode 0:24

My method (bug #2) is the easiest to reproduce for me. I tested this on two identical RTX 2060S purchased in different countries. But your theory about bugs is correct, you did a good job

 

[Wezelkrozum]

I've reported bug nr 3 to the Chromium developers: https://bugs.chromium.org/p/chromium/issues/detail?id=1480717

 

[christizzz]

Hello,

watching netflix on chrome is also causeing flicker... the screens will flciker until the gpu driver crashes (nvlddmkm)... disabling hardware acceleration solves this...
i dont think it is my 3080 thgough but i got worried...

 

[KsushaTeaKisa]

Hello,

watching netflix on chrome is also causeing flicker... the screens will flciker until the gpu driver crashes (nvlddmkm)... disabling hardware acceleration solves this...
i dont think it is my 3080 thgough but i got worried...

Hello, It's weird because this bug doesn't cause nvlddmkm crashes. Perhaps you have a different issue. Is it possible to share a screen recording to show what these flickers look like?

 

[Solaris17]

Is it possible to share a screen recording to show what these flickers look like?

im not sure it matters. I have had enough gpu's go bad over the years to literally think this kind of tearing was vmem related. I was on the verge of RMAing until I found this. I will have to try some of the fixes when I swap my 4090 back in.

 

[christizzz]

Hello, It's weird because this bug doesn't cause nvlddmkm crashes. Perhaps you have a different issue. Is it possible to share a screen recording to show what these flickers look like?

thank you for your reply. I ll try to make a video this evening. Basically, i have no issues in games or heavy gpu loads.
i can run benchmarks for hours without any issues evebn OCCT test are always ok.

I was getting the checker board recently. And yesterday i wanted to ckeck a video on netflix (in chrome not the app). So i started the video and my screen started going off and on several time until i exited chrome.
Then i tried it again and this time i put netflix in full screen, now both of my screens were turning on and off again. i left it for like 20seconds to see but nothing changed.. then i decided to test the angle workaround with Opengl, it worked but it flickered one time and i noticed the nvlddmkm error. So i started Heavenchmark which directly crashed my windows and restarted. So i reverted the OpenGL back in chrome and turned off Hardware acceleration. No problem since. I even tried Firefox and there is no probelm with netflix either.

I dont think its my GPU, i did a DDU this morning and i will try with default Chrome settings again this evening.

Regards

 

[KsushaTeaKisa]

thank you for your reply. I ll try to make a video this evening. Basically, i have no issues in games or heavy gpu loads.
i can run benchmarks for hours without any issues evebn OCCT test are always ok.

I was getting the checker board recently. And yesterday i wanted to ckeck a video on netflix (in chrome not the app). So i started the video and my screen started going off and on several time until i exited chrome.
Then i tried it again and this time i put netflix in full screen, now both of my screens were turning on and off again. i left it for like 20seconds to see but nothing changed.. then i decided to test the angle workaround with Opengl, it worked but it flickered one time and i noticed the nvlddmkm error. So i started Heavenchmark which directly crashed my windows and restarted. So i reverted the OpenGL back in chrome and turned off Hardware acceleration. No problem since. I even tried Firefox and there is no probelm with netflix either.

I dont think its my GPU, i did a DDU this morning and i will try with default Chrome settings again this evening.

Regards

Hmm, I think I understand what you are talking about. This sounds like a bug from this thread combined with another issue that causes your screen going off and restart the driver. I almost always read driver feedback, and some people have described a similar problem since driver version 536.
However, those people have crashes while gaming. Try switching setting "Power management mode" to "Maximum Performance" in NVIDIA Control Panel.
If you had a problem with crashes before version 536, then I have two options:
1. Your PSU is not enough for the GPU
2. Problem with the GPU. Better try to do RMA, but before that, try to test your GPU in another computer

I really don't want to upset you, but it's better to consider all the options.

 

[Zer0code]

I recorded a new video with artifacts in chrome, RTX 3060 graphics card. It looks like different video cards have slightly different artifact patterns.
Timecodes: 0:43, 0:47, 0:55, 0:57

 

[Wezelkrozum]

I recorded a new video with artifacts in chrome, RTX 3060 graphics card. It looks like different video cards have slightly different artifact patterns.
Timecodes: 0:43, 0:47, 0:55, 0:57

Could you verify that you do not get these artifacts with Chromium build 1136035 ?

 

[christizzz]

Hmm, I think I understand what you are talking about. This sounds like a bug from this thread combined with another issue that causes your screen going off and restart the driver. I almost always read driver feedback, and some people have described a similar problem since driver version 536.
However, those people have crashes while gaming. Try switching setting "Power management mode" to "Maximum Performance" in NVIDIA Control Panel.
If you had a problem with crashes before version 536, then I have two options:
1. Your PSU is not enough for the GPU
2. Problem with the GPU. Better try to do RMA, but before that, try to test your GPU in another computer

I really don't want to upset you, but it's better to consider all the options.

hello.. here is a video... https://drive.google.com/file/d/1u4raP-OeBqo_T9ON3C4W02h84JC2MJjI/view?usp=sharing

so as i said it only happening when in Netflix in the browser. if in full screen i get it on both displays. So after this today i didn not get any nvlddmkm. and as i said it doesnt do it all the time in netflix... so it is difficult to reproduce... but it happens often...i am testing the chrome beta too.
The above video is after the DDU, i played with Cyberpunk and did some video benchmarsk with OCCT... no errors. And the flicker doesnt happen in Firefox.


Update: same issue with Chrome Beta

 

[Zer0code]

Could you verify that you do not get these artifacts with Chromium build 1136035 ?

I didn't see any artifacts on this version. Probably need more time for the test.

 

[KsushaTeaKisa]

hello.. here is a video... https://drive.google.com/file/d/1u4raP-OeBqo_T9ON3C4W02h84JC2MJjI/view?usp=sharing

so as i said it only happening when in Netflix in the browser. if in full screen i get it on both displays. So after this today i didn not get any nvlddmkm. and as i said it doesnt do it all the time in netflix... so it is difficult to reproduce... but it happens often...i am testing the chrome beta too.
The above video is after the DDU, i played with Cyberpunk and did some video benchmarsk with OCCT... no errors. And the flicker doesnt happen in Firefox.


Update: same issue with Chrome Beta

Hello,
Thanks for the video. I saw similar video-reports in Nvidia Driver Feedback Thread, but I don’t know how those users solved this problem and whether it was a hardware problem or not. How long have you had this problem? I want to hope that this is just a problem in the driver or operating system, and not in the hardware. Are you currently using Chrome's default settings? If this happens again, then try using "Maximum Performance" in NVIDIA Control Panel, and then use OpenGL API without disabling hardware acceleration.
I also recommend that you try to reproduce this problem on another computer with a clean operating system and write about it in the Nvidia Driver feedback. Something tells me that this shouldn't be a hardware problem, at least I hope so.

 

[christizzz]

to be fair i never noticed until yesterday. I never watch netflix on the PC, but yesterday my TV was not available. So i fired up netflix i. the browser and got this...

 

[problem777b]

Now this issue will be in the list of problems from user m_w_h under every NVIDIA driver and will be constantly known to NVIDIA and other users.

View attachment 290518

Hello! as i can see u have already done a lot of work in related with this bug or problem! and also u have sproken with many guys with the same problem so maybe u can help me with an advise?
2 days ago I got a brand new GPU ASUS RTX 4070! before that GPU i was using my old GTX 960 and had no black boxes in my chrome at all! Now i am wondering! as my return window is still open! maybe it will be better to send the card back and get another one? maybe this bug is somehow related also with hardware? or there is no meaning to do that? and i will get the same boxes with the new copy of GPU? maybe u know someone who has already changed the GPU and the problem was fixed or maybe the replacement did not give any results? thx in advance

 

[KsushaTeaKisa]

Hello! as i can see u have already done a lot of work in related with this bug or problem! and also u have sproken with many guys with the same problem so maybe u can help me with an advise?
2 days ago I got a brand new GPU ASUS RTX 4070! before that GPU i was using my old GTX 960 and had no black boxes in my chrome at all! Now i am wondering! as my return window is still open! maybe it will be better to send the card back and get another one? maybe this bug is somehow related also with hardware? or there is no meaning to do that? and i will get the same boxes with the new copy of GPU? maybe u know someone who has already changed the GPU and the problem was fixed or maybe the replacement did not give any results? thx in advance

Hello,

Yes, I know people who did RMA and got the same bug again on a new GPU. There is no point in RMA your GPU if there are no other problems with it, because the artifact bug in Chromium is not a hardware problem, it is a software problem.
Just change your ANGLE to OpenGL API and wait for the fix.

 

[problem777b]

Hello,

Yes, I know people who did RMA and got the same bug again on a new GPU. There is no point in RMA your GPU if there are no other problems with it, because the artifact bug in Chromium is not a hardware problem, it is a software problem.
Just change your ANGLE to OpenGL API and wait for the fix.

do you know maybe also someone who did RMA and the problem was fixed bc of that?? How i was not having that problem on my GTX 960 then?

 

[KsushaTeaKisa]

do you know maybe also someone who did RMA and the problem was fixed bc of that?? How i was not having that problem on my GTX 960 then?

This bug should not affect the GTX 9xx due to non-support overlays. I've seen reports from people with videocards ranging from GTX 16 to RTX 40