Solution (FIX) - Checkerboard like patterns randomly appearing in Chromium based applications

This issue should now be resolved for all branches, on both Windows 10 and Windows 11 as of 25th of June 2024.

Original post with all edits:

Spoiler

https://blogs.windows.com/windows-i...nd-22631-3668-to-the-release-preview-channel/

Should be coming soon to everyone ^

Settings → System → About → Check your “OS Build” under Windows Specifications

Microsoft has fixed the issue in Windows 11 Build 26xxx (currently, both Dev and Canary insider builds are on this branch).

Stable and Beta have not yet been updated to this build of Windows. As of 17th of April 2024

EDIT: Old Update - December 6th 2023

As suspected earlier, it was never an nVidia or Chromium issue. Microsoft has resolved the issue, but right now it is only available for Windows 11 Insider Beta and Canary builds. Hopefully it will be pushed down to the stable version of Windows 11 soon. Information confirmed by @Astyanax on Page 4 of this thread.

I will update here most likely once the fix has been pushed to the stable build.

OLD POST BELOW:

A huge thank you to @Astyanax for proposing the latest solution to this open issue. It works better than the previous method, and one can continue using default browser settings without changing flags.

It works for both Microsoft Edge and Google Chrome in my testing - would appreciate more feedback

By adding the --disable-direct-composition launch parameter to the target location of the shortcut for each browser, you solve this issue.

I usually have my preferred browser pinned to the taskbar. If there is a desktop shortcut, I right click to unpin the shortcut in the taskbar, then right click the desktop shortcut, go to properties. Under Target: click and go to the end of the directory location, press space bar, and add the following:

Code:

--disable-direct-composition

After doing this, I drag the icon from the desktop to the taskbar to pin it back.

I added a lot tags to the post so if someone searches for this issue, hopefully they can locate this post. Feel free to link the post to anyone experiencing it elsewhere or just giving them the solution.

Post #2 is the previous method if the above does not solve the issue for you. But this did solve the issue and in a more stable way for me.

Edit:

Also, credit to reddit user u/m_w_h, who posted this solution over 5 months ago here.

 

27th of June 2024 - Check Above - Issue resolved on all branches of Windows 10 and 11. None of these are needed now, just update your OS.

Spoiler

The previous method which I discovered a while back when I faced the issue with my RTX 3090 was to open the "Flags" for the browser, and change "Choose ANGLE graphics backend" to OpenGL, but that started encountering issues lately. So D3D9 is now more stable.

EDIT Note – 29/10/2023: This method breaks RTX Video Super Resolution (VSR). So if you use that to upscale videos in Chrome, you might want to use the method from the original post above.

In Chrome type chrome://flags/ or in Edge browser type edge://flags/ in the address bar and press Enter. This should open the Flags, I do not recommend playing with settings here without researching them.

Search for the following:

Choose ANGLE graphics backend

Change it to D3D9 instead of Default, and click Relaunch in the bottom right corner.

Picture demonstration below:

 

While the the old workaround stated can be used with browsers, there are still issues with Chromium based applications/applications that use Chromium such as Visual Studio / Discord etc.

https://bugs.chromium.org/p/chromium/issues/detail?id=1155285#c44​

https://www.reddit.com/r/nvidia/com...dy_studio_driver_53141_faqdiscussion/jf5sg9u/

m_w_h 3 points 5 months ago*
Is the issue still present when using the following:
Create a windows shortcut to Chrome
Right click on the Chrome shortcut and add --disable-direct-composition-video-overlays [or --disable-direct-composition] to the end of the target line AFTER the quote "
e.g.

"FullPathWillBeHere\chrome.exe" --disable-direct-composition-video-overlays​

Start Chrome using the shortcut
Just want to rule something out ^​

https://www.reddit.com/r/nvidia/com...dy_studio_driver_53141_faqdiscussion/jf61uo8/

KseniyaTeaKisa 3 points 5 months ago
Thanks for your reply!

Yes, this parameter [--disable-direct-composition-video-overlays] helps, I've tested it with video where I always have artifacts with my GPU. Now on DirectX 11 and with my display refresh rate there are no artifacts on Youtube, but what about applications such as Discord, Visual Studio Code, etc.? This issue definitely appeared after the 22H2 update last fall.
​

If you are interested, there's a list of applications impacted along with mitigation / further testing in the thread over at https://www.techpowerup.com/forums/...lines-partial-solutions-to-this-issue.306623/​

 

Does option D3D11on12 also resolve the issue?

 

I assume the launch parameter solution from the first post works with those applications facing this issue?

I have also seen people experience it with some game launchers.

From my testing, nope. Because it ultimately still uses D3D11. OpenGL was working for months until recently too. D3D9 was the latest one to bypass the issue.

 

Many applications that use Chromium backend and are impacted don't expose/acknowledge the command line options -disable-direct-composition-video-overlays OR -disable-direct-composition so will need a Chromium/developer fix.

 

Oh yeah, fair enough. I really do hope it does get fixed.

According to @Astyanax nVidia has an engineer working on the issue. But ultimately Microsoft & Google need to figure it out.

I do hope it is resolved sooner rather than later.

 

@Blackfyre the following may also be of interest, an additional launch command line flag:

-disable-features=DCompPresenter
​

Addresses an issue that was introduced recently in Chromium dev, specifically in DCompPresenter ultisation of overlays

https://chromium.googlesource.com/chromium/src.git/+/02c3a71f121a8b7efc2600d5802ec23b1a5d95c3

"Instead of wrapping the root swap chain/surface allocation in DirectCompositionSurfaceWin as a GLSurface to be drawn as the DirectRenderer "current frame", the root render pass backing is now allocated in SkiaRenderer itself and rendered as a normal render pass and scheduled as an overlay."​

Testing / explanation at https://www.techpowerup.com/forums/...l-solutions-to-this-issue.306623/post-5099391

 

Thank you, I'll look into it later.

 

Could you tell me what is the default that edge/chrome uses? DX11!?

 

In the description it says:

So yes, D3D11 is the default. But you can choose default if you want in case your systems default is something else perhaps.

If you're using the first method in post 1 instead of the older method in post 2, you can just reset all flags to default and the issue should not show up.

 

It was just to satisfy my curiosity haha, I've been using your DX tip in the other thread for a while now.

 

@Blackfyre official update from Nvidia:

https://www.nvidia.com/en-us/geforc...53734-feedback-thread-released-91223/3384031/

Manuel@NVIDIA: Thank you. We are reaching out to Microsoft and I have shared the additional information from the URLs you shared.​

For now adding --disable-direct-composition and --disable-features=DCompPresenter to the web browser shortcut will address the legacy issue and a newer issue introduced in Chromium commit 02c3a71f121a8b7efc2600d5802ec23b1a5d95c3

Code:

--disable-direct-composition --disable-features=DCompPresenter

 

Not yet affected by this thankfully, only Edge has a flicker or two when doing a certain action, but this happens maybe once a week.

 

I had this issue but it went away with some Chrome Dev version. Maybe worth trying out?

 

Was random luck I guess, I just tested it over the past 12 hours on Chrome Dev Build.

I thought you were right for the first 6 or 7 hours, then they started appearing again, has happened multiple times since.

Conclusion, not fixed yet.

 

Spent the rest of today transitioning to Firefox, for both phones, and Windows. Since the Google password manager is also external now and can be used independently, I have no reason to stay with them.

I'm not going back to Chrome, not any time soon or until Firefox has some major issue in the future that's on this level.

Taking longer than a year to find a fix for this chromium artifacts BS and still no solution in sight? Get absolutely fu**ed with that sh**! To all the parties involved.

If it wasn't for Astyanax telling me that it's not solely an nVidia issue, I would have binned my RTX 3090 too. Even though DLSS is significantly better than FSR.

Google/Microsoft/nVidia need to get this sorted.

 

It wasn't until recently that I started seeing this issue and with the latest Nvidia driver it has gotten worse. Whenever I watch a YT video it keeps flashing that checkerboard pattern...I'll tryout Firefox.

 

Are you talking about the same issue I'm getting?
I have randomly black flickering (I think sometimes it's white but not sure),
that's happening basically while using Microsoft Edge, I don't remember if I noticed this issue outside Microsoft Edge,
it's happening only for a split second, and randomly, but I tried to mimic the same issue using Paint with random background https://imgur.com/a/XgU1GVe,

 

Are you sure it looks like that, that big? And on the desktop?

(Also check this thread, where there are a lot more examples and pictures).

It's more like these examples I found online: