No doubt, I'm checking if any solutions have been discovered.
No doubt, I'm checking if any solutions have been discovered.
I've noticed those dark squares appearing frequently while watching videos on YouTube or Prime (using a brave browser). Anyone know how to eliminate them? My GPU is a 3070 and it's running the latest version. It's a bit frustrating since Nvidia hasn't released an update to fix this issue. I just want to make sure it's not a problem with my GPU. Have others seen this? P.S.: I'm okay with games working perfectly, no artifacts or problems at all.
I kept refreshing and sometimes it occurs, though it rarely happens on other drivers. Eventually it does after some time. I believe it's not my GPU because I play GPU-heavy games without problems and have tested it several times.
It could stem from problems in the hardware decoder part of your graphics card. Try turning off the hardware video decoder in your media player to check if the issue lies there. MPC-HC automatically uses hardware decoding by default; if you encounter artifacts, disable it and switch to CPU decoding (or Quicksync in your CPU). You can find the software from https://github.com/clsid2/mpc-hc/releases. While playing videos, you can disable hardware decoding in the LAV Filter (Play > Filters > LAV Video Decoder). This method works with older MPC-HC versions on some devices. If you don’t see errors using only CPU decoding, the problem is likely in your card’s drivers or hardware. You might still adjust your browser settings to avoid hardware decoding, though it would slow things down more.
I've never encountered this before on any GPU. It seems like the cooling paste or pad might be applied by the manufacturer. If it were a GPU issue, it should crash rather than just heat up. This suggests a possible VRAM overheating or clock speed problem.
This appears to be a resolved problem with a known fix. Check the relevant issues: https://issues.chromium.org/issues/40281472 and https://issues.chromium.org/issues/40735345. Updating your system is important, as a driver update alone won't resolve it. The patch referenced is KB5037853.