I’m experiencing frequent crashes of the AMD GPU driver when using Brave Browser on my 14-inch AMD laptop, particularly when visiting video-intensive websites like YouTube and Dailymotion. The issue persists despite updating to the latest GPU drivers (version 24.5.1) and occurs even with previous driver versions. Initially, disabling Brave Shields and fingerprinting blocking seemed to mitigate the problem, but the crashes continue regardless of these settings.
Steps to Reproduce:
- Open Brave Browser on a 14-inch AMD laptop.
- Navigate to a website that plays videos, such as YouTube or Dailymotion.
- Play any video.
- Observe the system’s behavior; the AMD GPU driver crashes during video playback.
Troubleshooting Attempts:
- Disabling Shields and Fingerprinting Blocking: Initially appeared to prevent crashes but ultimately proved ineffective.
- Testing Other Browsers:
- Google Chrome: Functions without crashes when using the integrated GPU; crashes occur when forced to use the discrete GPU.
- Mozilla Firefox: Operates without issues, even with the discrete GPU.
- Microsoft Edge (Chromium-based): Experiences crashes similar to Brave when using the discrete GPU.
- Forcing Integrated GPU Usage: Configured Brave to use the integrated GPU via Windows Graphics Settings, which prevents crashes but is a temporary workaround that sacrifices the performance benefits of the discrete GPU.
System Information:
- Operating System: Windows 10 LTSC
- Brave Version: 1.66.118 Chromium: 125.0.6422.147 (Official Build) (64-bit)
- Hardware: 14-inch AMD laptop with both integrated and discrete AMD GPUs
Request for Assistance: Given that the issue seems to be related to how Chromium-based browsers interact with AMD’s discrete GPUs on my 14 inch AMD laptop, I am seeking guidance on resolving these crashes without resorting to the integrated GPU. Is there a known fix or setting adjustment within Brave that can address this compatibility problem? Any insights or recommendations would be greatly appreciated.
Additional Context: This problem appears to be specific to Chromium-based browsers utilizing the discrete AMD GPU by default. Non-Chromium browsers like Firefox do not exhibit this behavior, suggesting a potential issue within the Chromium engine’s handling of AMD’s discrete graphics hardware.
Thank you for your support.