[Solved] Capcut is freezing and crushing with dedicated GPU (Radeon RX9060 XT)

Hi,

Thanks for the detailed explanation this is actually a fairly common issue with CapCut when running on newer AMD GPUs like your Radeon RX 9060 XT.

CapCut is still not fully optimized for AMD cards on PC, and problems like white screens, ghost windows, and system freezes are often caused by driver-level conflicts or hardware acceleration bugs.

Here is a breakdown of potential causes and further troubleshooting steps, going beyond what you have already tried:

Understanding the problem:

• Driver/Software Conflict: Even though you reinstalled drivers, there might be a subtle conflict between the specific Radeon RX 9060 XT drivers and CapCut's rendering engine. CapCut might not be fully optimized for this very new (perhaps a typo for 7900 XT?) or certain aspects of AMD's architecture.

• Hardware acceleration issues: CapCut relies on hardware acceleration for smooth preview and rendering. When you switch to "High Performance" (which forces the dedicated GPU), it's trying to utilize the RX 9060 XT, and that's where the problem arises.

• CapCut version/bugs: It's possible the version of CapCut you are using has a bug that manifests specifically with certain AMD GPUs or newer architectures.

• DirectX/Vulkan/OpenGL Conflicts: CapCut uses one of these APIs for rendering. There might be an incompatibility or corruption in how these APIs interact with your specific GPU drivers.

• Power Supply Issues (less likely given 3DMark): While your 3DMark results suggest the GPU is getting enough power under stress, if there's a transient power delivery issue specifically when CapCut tries to heavily utilize the card in a certain way, it could theoretically lead to instability. However, this is less probable given your observations.

• Overlays/Background Apps: Other software running in the background with overlays (like Discord, Xbox Game Bar, or even some GPU monitoring tools) can sometimes interfere with applications, especially when hardware acceleration is involved.

Advanced troubleshooting steps:

1. Disable Hardware Acceleration in CapCut
   • This is the #1 fix for many AMD users.
     • Open CapCut
     • Go to Settings > Performance
     • Turn off hardware acceleration (you may have to scroll to find this option)
     • Restart CapCut
   • Disabling GPU rendering sounds counterintuitive, but it often fixes AMD-related instability.

2. Check for CapCut Updates:

   • Ensure you are running the absolute latest version of CapCut. Developers frequently release updates to address compatibility issues and bugs.

3. Specific AMD Driver Version Testing:

   • While you reinstalled drivers, sometimes going back to a slightly older, known-stable AMD driver version can resolve issues. Check AMD's website for previous recommended drivers for your GPU.

   • Even though 3DMark works, CapCut may choke on the latest Adrenalin version. Avoid the very latest "Adrenalin" drivers if they are brand new and might have introduced regressions.

   • Clean Driver Installation (DDU): If you haven't used it already, perform a clean driver installation using Display Driver Uninstaller (DDU) in Safe Mode. This ensures all old driver remnants are completely removed before installing fresh ones.

     • Download DDU and the specific AMD driver you want to install.

     • Disconnect from the internet.

     • Reboot into Safe Mode.

     • Run DDU to remove AMD drivers.

     • Reboot normally.

     • Install the downloaded AMD driver.

     • Reconnect to the internet.

   • Reinstall Adrenalin 23.11.1 WHQL (or another stable version from late 2023).

     • Download from AMD’s official site

   • Avoid optional/beta drivers for CapCut unless they explicitly improve video encoding.

4. CapCut's internal settings:

   • Go into CapCut's preferences/settings. Look for any options related to:

     • Preview Quality/Rendering Mode: While you tried 540p proxy, there might be other settings that influence how the preview is rendered.

5. Windows Graphics Settings - "Graphics Performance Preference":

   • You mentioned "High Performance" under Display Options. Be more specific here. If you're using Windows 10/11:

     • Go to Settings > System > Display > Graphics settings (or search for "Graphics settings").

     • Under "Graphics performance preference," you can add CapCut.exe and explicitly set it to "High performance" (using your RX 9060 XT). While you likely already did this, re-verify.

     • Experiment with "Let Windows decide": Temporarily try setting CapCut to "Let Windows decide" or even "Power saving" just to see if it bypasses the crash, although this is counter-intuitive for performance.

6. Disable AMD Software Features:

   • The AMD Adrenalin software comes with many features (Radeon Boost, Anti-Lag, Image Sharpening, Chill, etc.). Temporarily disable all of them for CapCut. These features, while beneficial for gaming, can sometimes interfere with professional applications.

   • You can do this in AMD Adrenalin > Settings > Graphics or Hotkeys sections.

   • Go to AMD Software: Adrenalin Edition, select CapCut under "Gaming" (or add it), and turn off all performance-enhancing features.

7. Check for DirectX/VC++ Redistributable Issues:

   • Ensure all necessary Microsoft Visual C++ Redistributable packages are installed and up-to-date. These are crucial for many applications. You can often find installers on Microsoft's website or by running Windows Update.

   • Run the DirectX End-User Runtime Web Installer to ensure DirectX components are not corrupted.

8. Monitor GPU Usage and Temps during Crash:

   • Use tools like HWMonitor or GPU-Z to monitor your GPU's temperature, clock speeds, and power draw just before and during the crash if possible. A sudden spike or drop might indicate an issue, though less likely if 3DMark passes.

9. Force CapCut to use software rendering

   • This is more aggressive than simply disabling hardware acceleration in CapCut.

     To do it manually:

     • Right-click CapCut shortcut > Properties

     • In the Target field, add this at the end:

        

       --disable-gpu --disable-gpu-compositing


     • Click Apply, then run CapCut using that shortcut

10. Event Viewer:

    • After a crash, check the Windows Event Viewer (eventvwr.msc). Look under "Windows Logs" -> "Application" and "System" for any "Error" or "Warning" entries related to CapCut or your graphics driver around the time of the crash. This can provide specific error codes or module names that help pinpoint the problem.

11. Compatibility Mode:

    • Right-click on the CapCut.exe, go to "Properties," then "Compatibility." Try running it in compatibility mode for a previous version of Windows (e.g., Windows 8). This is a long shot, but sometimes it can work around certain API calls.

12. Disable In-Game/Application Overlays:

    • Temporarily disable any overlays from applications like:

      • Discord

      • Xbox Game Bar

      • NVIDIA GeForce Experience (if any remnants from your old card)

      • AMD Radeon Overlay (within Adrenalin software)

13. Run CapCut as Administrator:

    • Right-click on the CapCut shortcut and choose "Run as administrator." This can sometimes resolve permission-related issues.

14. Consider a Different CapCut Build:

    • If you're using the Microsoft Store version, try the standalone desktop installer from CapCut's official website, or vice-versa. Sometimes there are subtle differences in how these builds are packaged and interact with system resources.

15. CapCut Beta/Desktop version bug
    • You may be running a newer (buggy) build. Test this:
      • Download an older stable CapCut version like v3.2 or v3.5 from a trusted mirror like UptoDown
      • See if the crashes go away
16. Alternative rendering fix
    • Some AMD users reported that switching to DirectX 11 (instead of DX12) helped, but CapCut doesn’t expose that directly. You’d have to use:
      • Environment variable for DirectX fallback (for advanced users)
      • Or wait for a patch—CapCut team is slowly improving AMD compatibility

17. Contact CapCut customer support:

    • If all else fails, write an email to [email protected]. Provide them with all the details you've shared here, especially that your previous GPU worked fine, the new GPU passes 3DMark, and the problem is specific to the dedicated AMD card. They may have specific knowledge about compatibility issues with certain AMD architectures or can provide a beta build to test.

CapCut’s core engine is optimized for NVIDIA (CUDA) and Intel GPUs, so your old GTX 1060 worked beautifully. Unfortunately, AMD cards—even powerful ones like yours—still face occasional instability until CapCut fully supports RDNA 3.

If nothing works, you might consider dual-booting into Linux with CapCut Web version (no GPU dependency), or using DaVinci Resolve Free for heavier projects—it plays much nicer with AMD.

Given that your 3DMark tests are fine, the GPU itself is almost certainly not faulty. The problem lies in the interaction between CapCut, its chosen rendering methods, and your specific AMD driver/hardware combination.

I plugged the monitor to the onboard hdmi... sily me 🙂

Anyway, Thanks for the help.