Skip to main content
Participating Frequently
November 7, 2016
Question

Cuda GPU "not available" ?

  • November 7, 2016
  • 2 replies
  • 1781 views

Since upgrading to Premiere Pro 2017 I'm getting a warning that GPU acceleration is not available. Always managed to get Premiere to accept my NVIDIA GeForce GTX 670 in the past but stumped as to how to do this in 2017?

Also, wondering if I should consider upgrading this NVIDIA  graphics card and would welcome any suggestions. Current config:

  • Intel Core i7-3930K CPU @3.20GHz
  • 32 GB RAM
  • 64 bit Win 7
    This topic has been closed for replies.

    2 replies

    Participant
    December 2, 2016

    I figured it out. At least for me. I have an AMD R9 270X and an Intel Integrated Graphics. Turns out PP CC 2017 could initialize the Intel card. I realized that by using the GPUSniffer.exe. Then I simply went into my BIOS and disabled the Intel Graphics Card. And ta-daa, it worked. Hopefully it will be a solution for you guys, as well!

    All the best!

    ST

    Bill Gehrke
    Inspiring
    November 8, 2016

    Run GPUSniffer.exe in a CMD window and show us what it says.

    Here is my GTX 680 with CC 2017 on Windows 10

    C:\Program Files\Adobe\Adobe Premiere Pro CC 2017>GPUSniffer.exe

    --- OpenGL Info ---

    Vendor: NVIDIA Corporation

    Renderer: GeForce GTX 680/PCIe/SSE2

    OpenGL Version: 2.1.2 NVIDIA 375.63 21.21.13.7563

    GLSL Version: 1.20 NVIDIA via Cg compiler

    Monitors: 1

    Monitor 0 properties -

       Size: (0, 0, 1920, 1200)

       Max texture size: 16384

       Supports non-power of two: 1

       Shaders 444: 1

       Shaders 422: 1

       Shaders 420: 1

    --- GPU Computation Info ---

    Found 1 devices supporting GPU computation.

    CUDA Device 0 -

       Name: GeForce GTX 680

       Vendor: NVIDIA

       Capability: 3

       Driver: 8

       Total Video Memory: 2048MB

    C:\Program Files\Adobe\Adobe Premiere Pro CC 2017>

    What version of driver are you using?

    Above you can see my driver:  NVIDIA 375.63

    TymbAuthor
    Participating Frequently
    November 8, 2016

    Thanks much Bill. Looks like I made the mistake of trusting Windows to update the driver. When I went to NVidia's site directly I did discover that the driver was out of date. I updated to the latest version and that seems to have solved the issue.