I thought that setting in nvidia control panel is useful for laptops with built in GPU only. I have a desktop with similar setting, 5820K @4.0GHz, 32GB DDR4 Ram, Galax GTX980, Samsung EVO 850 - 256GB, 500GB(For projects) and I have no problem playing my LX100 and GP Hero 4 black 4K sequence in CC2015. Preview codec is set at only FHD so this maybe the reason. I will try it again tonight.

@smoke23

This may sound crazy, but reduce the amount of RAM that Premiere uses. I recently troubleshooted this same problem. In preferences/Memory, set Ram available to Premiere to 5.4 GB. This won't eliminate the stuttering, but it will reduce it and make recovery from it quicker. The problem seems to be that during playback, Premiere doesn't release the memory after it plays a frame. Instead, it keeps gobbling up more and more RAM until it reaches the limit set in Preferences. You can see this if you turn on the task manager. When it reaches that ceiling, the stuttering starts as it desperately tries to release all that RAM. By clamping down on the amount of RAM allowed to Premiere, it makes recovery quicker and hence, less stuttering. You can experiment with taking it as low as 4GB. I haven't observed any adverse affects in other areas of the program. BTW, I'm using CS6. Don't know if this applies to CC, but give it a shot.

@Ralph_B MOV is the only wrapper that supports TC on the GH4 and GH3. I have used 3 year old laptops with NVidia 635M cards and they play this 4k MOV 100Mb/s stuff just fine. Nvidia drivers can be picky, if the newest drivers are installed, try an older one.

I'm not sure where your media files "live" in that disc structure you have.

Just general info ... media cache files & media database, previews, and project files have huge demands both read/write.

Media files are mostly read-only and export are mostly write-only, so those can at times be on "slower drives" though 4k needs a strong fast connection.

Preview files need SPEED ... especially for smooth playback. Internal SSD's for cache, for previews, and for projects are cool. Or ... if you've got M.2 mobo connections, a 1/2T or full T new high-speed SSD built for M.2 connections is amazing ... can hold several parts of the project and still give better functionality than multiple drives.

Neil

That could be several things ... an issue with the way the card & your mobo's resources are set (had a problem with that once, my builder finally figured out the mobo wanted to put both the video card and some other things on the same resource-set whatever) ... or that PrPro is having issues relating to your card.

However ... noting you say you just built this ... are you on Win10?

Some people are working well on that ... and some are simply not even able to function in it, had to roll back to 8 or 7. MS completely re-built the video section for 10, dropping many of the previous coding capabilities so it's a new beast. Good part of that is the code is now a ton lighter & faster for many. Bad part ... some parts on certain setups aren't working well especially concerning video & sound cards, internal/external devices such as the AJA/BlackMagic/Kona cards & boxes ... but they seem to do ok on someone else's setup.

So that could be the main issue. Strangely, a few people found their video cards were not being used, tried to roll back to an earlier driver for that card & it worked fine. Others have to be on the latest Win10 driver set.

If you're on Win7/8, well even if 10 ... it might be worthwhile to go to their online chat support and ask for the video queue people, as their "general" people don't really have the knowledge even though they may try & go through a list of questions.

Neil

I am on Windows 10 as well, checked last night I had no problem playing 4K files of LX100 and GP Hero black.

I do know that a couple people on Win10 who were having issues (perhaps very much like this) had initially upgraded from 8 or 7. They decided to do a complete wipe of their OS / C drive, and did a complete format/fresh install of Win10, and say they are now operating fine. But I expect on the new build you installed Win10 "fresh"? So that probably doesn't help.

Trying a previous driver for the v-card is something you'd just have to test, and thankfully it's pretty quick to do.

Other than separating out the "parts" of the process as much as possible on different drives (media cache & media cache database, previews, project files, and media on separate drives if possible) and trying to work as best as possible in software-only is all I've got right now. Sadly ...

Neil

@rNeil, thank you for all your help. I'm going to try and remove the graphics card and then reinstall the original drives that came with it and report back. Could it be the PHantom 3 4K files are more compressed than the GH4 4K, and the GPU has trouble reading the frames?