- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hardware:
•32 GB DDR4 3666 Mhz
• AMD Ryzen 5700X3D
• Intel Arc B580 (Sparkle)
• Windows 11 25H2
• Native 4K display
Driver versions involved:
• 31.0.101.8434 → worked perfectly until today
• 31.0.101.8509 → updated today, same issue persists
Issue Summary
DirectComposition suddenly became disabled system‑wide today, even though driver 31.0.101.8434 had been working perfectly until now. After noticing the issue, I updated to the latest driver 31.0.101.8509, but the problem remains unchanged.
This causes severe performance issues in Chromium‑based browsers that rely on DirectComposition for video playback and frame presentation.
Before today, everything was working flawlessly on driver 8434
Browsers Affected
❌ Microsoft Edge (Chromium)
• shows DirectComposition = Disabled
• 1440p and 4K YouTube playback becomes choppy
• Hardware overlays are not used
• Fullscreen performance is degraded
• Worked fine on 8434 until today, now broken on both 8434 and 8509
❌ Brave (Chromium)
• Same behavior as Edge
• DirectComposition disabled
• 1440p/4K playback stutters
• Issue appears today on 8434 and persists on 8509
✔️ Google Chrome (Chromium)
• Chrome works correctly
• 1440p/4K playback is smooth
• Chrome uses a different fallback rendering pipeline that does not depend on DirectComposition
• This is the only browser unaffected
Technical Details
Edge and Brave rely heavily on:
• DirectComposition
• DComp video overlays
• DWM‑integrated presentation paths
When the Intel driver disables or breaks DirectComposition:
• hardware‑accelerated composition is lost
• frame presentation becomes unstable
• high‑resolution video playback suffers
Chrome is unaffected because it has a fallback pipeline (ANGLE + D3D11 without DComp) that activates when the compositor is unavailable.
This explains why Chrome works while Edge and Brave do not.
Steps to Reproduce
1. Use Intel Arc driver 31.0.101.8434 (which had been working fine until today).
2. Suddenly, DirectComposition becomes disabled.
3. Update to the latest driver 31.0.101.8509.
4. Issue persists.
5. Open Edge or Brave and check or .
6. Observe: Direct Rendering Display Compositor = Disabled.
7. Play a 1440p or 4K YouTube video → stuttering.
8. Install Chrome and check .
9. Chrome uses a fallback pipeline → smooth playback.
Expected Behavior
• DirectComposition should remain enabled.
• Edge and Brave should maintain smooth hardware‑accelerated video playback.
• Driver updates should not disable the compositor globally.
Actual Behavior
• DirectComposition became disabled today, even on driver 31.0.101.8434, which previously worked fine.
• Updating to 31.0.101.8509 does not fix the issue.
• Edge and Brave lose proper video acceleration.
• Chrome works only because it uses a different fallback rendering path
Conclusion
This appears to be a regression affecting both driver 31.0.101.8434 and 31.0.101.8509, likely related to Multi‑Frame Generation interfering with DirectComposition.
A fix on Intel’s side is required to restore DirectComposition functionality for Chromium‑based browsers that rely on it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Aldao,
Thank you for posting in Intel Communities.
I'll check on this and I will post an update once it's available.
Best regards,
JeanetteC.
Intel® Customer Support Technician
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Aldao,
Thank you for posting in Intel Communities.
I'll check on this and I will post an update once it's available.
Best regards,
JeanetteC.
Intel® Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for your dedication and time; it mysteriously resolved itself. It now works fine in all browsers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Aldao,
Thank you for your dedication and time; we’re glad to hear the issue mysteriously resolved itself and that everything is now working fine in all browsers.
We will proceed to close this thread. Should you have any further questions or concerns in the future, please feel free to submit a new post, and we will be happy to assist you.
Sincerely,
JeanetteC.
Intel Customer Support Technician
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page