This sounds like the known issue with the 460-series Nvidia drivers.
Reverting to the latest 458.xx corrects it.