No, that issue is an interaction problem with the Chrome sandbox, which is preventing the driver from querying one of its device files. Unless your other applications are using a similar sandbox, it’s not likely to be related.
GPU-Util should be 0% and Power should be 5w. Additionally “top” shows “[irq/37-nvidia]” using a constant ~2-4% CPU.
The display composition pipeline went through a major overhaul in release 390. As a side effect, it is now re-compositing the screen on every vblank. That’s likely the cause of the GPU load you’re seeing. We’re working on optimizing it to reduce the overhead (tracking bug 2085439) but in the meantime, you can force the driver to use the old composition pipeline by setting
Option "UseNvKmsCompositionPipeline" "false"
in the Device or Screen section of /etc/X11/xorg.conf.