I’ve tried other monitors with the same result, and I’ve tried several versions of the driver including the one that first supported the NVS 810, they all result in the same issue.
Based on feedback I’ve seen in other forum threads this clearly appears to be a wider issue with the driver even outside of the NVS 810.
Definitely looks to be a regression issue, as there were spans of time in posts made several years back that complained about the issue as well, then a period of silence, and now another surge in activity.