After discussing with the nvidia team this does seem to be a bug in the 177.80 driver. Reverting to the 173.14 driver does fix the issue for me.
After discussing with the nvidia team this does seem to be a bug in the 177.80 driver. Reverting to the 173.14 driver does fix the issue for me.