There is a pretty fair chance this may be related to a known issue with specific hardware setups using the 445.xx and 446.xx Nvidia drivers - the topic is currently being discussed here.
TL;DR summary: may need to revert to an older driver (e.g. any variant of 442.xx) to fix this.